Got the new MoBo, now having some teething trouble

[prophet]

The motherboard chipset is the main factor in problems booting the operating system after a switch.

Its far easier to upgrade a motherboard that has a via chipset to a via chipset, or nforce to nforce, or intel to intel etc. going from sis to nforce or via to intel etc is going to obviously present problems.

Going to the extreme of reinstalling your OS just because of driver issues is a bit on the slack side (something a novice might do). For future reference, those novices might want to remember this tip.

When upgrading/replacing/switching (whatever) your motherboard, the first thing you should do is go to device manager, uninstall any drivers relating to your motherboard & install your new motherboards drivers. then shut down the machine, switch boards, reboot. then reinstall the new motherboards drivers again.

So if your stuck at the moment, your simplest option might be to just switch motherboards back, reboot, and do the above before switching back to your new motherboard.

But you could also try booting to safe mode and doing the above.

or as a last resort (theres always a last resort before formatting, besides what can you lose?) you could try a repair install (in place upgrade)

simply pop in your os disk and reinstall. it will only overwrite your current os files, nothing else. If your using xp or 2000, boot to disk, at first R for repair skip that, but at second R choose that. (for more detailed instructions just google in place upgrade, or go to microsoft knowledgebase)

all other os's just boot to disk and install

hope this helps.

(if you still get blue screen stop errors, go into device manager and uninstall everything to avoid any driver conflicts) but you should then do an inplace upgrade.

[progfusion74]

prophet,

Thanks for the advice. I will give it a shot. My old motherboard is dead, hence the new one, so I will have to try the safe mode option. I might upgrade anyway while I am at it.

Cheers

prog

[DevonB]

99.9% promise you that won't work either. That error is a driver issue for the disk controller. The driver is missing, and it won't load properly until he gets it in there right. You're better off reloading the OS.

It has worked for me a number of times, including on serial ATA drives on a PCI SATA controller where the drivers for the SATA controller weren't installed on the OS. I would at least put the chances of it working > 0.01% from my experience.

progfusion74, IMO, your OS and apps can be on the same partition, however, your data, (docs and song files etc.) should be on another partition or ideally another drive.

So you actually replaced the controller, and put the boot drive on a new controller that the OS didn't know about? Certainly not something typical. I'm not referring to taking a standard IDE drive and putting it on a standard controller, then moving that drive to a new motherboard/system. Standard IDE controller ususually don't freak it out, but a SCSI RAID or SATA might.

Devon

[DevonB]

Its far easier to upgrade a motherboard that has a via chipset to a via chipset, or nforce to nforce, or intel to intel etc. going from sis to nforce or via to intel etc is going to obviously present problems.

I had a drive I flipped around between a few motherboards with Win95, and you did get weird problems like everything came up triple in System tree for the motherboard in Device Mangler. WinXP I've noticed has been MUCH more graceful with the switch and doing nothing, and actually have had no issue flopping stuff around. As long as I had my XP CD sitting right there along with new mobo drivers...

But, sometimes just doing a clean install is preferable to clean out all the 'crud' on your machine. I've had my Windows directory shrink by over a gig after a reinstall.

Devon

[progfusion74]

But, sometimes just doing a clean install is preferable to clean out all the 'crud' on your machine. I've had my Windows directory shrink by over a gig after a reinstall.

Devon

That's one reason I am leaning towards a clean install. I can do a cleaner installation, and I was planning to upgrade to XP next year anyway, why not do it now. I can clean up my original boot disk in the process as well.

I just tried a safe mode bootup. No luck.

Cheers

prog

[cold c]

So you actually replaced the controller, and put the boot drive on a new controller that the OS didn't know about? Certainly not something typical. I'm not referring to taking a standard IDE drive and putting it on a standard controller, then moving that drive to a new motherboard/system. Standard IDE controller ususually don't freak it out, but a SCSI RAID or SATA might.

I've done that for IDE ATA drives (various times) and also (on one occasion) for a drive moved to a SATA PCI controller using the same method (also mirroring from an IDE ATA drive on a serillel adapter to a native SATA drive, then removing the old drive). These would have been mainly on installations of XP or possibly Windows 2003 Server. I've also switched an installation from a VIA chipset to nforce2 without too many problems, but that was on XP again.

I just tried a safe mode bootup. No luck.

As others have mentioned, win2K is more sensitive to switching. As prophet says, the repair mode could help, or see this link for the differences between XP pro and home (and pro also supports multiple processors).

[prophet]

before formatting, you could also use the files and settings transfer wizard that comes on the xp disk.

This will allow you to basically transfer everything over (except for programs but your going to be reinstalling them anyway)

this is a quick way of getting things back to the way they were before you wiped the hard drive. ie. internet connection settings, network settings, favourites, docs & settings, pretty much anything you want.

its always handy to do backups of these every now and again.

but who actually ever gets round to backing up anyway?

[DevonB]

This will allow you to basically transfer everything over (except for programs but your going to be reinstalling them anyway)

this is a quick way of getting things back to the way they were before you wiped the hard drive. ie. internet connection settings, network settings, favourites, docs & settings, pretty much anything you want.

Out of someone else's experience, I've heard it works well too.

but who actually ever gets round to backing up anyway?

You only need to back up what's important to you, if you don't i guess it wasn't important, huh?

Devon

[DevonB]

So you actually replaced the controller, and put the boot drive on a new controller that the OS didn't know about? Certainly not something typical. I'm not referring to taking a standard IDE drive and putting it on a standard controller, then moving that drive to a new motherboard/system. Standard IDE controller ususually don't freak it out, but a SCSI RAID or SATA might.

I've done that for IDE ATA drives (various times) and also (on one occasion) for a drive moved to a SATA PCI controller using the same method (also mirroring from an IDE ATA drive on a serillel adapter to a native SATA drive, then removing the old drive). These would have been mainly on installations of XP or possibly Windows 2003 Server. I've also switched an installation from a VIA chipset to nforce2 without too many problems, but that was on XP again.

Just to clarify (I'm sure you know I like to keep on top of all this stuff. )

You moved an IDE drive from an imbedded IDE controller to another imbedded IDE controller? That I would expect it to work, unless it was like the boards that come with RAID IDE ports directly in the board.

I'm mainly referring to when you move from one type of controller to another. Such as you buy a new brand of SCSI controller and just move the drives over (LSI Logic chips to Adaptec for example). Or if you move from EIDE to SATA controller. Thinking about it, since SATA is completely backwards compatible, that should work, provided the controller doesn't need specific drivers to function. I just want to be clear for my own sanity and helping others on these threads too.

Devon

[cold c]

Just to clarify (I'm sure you know I like to keep on top of all this stuff. )

You moved an IDE drive from an imbedded IDE controller to another imbedded IDE controller? That I would expect it to work, unless it was like the boards that come with RAID IDE ports directly in the board.

Yes, I have moved installations on IDE ATA drives (on chipset embedded controller) from one machine to another machine's IDE ATA controller (also embedded on motherboard chipset). I have also moved installations between motherboards RAID ports (on motherboards that were using 3rd party RAID contollers, on the motherboard but not integrated into the chipset) succesfully.

It worked moving an IDE ATA drive from and integrated IDE ATA controller to a PCI SATA. The contoller was a Silicon Image SATA controller and I installed the drivers for the PCI card after booting in safe mode.

I'm mainly referring to when you move from one type of controller to another. Such as you buy a new brand of SCSI controller and just move the drives over (LSI Logic chips to Adaptec for example). Or if you move from EIDE to SATA controller. Thinking about it, since SATA is completely backwards compatible, that should work, provided the controller doesn't need specific drivers to function. I just want to be clear for my own sanity and helping others on these threads too.

I've never tried it with SCSI drives moving between controllers, I don't have that kind of hardware in any of my machines unfortunately. I don't know if there is a SCSI equivalent of the "Standard Dual-Channel PCI IDE Controller" in Windows? Probably not.

[progfusion74]

I've never had much luck doing a mobo swap on Win2000 when trying to keep the O/S intact, for either server or desktop. Eventually I learned to just keep regular backups and do a full clean O/S install...less grief in general.

I have been lazy with backups. So I am going to go in from scratch and do a clean install of XP on a new drive. Gives me an excuse to go XP. After making sure all my older files are safe, I am going to clean my original OS drive, and use it for now music project data.

Going to get a DVD-RW (man they have become cheap), and HOPEFULLY, do some routine backups.

The suckiest part is reinstalling all my software and re-authorizing it.

[whyterabbyt]

prophet quoth

Going to the extreme of reinstalling your OS just because of driver issues is a bit on the slack side (something a novice might do). For future reference, those novices might want to remember this tip.

Ummm, no. Doing a clean reinstallation of the OS after swapping a motherboard is a perfectly reasonable option, and I dont particularly consider myself a novice.

Its far less problematic to do a fresh reinstall from a slipstreamed disk, and you ensure that there are definitely no issues with old/unneeded drivers, and as a side-effect you clear out any cruft and crap from the system. In computer lab setups, that's actually a bonus.

When upgrading/replacing/switching (whatever) your motherboard, the first thing you should do is go to device manager, uninstall any drivers relating to your motherboard & install your new motherboards drivers. then shut down the machine, switch boards, reboot. then reinstall the new motherboards drivers again.

This isnt 100% foolproof, and in my experience of running labs of W2K systems, I really dont think its the best solution.