I think Windows 2003 uses a more modern code base than Windows XP. 2003 is more similar to XP 64-bit.
On Mon, Aug 6, 2012 at 8:49 AM, Gerd Hoffmann firstname.lastname@example.org wrote:
On 07/24/12 19:51, Alexey Korolev wrote:
Win2003 falls to BSOD during early init stage of installer. It is ACPI related issue and it appears in any configuration. RAM size is 6GB Error code is : 0x000000A5 (0x02, 0xFFFFfADF6A446880, 0x1, 0xFFFFFADFAA34690)
The things get broken after commit 2062f2bab81915c5c1f7af12a49ad8d4b3fd23fb (update dsdt resources at runtime)
I've tried to debug this issue but haven't succeed yet.
One strange thing here is that the code doesn't reach the _CRS method. We have added a debug output but nothing related to CRS was printed. May be you have any ideas why it may fail. I would much appreciate any help on this.
DBUG() didn't work for me with winxp (same code base as win2k3 iirc), so no debug output is *not* an indicator for not reaching _CRS.
Is this win2k3 with latest service pack? I've used winxp with sp3 for testing ...
SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios