Win2K BSOD with new CUSL2-C mobo - any ideas?

[Wiz]

I got the Asus CUSL2-C mobo yesterday and last night tried to get it hooked up.
I'm typing to you today from my old BX (BH6) system.
I've installed, reinstalled, configured and worked on NT and Win2K a lot of times, so you would think I would have learned a few things by now...
I blame it on this killer head cold I have, but here's the stupid thing I did:
Shut down Win2K normally after a nice uneventful session
Gutted out my computer case - remove BH6 mobo & all cards incl. 2 ISA cards
Mount CUSL2-C mobo
Hook up all cards - except ISA cuz no ISA slots, had extra PCI NIC so I put it in in place of 1 ISA NIC, (this system needs 2 NIC's) no place to put old ISA 56k modem - left it out
Get everything put together and try to power up.
Play with BIOS settings
Set it at 700 mhz (P3 700e) and try to boot.
Blue Screen - 'INACCESSABLE BOOT DEVICE'
futz around with it a bunch, cant boot.

11:45 pm and feeling lousy, went to bed.

11:00 am today I decided to put BH6 board back in while I still remembered the order I had the PCI cards.
Ok, I got it all put back together and it booted fine.
Now I am thinking I need to tell the system I don't have those ISA cards any more, but I am not sure what to do about the different HDD controller in the other mobo. The way I have WIn2K installed is with NTFS so that makes things difficult if it won't boot.
I am thinking about going in and removing devices and then letting the system find new ones next time I boot up with the new mobo.
Of course if that doesn't work it may be unbootable with either system.
I could remove the ABIT HDD controller and install the driver for the ASUS HDD controller then move all hardware back so I am using the new ASUS mobo and see if it boots...
I am not sure so I will wait and see if anyone here has any advice before proceeding. TIA

 

[CAMS]

Ever wonder why Windows 95/98/NT/2000 isn't sold as an image & installed from DOS in 10 Min. Looks like you just found out!

That's what you are effectively doing by not formating and reinstalling with a new motherboard.

 

[Wiz]

Interesting point Cams, however I've found that Win2K can sense changes in it's hardware and load new drivers much better than NT ever did. I think my biggest problem right now is that I changed HDD controllers and the system thinks my old controller is a device it can't boot without.
It can obviously read from the HD otherwise it wouldn't get that far.
I believe at this point I need to install a new copy of WIn2K in a different directory using the new hardware, then once it's up and running copy my 'documents and settings' over from the old install to the new.
This is the path I've chosen at this point in time, so we will see how it works out.
Speaking of installing by image, ever use PowerQuest Drive Image Pro, or Norton's Ghost? Ever do a group install to 2500 workstations using SMS? There are some nice tools available, but changes of hardware make things a bit tricky.
Anyway, thanks for the contribution.