K7s5a pro resets on boot

ihatecomputers2

Honorable
Feb 18, 2012
7
0
10,510
Hello,

I decided to put the MB K7S5A pro into an old 4U case with 10MB Caviar 101AA HDD where Win2000 is already installed.

This HDD will boot another machine I have here.

The K7S5A will boot up to the point where it says "windows 2000
loading". Just as it gets to the point when the monitor should switch to
graphics, the MB resets and it tries to boot again.

I googled around and some people say this MB it sensitive to power issues
like low voltage. The P/S in this case is a small one, 200W, but I'm only
running a video card and the HDD - not even a CDROM. So, I'm not drawing
too much juice, but maybe the PS is low volting enough to trip the MB off.

Does anyone else here have any ideas?
 
It most likely crashes with error 0x0000007b. Was Windows 2000 previously running on a motherboard with the same chipset? If different, what steps did you take to make sure that it would be bootable when moving the hard disk to a system with a different chipset? Did you use MergeIDE?
 

ihatecomputers2

Honorable
Feb 18, 2012
7
0
10,510


> It most likely crashes with error 0x0000007b

hmm, how would I know that?

The old drive with the win2000 installed was/is running on a different MB, a P3. Basically, this is a MB upgrade I'm attempting. I was not aware that there are any special steps I should be taking. I don't know MergeIDE, I'll Google.

I have the restore CDs, but not the original install win2000. There is no vital data on the drive.

The MB ran fine as a server until the HDD died (click click)

the video card is from that same server. Basically, the MB and video is from the server with the dead HDD. The case, P/S and caviar HDD is from the old P3 that I am updating. the CD player is from my junk pile.

Is is possible to reinstall the win2000 from the restore disks? Is there an easier way?

Thanks for your attention,

Shane
 
You should briefly see the error code when it crashes. Since you went from Intel to AMD and the chipsets are different, I'm 100% sure the system crashes with that error.

MergeIDE is from Microsoft, but it's useless if you didn't use it before the old motherboard failed. In other words, you had to prepare your system for a motherboard swap just in case.

You'll need the Win2K CD to reinstall or you'll have to connect the drive to a compatible system and use MergeIDE (this is the easiest way).

Why would you want to use Windows 2000?
 

ihatecomputers2

Honorable
Feb 18, 2012
7
0
10,510
Both motherboards work. I have put the machine back to original configuration and am using it now. I want to improve it by upgrading the MB.

I don't have the OS install disks but I did buy this OS and don't want to pay for another.

Win2000 works OK, why change? I saw what happens when people put a new OS on old hardware. I suppose XP might be a good choice for this old machine, but I don't have a copy.

Still reading up on the MergeIDE utility. Perhaps I can still make this work. hmmm
 

ihatecomputers2

Honorable
Feb 18, 2012
7
0
10,510
I could not find MergeIDE to download. One site had a German version, but not understandable to me.

I found a suggestion to fire up with the old board, use the system manager to select the generic IDE drivers, swap out the board and boot. Still the same problem.

I was able to get a bootable CD Win 2000 install. The machine reports that the CD boot record is good. Then tells me that setup is examining my hardware, but goes no further.

 

ihatecomputers2

Honorable
Feb 18, 2012
7
0
10,510
I'm not getting a blue screen or error message. When booting from the HDD, it gets as far as that progress bar that runs left to right across the bottom of the screen. Then it reaches complete, the board does a hardware reset. I don't see a blue screen, and I get no error message.

Now that I have a win 2000 instal CD, It boots up to the point of "examining your hardware" and it just stops.
 
You can't access the Microsoft link that I provided?

You can find the instructions about 1/3 of the page. It starts with:

1. Copy the following information into Notepad, and then save the file to a floppy disk as Mergeide.reg. (you can save it whever you want.)

Note Make sure that you save the file by using a .reg extension and not a .txt extension.

********* START COPY FROM HERE *************

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires atapi.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00


************ END COPY HERE ***************

EDIT: Make sure that the missing drivers are copied to the drivers directory; otherwise it won't work.
 

ihatecomputers2

Honorable
Feb 18, 2012
7
0
10,510


Yes, thanks for the link. Not sure why I did not find that with google.


I'm already off on another tack though. The local puter geek gave me a Win 2000 install disk.

You see, any important data on the drive has been copied off. This is not a data recovery scenario.

So, I suppose I have a new problem now. The install is hanging.

I can still put the machine back to the old MB and make it work. The CDROM reads OK, I just proved it. I can prove all the h/w except the new MB. that, as I recall, was working fine when working serving i'net stuffs with freeBSD 5

Perhaps I should try the IDE jumped to cable select instead of master.

Don't you just love computers?
 

ihatecomputers2

Honorable
Feb 18, 2012
7
0
10,510
After spending far too much time, I have solved this.

The results of trying to boot or run the install were variable. The few times I did get an error, I noted them and did some googling. The one consistent thing about the errors was reference to a file on the instal disk "arcdisp.c"

An unexpected error has occurred. (536821760) occurred at line 1768 in D:\xpclient\base\boot\setup\arcdisp.c

Some reading showed me that Win 2000 makes a ramdisk for use during install. I should have realized earlier that variable errors was often the fault of RAM.

Well, lucky for me, the RAM seems OK, but the loose connection must be in the socket. When I moved the SIMM to the other slot, the machine booted up to the generic IDE drivers.

After that, I needed to set up some drivers to get things right and I'm happy to say the rig is doing it's thing OK now.

Thanks to GhislainG for his help on this. I hope this thread might save another soul time.

Don't overlook a bad SIMM socket when hunting down weird boot problems.