myne
05-12-05, 08:05 PM
I hate to say it, but I joined this forum simply to flame.
There are MUCH better ways of preparing for a new motherboard.
I personally use 2 methods and no doubt there's a third I havent bothered figuring out yet.
1) Change the IDE driver.
It may suprise you, but when moving to a new motherboard, 95% of the time it will BSOD with a 0x0000007b error, aka "unmountable boot volume" aka "cant find the HDD".
What causes this is the custom chipset specific IDE driver.
Say you move from a VIA mobo to an Nforce mobo, it goes something like this :
Post
Boot menu
Loading
Loads VIA IDE driver
Tries to re-mount HDD
BSOD.
To prevent this, if you have some fore-warning (eg a planned upgrade) all you have to do is go into device manager and change the driver of the IDE controller to a "standard IDE controller" type driver. Here's a very very basic guide I made 2years ago when I went from an MSI k7tturborle to an Epox 8rga+ : http://www.users.on.net/~jvizard/myne/XPmoboUG/
2) Hardware profile upon first bootup
This is really quite simple.
When you first do an install of XP, before you install any programs, drivers, services or anything, you change the IDE driver to a standard one, reboot and make a hardware profile called "clean".
Why is this good?
Well, if your motherboard dies, you can rip out the hdd, stick it in ANY machine, press F8 during bootup and select the "clean" hardware profile and barring any other strange clashes, it should boot fine.
3) Activating the Std driver via Recovery console (this is the method I havent bothered figuring out)
I added this, because perhaps you'd like to figure it out.
The basic premise is that you load recovery console and change the startup registry value for the std ide driver. You'd do this using the very basic registry/service interfaces in recovery console. Last time I tried it, simply enabling the pciide service didnt work, but that could have been for other reasons.
4) Another bsod recovery method that I just threw in because I can
Now, after all that has failed, there's still another option for those rare cases where it's just a corrupted file. This method shouldnt work for 0x0000007b errors.
Load recovery console. Browse to \windows\system32\config\ , copy system, software, security and sam to a new folder that's not in the windows dir, start a repair install, On the first graphical reboot go into safe mode and copy those files back. Sometimes windows will revive exactly as you left it.
Basically all you're doing is backing up the registry, copying fresh new files into the right places and then copying the registry back. Repairs, last time I checked, dont keep all of the registry.
Only after you've done all of that should you give up on the install and do a full repair install.
Anyway, that's my 'flame'. I think your method is a last resort and would never recommend a newbie to do that first off when there's much faster and more elegant methods avaliable.
-myne.
There are MUCH better ways of preparing for a new motherboard.
I personally use 2 methods and no doubt there's a third I havent bothered figuring out yet.
1) Change the IDE driver.
It may suprise you, but when moving to a new motherboard, 95% of the time it will BSOD with a 0x0000007b error, aka "unmountable boot volume" aka "cant find the HDD".
What causes this is the custom chipset specific IDE driver.
Say you move from a VIA mobo to an Nforce mobo, it goes something like this :
Post
Boot menu
Loading
Loads VIA IDE driver
Tries to re-mount HDD
BSOD.
To prevent this, if you have some fore-warning (eg a planned upgrade) all you have to do is go into device manager and change the driver of the IDE controller to a "standard IDE controller" type driver. Here's a very very basic guide I made 2years ago when I went from an MSI k7tturborle to an Epox 8rga+ : http://www.users.on.net/~jvizard/myne/XPmoboUG/
2) Hardware profile upon first bootup
This is really quite simple.
When you first do an install of XP, before you install any programs, drivers, services or anything, you change the IDE driver to a standard one, reboot and make a hardware profile called "clean".
Why is this good?
Well, if your motherboard dies, you can rip out the hdd, stick it in ANY machine, press F8 during bootup and select the "clean" hardware profile and barring any other strange clashes, it should boot fine.
3) Activating the Std driver via Recovery console (this is the method I havent bothered figuring out)
I added this, because perhaps you'd like to figure it out.
The basic premise is that you load recovery console and change the startup registry value for the std ide driver. You'd do this using the very basic registry/service interfaces in recovery console. Last time I tried it, simply enabling the pciide service didnt work, but that could have been for other reasons.
4) Another bsod recovery method that I just threw in because I can
Now, after all that has failed, there's still another option for those rare cases where it's just a corrupted file. This method shouldnt work for 0x0000007b errors.
Load recovery console. Browse to \windows\system32\config\ , copy system, software, security and sam to a new folder that's not in the windows dir, start a repair install, On the first graphical reboot go into safe mode and copy those files back. Sometimes windows will revive exactly as you left it.
Basically all you're doing is backing up the registry, copying fresh new files into the right places and then copying the registry back. Repairs, last time I checked, dont keep all of the registry.
Only after you've done all of that should you give up on the install and do a full repair install.
Anyway, that's my 'flame'. I think your method is a last resort and would never recommend a newbie to do that first off when there's much faster and more elegant methods avaliable.
-myne.