Upgrading BX --> 815E running Win2K. Anyone able to do this without reinstall?

Pauli

Senior member
Oct 14, 1999
836
0
0
I am upgrading my Soyo BA6+III Mobo to an MSI 815E Pro. I've seen this topic a few times but no one has answered that they have successfully accomplished this. I really want to avoid a reinstall because it has taken me weeks if not months getting everything the way I want it. A previous post stated that if all of the listed devices in Device Manager are removed prior to changing the Mobo, then it will redetect them properly but the guy didn't actually try it. Has anyone tried this? Thanks.
 

Hanpan

Diamond Member
Aug 17, 2000
4,812
0
0
I tired it once but it just screwed everything up. However this was going from an older to a new via chipset. May work with bx but i'm not sure.

Sorry :(
 

BlueVenus

Member
Nov 9, 1999
101
0
0
Hey Dude,

Pulled this off the newsgroups..have not tried it out myself yet, but will soon, Good Luck

"Before you shutdown your system to install your new motherboard, go into
Device Manager and change the drivers for your IDE controller to "Standard
Dual Channel PCI Controller". This will allow you to boot up with the new
motherboard. Windows 2000 will detect the new controller and load (or prompt
you for) the new IDE drivers.

Remember, you must do this BEFORE you install your new motherboard.
Otherwise you will get the "Inaccessible Boot Device" error.

This works, trust me. I have done it dozens of times."

If you try it..let us know if it works. It seems the trick with Win2K is the IDE controller. I would assume your peripherals will be redetected, so have drivers ready.


-Bung
 

Wik

Platinum Member
Mar 20, 2000
2,284
0
0
I went from a Asus P2B BX board to the MSI 815E Pro and went it to Device manager in safe mode to delete everything I could. I then did the swap and it did not go well, I ended doing a fresh install (planned to do so anyway but had to try)
 

igiveup

Golden Member
Feb 17, 2001
1,066
0
0
One of the other tech guys just replaced his mobo at the office. Hard drive as ok and still had 98 on it. He didn't even delete the items out of Device manager. Just plugged the new mobo in and went with it. All was ok. Not a single problem. The computer will run through a detecting new hardware phase but it was all ok in the end. Who knows how it will go for you, I just know it happened ok this time.
 

Wik

Platinum Member
Mar 20, 2000
2,284
0
0
Win 98 will do it no problem. He is using Win2K though, and it will not do it as easy as 98 does it.

On a side note you can do it with ME also but during the bootup as it is finding new hardware it will freeze up and you will have to end task on a bunch of multiple things and it will keep going. You do this several times as it reboots and it will finally find all the new hardware.
 

vfrjim

Golden Member
Oct 10, 1999
1,281
0
0
You know, there is an article at microsoft about this, don't remember where, you just have to search their knowledge base, but I had a 50-50 experience with what you are about to do, the first time went without a hitch, plug and played EVERYTHING, next time BSOD, so go find the article and follow it.

Jim
 

Pauli

Senior member
Oct 14, 1999
836
0
0
I am going to try what Blue Venus suggested. I couldn't find the reference on MS web site. I also looked into the sysprep utility, but I don't think that is used for this purpose. It's going to take me a few days to get to this but I'll post back to let you know how it turns out.
 

Pauli

Senior member
Oct 14, 1999
836
0
0
Ok, I went with BlueVenus' advice and guess what? It actually worked! Thank God I don't have to reinstall all of my software and tweaks. Thanks everyone!
 

TomBilliodeaux

Senior member
Sep 29, 2000
788
0
0
Pauli,
Can you give us details as to where to find the files or how to do the command for the change settings?
This looks like something that may be usable in the future to many.
 

Pauli

Senior member
Oct 14, 1999
836
0
0
I simply went into Device Manager and changed the IDE driver as detailed in BlueVenus post. I rebooted and everything was re-detected. It took a couple of those automatic reboots to get everything detected.