Custom using Intel Pentium II 333 MHz
Intel MU440EX motherboard with onboard everything, supports UDMA2 for IDE
192 MB RAM
Varying hard drives from 20 GB maxtor to 40 GB Western Digital
I used Win2K SP4 as my baseline, and I used its recovery console to inspect the drives before and after a failed setup.
Baseline: Win2K SP4 Diskpart display
Code: Select all
38167 MB disk 0 at Id 0 on Bus Atapi C: FAT32 9000 MB (8991 MB free) Unpartitioned Space 29167 MB
Code: Select all
38167 MB Harddisk 0 (Port=0 Bus=0 Id=0) on Atapi C: FAT32 9000 MB Unpartitioned Space 4294959599 MB
I've used FIXBOOT and FIXMBR from the Win2K console to reset the boot sectors, but this didn't make a difference. The disk had been exposed to Norton Ghost 2003 and it had a Ghost ID on it, so I thought that was confusing Setup. I also tried disabling Logical Block Addressing support in the BIOS and repeating the FIXBOOT and FIXMBR steps, with the same results.
Even more interesting is when I try to delete existing partitions from ReactOS setup, I'll only be able to create new partitions of 1.2 GB, or maybe 1.8 GB if I'm lucky. Attempting to format any partition from Setup will promptly freeze.
I've tried creating partitions using Diskpart from Win2K Recovery Console manually, then starting ReactOS Setup. From this approach, I can get as far as specifying the ReactOS folder. Then it will begin to create its folder structure and start to copy atapi.sys, after which it promtly freezes. Inspecting the crashed installation shows me the folders in system32 and atapi.sys in system32\drivers, but I haven't yet inspected this file to see if it's complete -- it does match the original file size however.
I don't know if ReactOS tries to use ACPI or not, but this machine's motherboard required me to force ACPI support in Win2K Setup to enable it. However, it does work. I was under the impression that ReactOS doesn't use ACPI though.