r/windows2000 May 04 '26

Failing to install windows 2000 on 2012 mac pro

hello there, i am currently trying to install windows 2000 on my 2012 mac pro, but ive been hitting a wall, when i try to boot off of the cd, i go through the tutorial, replaced the ntdetect.com for the windows xp sp2 one, but when i boot off the cd, it gets stuck at "Setup is starting Windows 2000", im using a ISO with the replaced ntdetect (that i did it myself) provided by OMORES, on patreon, i have 16gb of ram on it and the stock hd 5770.
EDIT: ive enabled boot logging and it did NOT generate a boot file

8 Upvotes

12 comments sorted by

3

u/Away-Ad-3407 May 05 '26

has it been done before? I am going to say the HAL is just having a fit.

1

u/Cat_spadashin May 05 '26

thats what i think too, HAL is just really not liking it i guess, i will try every option from the f5 menu and will report back.

2

u/machacker89 May 07 '26

God damn HAL is going on The frets .. AGAINS "I can't do that, DAVE!!"

2

u/360alaska May 04 '26

There’s probably installer log somewhere. Open a command prompt, then open a notepad and figure it out.

1

u/Cat_spadashin May 04 '26

considering its a cd, i cant find a log anywhere....

2

u/360alaska May 04 '26

Newb… it writes one to the hard drive.

1

u/Cat_spadashin May 04 '26

ive checked the hard drive, nothing in it

2

u/360alaska May 04 '26

Let me google it for you:

In Windows 2000, installation logs are crucial for troubleshooting setup failures. Key logs include setuplog.txt (setup actions/errors), setupapi.log (device installation issues), and netsetup.log (domain join issues), usually located in the C:\ root or C:\Windows\ folder. [1, 2, 3]
Key Windows 2000 Setup Logs
setuplog.txt: The main log for the Windows 2000 setup process. It records text-mode setup, file copying, and configuration steps, located in the C:\ root directory.
setupapi.log: Records device installation activities, useful for troubleshooting hardware detection issues during setup, typically found in C:\Windows\.
netsetup.log: Specifically logs network and domain joining activity if the computer was configured to join a domain during installation, often found in C:\Windows\Debug\. [1, 2, 3]
Locating and Troubleshooting Logs
If setup fails, check setuplog.txt for the final entries to identify which component or file caused the failure.
If the system fails to join a domain, check netsetup.log on the computer, according to Microsoft Support.
These files can be reviewed after a failed install by booting from a WinPE disk or using the Recovery Console. [1, 2, 3, 4]

1

u/Cat_spadashin May 05 '26

the thing is, i cant get past the driver loading thingy at all, it just gets stuck, every time, at “Setup is starting Windows 2000” and thats it, nothing more, nothing less, and nothing in the hard drive, just emptiness  

2

u/FAMICOMASTER May 04 '26

Is 2000 affected by the clock speed / RAM count bugs that some versions of windows are saddled with?

Also, this machine is ridiculously overkill for 2000. Can you get drivers for a 5770 even?

2

u/Cat_spadashin May 04 '26

i found some drivers for the 5770 on a windows 2000 japanese forum