Keeps restarting while installing GUI portion of Win2k

Hey all, I am having trouble installing Win2k Server. Installing the dos part is fine, the problems happens after restarting and when it is detecting the keybord and mouse on the GUI install it restart the pc about half way through and keeps going in that cycle. This is a brand new install I am doing on a AMD duron 900 Mhz and the MB is a Legend Qdi KinetiZ 7B with 256 MB RAM and 20 GB HDD. I know the keyboard and the mouse isn't the problem because I have installed win2k server on another pc a few days ago with the same keyboard and mouse and the installation was smooth.On the same PC I have installed from scratch win 98SE without any problems. I have tried to do a fresh install and an upgrade from win98 and I still get the same thing. I have flashed my BIOS to the most current ver. <IMG SRC="smilies/eek.gif" border="0"> <IMG SRC="smilies/mad.gif" border="0">

I had real troubles with an AGP video card the first time I installed 2k pro. Turns out that I can't use it right now, may have something to do with the MoBo not able to supply enough power to the AGP, or that is the impresion i get from many others that have posted with a similar problem. Try ruling out all hardware problems by removing everything but video. Even try a diferent card (perhaps PCI) just to see what happens. I get the impresion that you have began the setup a few times, did you reformat each time? Using NTFS? It is early yet, I am sure someone will post some more ideas...

it doesn't matter what file system I do it in, Fat32 or MTFS it still does it. I think at this point I have ruled out it's sw or OS related and it is most likely a hw issue, maybe mobo???

I recently had an issue installing Win2k on a workstation that I had no problems installing Win98, it ended up being a memory issue. Try changing out memory with another brand and give it a fresh install <IMG SRC="smilies/smile.gif" border="0">

Check memory, a few other recent posts involve bad RAM. If you suspect a little oxidation or film has built up on the contracts, you may be able to "earase" the film by very gently using an eraser from a pencil on the contacts of the suspect DIMM. I know of 440LX boards having problems powering video cards in win2K, but not installing the OS. Try checking the ram, or even using another DIMM, if possible.
Good Luck.

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!

I let the setup run all night last night and it eventually got through and installed. I think it might be a memory issue as well. I am going to fdisk and swap my mem with another one and try the install again. It didn't matter if I was installing server or Pro, it would keep restarting. <IMG SRC="smilies/biggrin.gif" border="0">

Well I had swapped the memory started over and fdisk and it still keeps restarting during the GUI part of the install of Win2k. Sometimes it gets further through the install, but eventually keeps restarting. I don't know what to do at this point. Any one have any more ideas???

pc config:
Legend QDI Kinetiz 7B Motherboard (already flashed the new Bios)
Duron 900
256 MB ram
20 GB 7200 Maxtor
LG cd-rw
ati expert 2000 agp 32mb RAM
floppy
standard mouse/keyboard

Check the Knowledge Base! Go to the Suport page and search the knowledge base. Put in Windows 2000 as your OS, and Search buy keyword. Put this in as your keywords

kbenv reboots setup


There are plenty of pages here, but if one doesn't match up, trying using some of the other keywords that are listed at the bottom of each article. Find an article that is close to the problem you're having, then do a new search with the keywords from the previous page....

I think I know what the problem might be. The mobo doesn't show up in the HCL

You might check the Power Supply, especially with an AMD processor. Is it AMD certified? At least 300WATTs?

How do I know if it is AMD certified? It is a 300W supply.

Here is the site with the list on it. Just put in your speed and form factor.

when I click on the above link, it gives me this msg
Forbidden
You don't have permission to access /duron/power/ on this server.

Yes, I got the same thing. Can't it tell that I have an AMD? <IMG SRC="smilies/wink.gif" border="0">

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.

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>

---

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.

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: