blue screen from !@#$ stop error - inaccesible boot disk

[cards]

I just moved my system from an ecsk7s5a to a new msi k7n2 delta-ilsr - problem is my OS is WIN2k and it doesn't like the move - I get the blue screen with the stop error "inaccessable boot disk" - I think that the problem is due to ide controller differences between the 2 boards - some fixes I used beofre (recovery, etc) don't seem to work - someone suggested it was becuase of the onboard raid controller? short of an re-install of win2k does any one have any ideas? I tried running win recovery but that didn't do it -

thanx for any s uggestions

system
msi k7n2 delta ilrs
amd 2400
ati 9600 pro
512 crucial ddr
wd 100 gig HD
etc.

 

[mechBgon]

I recommend reinstalling Windows. If you need to save data off the drive first, put it in another Win2000 or WinXP system as a second drive and stow the data on that computer's boot drive. Now you're free to set up Windows with your new motherboard. Once that's done, put the drive into your "holding tank" computer again and move the data back onto it.

If you are desparate, you could do a Repair, but it sometimes leaves you with a buggy system. If you really want to try that, then boot from your Win2000 CD and start Setup. When it asks if you want to do a fresh install or a Repair, choose the Fresh Install this first time you're asked.

Windows Setup will get ready, then ask you where to install to. Choose the C:\ partition that's already there, and it'll spot the Windows installation in the C:\WINNT folder, and ask if you want that Repaired? and now you say Repair.

Make sure your system's not hooked directly to a broadband Internet connection by a network cable while doing this, because you get a "raw" Windows installation that is easy prey for Internet worms the moment the NIC's driver is installed. Not fun. If you need to get around this Catch-22, click here.

 

[dclive]

Originally posted by: cards
I just moved my system from an ecsk7s5a to a new msi k7n2 delta-ilsr - problem is my OS is WIN2k and it doesn't like the move - I get the blue screen with the stop error "inaccessable boot disk" - I think that the problem is due to ide controller differences between the 2 boards - some fixes I used beofre (recovery, etc) don't seem to work - someone suggested it was becuase of the onboard raid controller? short of an re-install of win2k does any one have any ideas? I tried running win recovery but that didn't do it -

thanx for any s uggestions

system
msi k7n2 delta ilrs
amd 2400
ati 9600 pro
512 crucial ddr
wd 100 gig HD
etc.

There are ways around this - one suggestion was to set your IDE controller to the 'standard IDE controller' built into XP, and then shut down, pop the HDD into the new motherboard, and try booting that way.

Mine's easier, IMHO - install the new MB's IDE controller drivers while on the old MB, and then you'll be fine. The issue with this, though, is that sometimes it will refuse to install from the setup program because it doesn't detect the right hardware type, so sometimes you need to manually mess with it.

 

[23skidoo]

If you go to the Windows 2000 support site at MS and do a search for mergeide.reg you should get a hit for troubleshooting the STOP code you are getting. I'm also posting a thread from another hardware forum where an abbreviated set of instructions for using mergeide.reg are posted by Major Kong. I've used this trick with about an 80% success rate on W2K drives. However it will not work for a RAID partition so if you're running RAID, give it up and reformat your hard drive(s). Here's the Link

 

[KingofFah]

ignoring everything and just going buy the error you gave me.
In my experience, change it back to the ecs mobo and see if it still works. If it does, check your bios settings in the new one. If all looks well rma the board. I've had boards do this before (they also had stability issues and bootup/posting problems sometimes too, but those developed afterwards.)

 

[dclive]

Originally posted by: 23skidoo
If you go to the Windows 2000 support site at MS and do a search for mergeide.reg you should get a hit for troubleshooting the STOP code you are getting. I'm also posting a thread from another hardware forum where an abbreviated set of instructions for using mergeide.reg are posted by Major Kong. I've used this trick with about an 80% success rate on W2K drives. However it will not work for a RAID partition so if you're running RAID, give it up and reformat your hard drive(s). Here's the Link

For a RAID partition it should work just like it works for any other hard drive controller. The RAID controller just gives one volume(however many physical drives that may be) to the computer's BIOS / the Windows OS. That's it. There's no magic there.

One way to avoid the situation is to use a PCI IDE controller, and simply move that from computer to computer with you when you upgrade. Very easy, very fast. Works great, too.

 

[dclive]

Originally posted by: KingofFah
ignoring everything and just going buy the error you gave me.
In my experience, change it back to the ecs mobo and see if it still works. If it does, check your bios settings in the new one. If all looks well rma the board. I've had boards do this before (they also had stability issues and bootup/posting problems sometimes too, but those developed afterwards.)

I strongly disagree with this. This issue has nothing to do with stability.

The problem is that the hard drive controller uses unique drivers, and the old motherboard's hard drive was using other different drivers to access its' hard drive. The computer loads all devices necessary to boot (ie set to 'boot' in the registry) and then looks for the hard disk - it can't find it (because the new motherboard's IDE drivers aren't loaded or set to 'boot' value in the registry) and so it throws up a Stop 7B Inaccessible Boot Device.

 

[cards]

thanx to all for the suggestions - i'll try the merge reg tonite and see if that does it - i thought that the ms site said that proceudre would not work for raid boards but it is worth a try - i have used it before and been successful. if that doesn't work i'll try putting the hardware back on the old ECS MB and loading the new nForce drivers I would prefer avoiding a new install of windows and having to re-install many games and other software.

again thanx much to all for your suggestions

 

[VirtualLarry]

Originally posted by: dclive
One way to avoid the situation is to use a PCI IDE controller, and simply move that from computer to computer with you when you upgrade. Very easy, very fast. Works great, too.

Hey! That's *my* secret.

That method does work well, and is highly recommended. I've moved a multi-boot (Win98se, W2K) system between quite a few different motherboards over the years, and it has never caused any problems.

I put my opticals on the mobo's IDE controller channels.

 

[cards]

eureka! thanx all - i switched back to the old MB; changed the ide controller to the standard dual channel - switched back to the new MB and success! win2k loved it. of course things never end - i added a wintv2000 card; loaded the software and the machine started a continuous rebooting cycle! theat board is history until i find out what's happening there.

 

[dclive]

Originally posted by: cards
eureka! thanx all - i switched back to the old MB; changed the ide controller to the standard dual channel - switched back to the new MB and success! win2k loved it. of course things never end - i added a wintv2000 card; loaded the software and the machine started a continuous rebooting cycle! theat board is history until i find out what's happening there.

Follow these http://forums.anandtech.com/messageview.cfm?catid=32&threadid=1359897&enterthread=y steps, and we can help you with that too. A quick suggestion, though, is just to pop out the WinTV card...