Hey Ron, i looked in the MS kbase and I couldn't find anything that could relate to me. I think it might be the mobo, because I did load win98SE and it loaded just fine. The win2k HCL didn't have my mobo listed. That could be it right there
Printable View
Hey Ron, i looked in the MS kbase and I couldn't find anything that could relate to me. I think it might be the mobo, because I did load win98SE and it loaded just fine. The win2k HCL didn't have my mobo listed. That could be it right there
Well, there are two possible reasons that the motherboard isn't listed. One is that the motherboard doesn't work with Win2K. and the other is that whoever manufactured your motherboard didn't want to pay to have it tested with Microsoft.
So, I would check the website or some other resource from your motherboard manufacturer to see whether they consider their motherboard compatible with Windows 2000. If they do, consider downloading SP2 and doing an integrated install. There may be a problem with one of your other devices that may have been fixed with a later service pack.
How would I intergrate the sp2 install with the win2k install?
You first need to copy the i386 directory from your Win2K CD to your HD. Then download the network version of the service pack, and run the service pack exe with the
/s:{directory} switch, where {directory} is the name of the directory where you copied the i386 directory to. For instance, if your cdrom was d: and your harddrive was c:, and you copied the i386 directory to c:\i386, then you would need to run (I don't remember the name of the exe for the service pack, but I'll just use sp2.exe)
sp2.exe /s:c:\
If you had copied the i386 directory to c:\win2k\i386 then you would do the integration with
sp2.exe /s:c:\win2k, then run the installation from your harddrive.
I had a similar experience while installing W2K Pro on a workstation. It kept rebooting at the same point over and over just as it was detecting the keyboard.Quote:
Originally posted by Ron Prestenback:
<STRONG>This also sounds like it could be an ACPI issue. If none of the above works, go into your BIOS, and turn off ACPI, reformat *before* you start the setup program. By formatting inside the setup program, it is possible for Windows to keep one or two files (such as boot.ini). It shouldn't be an issue with this, but just to be sure....
Then reinstall. There are some MSKB articles on the types of problems that ACPI can cause. Try the Knowledge base, keyword "Setup". Good Luck!</STRONG>
Ended up being ACPI was turned off in the BIOS. Switched it back on and W2k Pro finished installing without a problem.
Yes, it really all depends on whether your motherboard supports ACPI or not. Windows 2K will detect whether or not you have an ACPI compatible motherboard, and will intall the approprtiate HAL. You will see the same symptoms in either case. BIOS ACPI turned off with a ACPI compat. mb, Win2K will try to install a ACPI HAL. Same thing other way around. Turn on ACPI, but it isn't supported, Win2K will try to install a regular HAL and you will see the same issues. My motherboard manual said my computer was ACPI, but Win2K would intall a regular HAL, and I would get the reboots and lockups and such when I turned it on in the BIOS. I even tried manually selecting the HAL by pressing F5 at the screen where it tells you it is detecting hardware. I chose ACPI compatible computer instead of regular PC, and I had even more problems, so Win2K was correct in choosing with HAL to install. There is a very good Knowledge Base article about this exact thing:
http://support.microsoft.com/support...216573&SD=MSKB
Hey all here's an update. I finally got win2k installed on my new pc. I did what I suspected all along and changed out the mobo. I now have a gigabyte ga-7zmmc and everything loaded up fine without any hiccups. Thanks to all that offered suggestions :) :cool: