New mobo, now Win2k = inaccessable boot disk

[SonicTron]

Ok, I'm assuming this has something to do with the Win2k drivers for the new mobo not being installed. The problemo is that I had this boot drive on a promise ATA100 controller (built into a BE6-II) and I transferred this drive to my new mobo (K7S5A) and now I get the boot disk error (blue screen with stars and stuff).

Soooo, is there any way to fix this?? Will a re-install of Win2k be fine?

I would like to keep it as easy as possible, and reinstalling is on my harder things to do list !

 

[igowerf]

I always format when I switch motherboards. People say that if you uninstall all of the motherboard components before you switch the hard drive over, it will work. Window will detect everything on the new motherboard and allow you to install drivers. I've never tried this before but it might work for you.

 

[SonicTron]

Ok I threw the drive into another machine, and I was hoping someone could tell me what I could delete in order to force the system to re-detect all devices and such so I can boot up and load the new drivers.

 

[igowerf]

I would uninstal everything in the device manager and have it all be redetected.

 

[Raincity]

Your HAL is all screwed up Now along with the boot.ini . A simple reinstall over the existing Win2K install will fix you right up and existing data will still be intact.

Rain

 

[SonicTron]

oops lol no turning back now, started a format

oh well I think after all the hardware testing I did, it was time to re-complete the circle

 

[Heisenberg]

My experience has been that Win2k does not like hardware changes. When I added memory, it told me my Zip drive was bad (it's not)and would not boot. Then when I pulled some memory out recently it gave me the inaccessable boot device BSOD. I ended up reformatting.