How to: Upgrade your motherboard without reinstalling Windows.

[bob4432]

Originally posted by: dclive

Originally posted by: bob4432
dclive - in regards to sysrep and the way you suggest for a motherboard/system upgrade, how would i know if i have the same hal as the new hardware uses?

On the installed systems, you can look under Device Manager, Computer. If, under computer, it says exactly the same thing on new and old, you're fine. If not, you may need to do the repair install.

Either way, just try it. Most modern systems these days have the same/compatible HAL.

ok, i am not updating currently but have a question. my current system is a 2.8C which is HT, so the HAL used says ACPI Multiprocessor PC. now if i went to a a64 single core(not that it matters but either a venice or diego core), would i be f*cked with the sysrep way? in the past i have had bad luck with repairs, although they did work, the machine seemed to be very slow afterward.

 

[dclive]

Originally posted by: bob4432

Originally posted by: dclive

Originally posted by: bob4432
dclive - in regards to sysrep and the way you suggest for a motherboard/system upgrade, how would i know if i have the same hal as the new hardware uses?

On the installed systems, you can look under Device Manager, Computer. If, under computer, it says exactly the same thing on new and old, you're fine. If not, you may need to do the repair install.

Either way, just try it. Most modern systems these days have the same/compatible HAL.

ok, i am not updating currently but have a question. my current system is a 2.8C which is HT, so the HAL used says ACPI Multiprocessor PC. now if i went to a a64 single core(not that it matters but either a venice or diego core), would i be f*cked with the sysrep way? in the past i have had bad luck with repairs, although they did work, the machine seemed to be very slow afterward.

http://support.microsoft.com/?kbid=309283 points out what's compatible and what's not.

 

[LiLithTecH]

Originally posted by: bob4432

Originally posted by: dclive

Originally posted by: bob4432
dclive - in regards to sysrep and the way you suggest for a motherboard/system upgrade, how would i know if i have the same hal as the new hardware uses?

On the installed systems, you can look under Device Manager, Computer. If, under computer, it says exactly the same thing on new and old, you're fine. If not, you may need to do the repair install.

Either way, just try it. Most modern systems these days have the same/compatible HAL.

ok, i am not updating currently but have a question. my current system is a 2.8C which is HT, so the HAL used says ACPI Multiprocessor PC. now if i went to a a64 single core(not that it matters but either a venice or diego core), would i be f*cked with the sysrep way? in the past i have had bad luck with repairs, although they did work, the machine seemed to be very slow afterward.

You cannot go from an INTEL platform to a AMD platform, even with SYSPREP.

 

[dclive]

Originally posted by: LiLithTecH

ok, i am not updating currently but have a question. my current system is a 2.8C which is HT, so the HAL used says ACPI Multiprocessor PC. now if i went to a a64 single core(not that it matters but either a venice or diego core), would i be f*cked with the sysrep way? in the past i have had bad luck with repairs, although they did work, the machine seemed to be very slow afterward.

You cannot go from an INTEL platform to a AMD platform, even with SYSPREP.[/quote]

That's absolutely, completely, and wholly false.

As long as the HALs are compatible, you can move between processors at will. The only difficulty you may run across is the hard drive controller, but that's true of any CPUs, and can easily be fixed in a variety of ways (I've already mentioned one way).

Sysprep isn't required, and doesn't really buy you anything for one-off moves. I don't see why people bring Sysprep into this - again, for one-off moves.

Again, you can easily go from Intel to AMD and back without issues, as long as the HAL is compatible (see the link above for info on the HAL).

Yes, I've read http://support.microsoft.com/default.aspx?scid=kb;en-us;828287. I've also done the switches in real life; it works.

 

[bob4432]

Originally posted by: dclive

Originally posted by: LiLithTecH

ok, i am not updating currently but have a question. my current system is a 2.8C which is HT, so the HAL used says ACPI Multiprocessor PC. now if i went to a a64 single core(not that it matters but either a venice or diego core), would i be f*cked with the sysrep way? in the past i have had bad luck with repairs, although they did work, the machine seemed to be very slow afterward.

You cannot go from an INTEL platform to a AMD platform, even with SYSPREP.

That's absolutely, completely, and wholly false.

As long as the HALs are compatible, you can move between processors at will. The only difficulty you may run across is the hard drive controller, but that's true of any CPUs, and can easily be fixed in a variety of ways (I've already mentioned one way).

Sysprep isn't required, and doesn't really buy you anything for one-off moves. I don't see why people bring Sysprep into this - again, for one-off moves.

Again, you can easily go from Intel to AMD and back without issues, as long as the HAL is compatible (see the link above for info on the HAL).

Yes, I've read http://support.microsoft.com/default.aspx?scid=kb;en-us;828287. I've also done the switches in real life; it works.[/quote]

since i am running a scsi system drive and regular pata storage drive, does this make it easier? would using a onboard sata raid 1 option create a whole lot of problems?

 

[dclive]

SCSI PCI cards make it easier - just take the PCI card out of your old system, put it in the new one, and see if you can boot. Obviously, that will eliminate any HDD controller driver issues, and so the only remaining no-boot issue would be the HAL. If you can't boot then, you're looking at a HAL difference, and hence a repair-install.

(Easiest way to do that: Put HDD back into old system, start XP install with XP media (slipstreamed with SP2 if you're already running SP2), and after the very first reboot, put the PCI card and HDD into the new PC and let it install from there.)

It's all really very easy. The people that tell you you can't move between motherboards are absolutely wrong, with no ifs, ands, or buts.

Edit: And yes, booting from an onboard SATA RAID setup would cause issues, because anytime you move a motherboard-integrated RAID controller to another machine, you're going to have to completely reconstruct your RAID array unless the new motherboard is compatible with the old motherboard's RAID setup, which most won't be. But that has nothing to do with Windows at all - the same issue would be present if the OS was Linux.

 

[vailr]

After swapping a HD with an XP installation to a new motherboard, the (now non-existent)
previously installed Device Manager devices can be cleaned out by:

Start/Run/cmd
type:
set devmgr_show_nonpresent_devices=1 [Enter]
start devmgmt.msc [Enter]
View/Show hidden devices

Click each of the "+" signs, to expand the device listings.
Then, uninstall any "greyed-out" devices.
This should restore the Device Manager portion of the registry to a "good as new" condition.

 

[dclive]

When I'm swapping hardware around, I don't remove any of that, so that if I want to put the HDDs back into the old machine (or into a similar new machine) I can do so even easier.

 

[Phoenix86]

Originally posted by: LiLithTecH

Originally posted by: bob4432

Originally posted by: dclive

Originally posted by: bob4432
dclive - in regards to sysrep and the way you suggest for a motherboard/system upgrade, how would i know if i have the same hal as the new hardware uses?

On the installed systems, you can look under Device Manager, Computer. If, under computer, it says exactly the same thing on new and old, you're fine. If not, you may need to do the repair install.

Either way, just try it. Most modern systems these days have the same/compatible HAL.

ok, i am not updating currently but have a question. my current system is a 2.8C which is HT, so the HAL used says ACPI Multiprocessor PC. now if i went to a a64 single core(not that it matters but either a venice or diego core), would i be f*cked with the sysrep way? in the past i have had bad luck with repairs, although they did work, the machine seemed to be very slow afterward.

You cannot go from an INTEL platform to a AMD platform, even with SYSPREP.

That is completely incorrect. You *CAN* go from Intel to AMD, as long as the HALs are compatible (very common on newer systems), as dclive said.

dclive, I would hardly say this is method is not necessary. First off it's a "supported" method vs the controller trick. Second, it's very usefull when taking the next step of learning, creating images. This tool is going to be used as the Vista installer, ain't going to hurt to learn the process now. Also, since Vista will have Ximage, you can make your own images w/o 3rd party imaging software.

At any rate, there are a few issues with the controller trick that doesn't affect sysprep, though I don't recall the details. I have been using sysprep for some time.

edit: I'll see if I can dig up the differences in sysprep vs. the controller trick.
edit2: Oh, give me some time, going to be a busy work week.

 

[dclive]

Originally posted by: Phoenix86

Originally posted by: LiLithTecH
You cannot go from an INTEL platform to a AMD platform, even with SYSPREP.

That is completely incorrect. You *CAN* go from Intel to AMD, as long as the HALs are compatible (very common on newer systems), as dclive said.

dclive, I would hardly say this is method is not necessary. First off it's a "supported" method vs the controller trick. Second, it's very usefull when taking the next step of learning, creating images. This tool is going to be used as the Vista installer, ain't going to hurt to learn the process now. Also, since Vista will have Ximage, you can make your own images w/o 3rd party imaging software.

At any rate, there are a few issues with the controller trick that doesn't affect sysprep, though I don't recall the details. I have been using sysprep for some time.

edit: I'll see if I can dig up the differences in sysprep vs. the controller trick.
edit2: Oh, give me some time, going to be a busy work week.

For making images, sure. But I've been clear - for one off changes, I don't see a point in sysprep.

And even with Sysprep, you can still get caught with the HDD controller issue. You have to use the Sysprep /bmsd switch, and frankly, that's too much trouble for one-offs.

 

[Phoenix86]

Originally posted by: dcliveBut I've been clear - for one off changes, I don't see a point in sysprep.

It's supported. I can call MS (granted, who does this very often) and they will listed. However when you *do* need to call them it's usualy important.

Really I'm not *too* interested in what method you use, this is just another tool in the bag of tricks. Thanks for the insight in the thread.

 

[dclive]

Originally posted by: Phoenix86

Originally posted by: dcliveBut I've been clear - for one off changes, I don't see a point in sysprep.

It's supported. I can call MS (granted, who does this very often) and they will listed. However when you *do* need to call them it's usualy important.

Really I'm not *too* interested in what method you use, this is just another tool in the bag of tricks. Thanks for the insight in the thread.

No one would call and pay $245 or use a premier support incident to move from one PC to another. Again, emphasis: one-off.

I *like* Sysprep - don't let anyone get the impression I don't - it's a wonderful tool. But for just going from home PC A to home PC B, it's massive overkill, IMHO.

 

[Phoenix86]

Originally posted by: dclive
No one would call and pay $245 or use a premier support incident to move from one PC to another. Again, emphasis: one-off.

I *like* Sysprep - don't let anyone get the impression I don't - it's a wonderful tool. But for just going from home PC A to home PC B, it's massive overkill, IMHO.

What's funny is, I wrote that article in response to someone doing a repair install to do the same thing. I thought that was overkill. :beer:

 

[dclive]

Originally posted by: Phoenix86

Originally posted by: dclive
No one would call and pay $245 or use a premier support incident to move from one PC to another. Again, emphasis: one-off.

I *like* Sysprep - don't let anyone get the impression I don't - it's a wonderful tool. But for just going from home PC A to home PC B, it's massive overkill, IMHO.

What's funny is, I wrote that article in response to someone doing a repair install to do the same thing. I thought that was overkill. :beer:

Agreed - it is. But you'll still need to do the repair install step if the HAL is different.

 

[bob4432]

Originally posted by: dclive

Originally posted by: Phoenix86

Originally posted by: dclive
No one would call and pay $245 or use a premier support incident to move from one PC to another. Again, emphasis: one-off.

I *like* Sysprep - don't let anyone get the impression I don't - it's a wonderful tool. But for just going from home PC A to home PC B, it's massive overkill, IMHO.

What's funny is, I wrote that article in response to someone doing a repair install to do the same thing. I thought that was overkill. :beer:

Agreed - it is. But you'll still need to do the repair install step if the HAL is different.

when will the HAL be different? would it be if i were to take my wife's machine which is a iwill kt266 m/b w/ 1GHz Athlon and move the hdd to my machine? or am i way off with this thinking?

 

[dclive]

Originally posted by: bob4432

Originally posted by: dclive
Agreed - it is. But you'll still need to do the repair install step if the HAL is different.

when will the HAL be different? would it be if i were to take my wife's machine which is a iwill kt266 m/b w/ 1GHz Athlon and move the hdd to my machine? or am i way off with this thinking?

Look on both machines, then look on this chart and see if they're compatible:

http://support.microsoft.com/?kbid=309283 points out what's compatible and what's not.

 

[Mountainbiker54]

I'm really not sure I know what to do to help myself but I'm sure you do. My motherboard is dead... it got fried the other day. I have a new one on its way, but I have no idea how to keep my current install since I have no way to boot up my system with my old board, and what makes matters worse I have a RAID-0 with a WDC SATA raid card. Is there anything I can do to fix my problem or am I totaly screwed? Thanks

 

[dclive]

Originally posted by: Mountainbiker54
I'm really not sure I know what to do to help myself but I'm sure you do. My motherboard is dead... it got fried the other day. I have a new one on its way, but I have no idea how to keep my current install since I have no way to boot up my system with my old board, and what makes matters worse I have a RAID-0 with a WDC SATA raid card. Is there anything I can do to fix my problem or am I totaly screwed? Thanks

RAID0? Not the same RAID0 on the new motherboard? You won't even be able to look at your data - the data is unrecoverable with your current hardware.

That's why I don't like integrated RAID (aside from server hardware, naturally.)

 

[birdpup]

I do not have experience recovering data from a RAID array but at least two companies boast the ability to recover data from damaged RAID arrays. The two products I am aware of are R-Studio and GetDataBack.

Hard Drive, Partition, Data Recovery and Diagnostic Resources

[*]Data Recovery Programs

• TestDisk
• R-Studio
• Runtime's GetDataBack
• Ontrack's Easy Recovery Pro
• Quetek
• File Scavenger
• HDD Regenerator
• Freeware Data Recovery Tools
• ACR Data Recovery
• Digital Camera Memory Recovery: PC Inspector

Please let us know if you successfully recover your data. Thanks.

 

[Mountainbiker54]

Originally posted by: dclive

Originally posted by: Mountainbiker54
I'm really not sure I know what to do to help myself but I'm sure you do. My motherboard is dead... it got fried the other day. I have a new one on its way, but I have no idea how to keep my current install since I have no way to boot up my system with my old board, and what makes matters worse I have a RAID-0 with a WDC SATA raid card. Is there anything I can do to fix my problem or am I totaly screwed? Thanks

RAID0? Not the same RAID0 on the new motherboard? You won't even be able to look at your data - the data is unrecoverable with your current hardware.

That's why I don't like integrated RAID (aside from server hardware, naturally.)

Its not intergrated, it on a Western Digital SATA Raid Card (one that goes into a PCI slot)

 

[dclive]

Originally posted by: birdpup
I do not have experience recovering data from a RAID array but at least two companies boast the ability to recover data from damaged RAID arrays. The two products I am aware of are R-Studio and GetDataBack.

Hard Drive, Partition, Data Recovery and Diagnostic Resources

[*]Data Recovery Programs

• TestDisk
• R-Studio
• Runtime's GetDataBack
• Ontrack's Easy Recovery Pro
• Quetek
• File Scavenger
• HDD Regenerator
• Freeware Data Recovery Tools
• ACR Data Recovery
• Digital Camera Memory Recovery: PC Inspector

Please let us know if you successfully recover your data. Thanks.

In this scenario, which a later poster suggested wasn't correct since it's an add-in card, he certainly could pay for a service (and be out a few hundred to a few thousand dollars), but it's much easier just to use another integrated motherboard of the same type (ie same integrated RAID controller) to get the data back.

Software recovery methods won't do it.

 

[dclive]

Originally posted by: Mountainbiker54

Originally posted by: dclive

Originally posted by: Mountainbiker54
I'm really not sure I know what to do to help myself but I'm sure you do. My motherboard is dead... it got fried the other day. I have a new one on its way, but I have no idea how to keep my current install since I have no way to boot up my system with my old board, and what makes matters worse I have a RAID-0 with a WDC SATA raid card. Is there anything I can do to fix my problem or am I totaly screwed? Thanks

RAID0? Not the same RAID0 on the new motherboard? You won't even be able to look at your data - the data is unrecoverable with your current hardware.

That's why I don't like integrated RAID (aside from server hardware, naturally.)

Its not intergrated, it on a Western Digital SATA Raid Card (one that goes into a PCI slot)

Then the card can move from machine to machine and you'll have no HDD controller bootup woes or issues whatsoever.

 

[macknattack]

Well I've been reading this thread in preparation for exchanging out my optionless mobo for a new/better one.

I finally swapped it out last night and have not had a single moment of happiness since.

I did NOT use sysprep based on the responses in this forum (now wishing i had). I simply changed the HDD controller in windows as suggested above, turned off the computer and installed the new mobo.

When I turned the system back on, I needed to intall my SATA drivers from floppy out of F6, all was ok. The bios recognized the SATA drive (this isnt a RAID array) and proceeded to boot to windows. HERE IS WHERE ALL H*LL BREAKS LOOSE.

Windows begins to boot, then crashes with this error message:

PAGE_FAULT_IN_NONPAGED_AREA

It then makes some suggestions as for settings to change, try safe mode, blah blah blah.

At the bottom of the BSOD I get this:

SIWINACC.SYS address F7C42000 base at F7C42000

I've tried everything in my little brain that I know about to fix this.

- Reinstall the sata drivers
- Install the NEWEST drivers from the ABIT website
- Run a windows repair through the repair option
- Run a windows repair through the install option
- Change BIOS settings to try and aleve the BSOD

Nothing is working. Im fairly disappointed that these problems have come about after reading this thread. I really REALLY would appreciate any suggestions for help at this point. Windows will not boot into safe mode, data logging mode, etc etc.

My system is an Athlon Socket 754 with an Abit KV8 Pro motherboard. All components were in my old Gigabye NFORCE3 150 mobo for 2 years so I don't think I have any hardware issues. If it was the mobo I wouldnt expect Windows to boot and crash with the same error each time. The OS is XP Pro with SP2 isntalled.

Im hoping for a miracle here, please advise.

Sincerely,

Mack


UPDATE:

I created another XP install on a fresh drive and it installed just fine. Is there any way I can transfer all the system parameters over from the new install onto my old partition? Maybe that is logistically impossible. But I can now access the bad (old) windows directories and make whatever changes you all might suggest.

 

[Phoenix86]

macknattack,

At this point you are best off ditching the old install. You have a new install up and running, go with it. In moving some data over from the previous install, you might move part of the issues you were having.

As far as what method to use, look at it this way. Sysprep is made by microsoft to do this task. It's supported by MS. It's used in many-many-many corporations to deploy thier images. Vista is slated to use sysprep+ximage as it's default setup process, the same way the many-many-many corporations deploy their images (tried and true working method).

 

[macknattack]

Pheonix,

Yes I really missed the boat not using the sysprep... lesson learned for sure.

I did manage to get into the old install removing some files out of the windows directory (I believe all my problems are driver based sata issues). So I was able to get in and install all the new drivers for my new Mobo.

System is running with a few problems with windows hanging at startup for about a minute and other issues. I guess Im not going to give up just yet on this old install, we'll see how it runs after some house cleaning and installing all the windows updates (yes I did a painful repair). But I am online and the system is running for the most part.

Thanks for everyone's advise. I'll be back if I can isolate any more issues and am looking for answers.

Note to anyone reading this - Use sysprep, at worst it could just be overkill. Most likely it will save you a day in your life (at least). I wish I did.

- Mack