Archived from groups: alt.comp.periphs.mainboard.asus (
More info?)
_R wrote:
> On Wed, 06 Apr 2005 04:24:15 -0400, nospam@needed.com (Paul) wrote:
>
>
>>In article <o0l651lhi0f6v50ktv93nn9kjlr017onlh@4ax.com>, _R
>><_R@nomail.org> wrote:
>
>
>>With XP, there are two aspects to the migration - Activation
>>and Enumeration.
>>
>>Activation is MS's effort to prevent piracy. You will find
>>various descriptions on the net, for how much of a hardware
>>change the OS will tolerate, before it requests that you
>>re-activate the installed OS.
>
>
> Hi Paul, This is exactly what I was looking for. In fact, I
> would have forgotten an important step if you hadn't jogged
> my memory.
>
> (continued)...
>
>
>>One thing I discovered (via Google search), was the importance
>>of the disk driver handoff at boot time. The BIOS INT13 routines,
>>are what is used to fetch the initial data from the disk. At
>>some point, Windows will try to use its own drivers to fetch
>>data. If the new Southbridge looks nothing like the old
>>Southbridge, or you moved your boot disk to a non-Southbridge
>>IDE controller (like a Promise chip), then it is highly unlikely
>>the boot disk will have a driver for the new hardware.
>
>
> I'm moving from a P4TE w Rambus to P4C800-E with Northwood
> and dual channel DDR. I was hoping that would not be enough
> of an upset in itself. If so, I'll need to reinstall.
>
I recently moved from a P4T-E to a P5P800 and had no problems with the
conversion. I just installed the new motherboard, did a repair install,
and installed the drivers. I originally used the onboard NIC with the
new board but swapped it out later for the old NIC from the P4T-E. I
kept the same hard drive and video card so that may have made the
conversion easier.
I did not have to reactivate Windows until I upgraded the CDRW to a DVD
burner.
> I am building the new system in a new case, with a new drive.
> Everything will be incremental and parallel when possible. I
> installed Gigabit Lan, identical video cards, and identical aux
> ATA cards. The NIC may be a major one, so I've installed a
> NIC card in the P4TE. The P4C800 has NIC hardware onboard,
> but I'll move the old NIC card to the new system along with the
> new drive for first boot. At least it will have a familiar MAC
> address (that may be a major one).
>
> I currently run the system (C, D) partitions from the mainboard
> ATA controller, but now that you mention it, there may be some
> problems. I was thinking that the ATA controllers would be
> fairly generic and compatible, but you're right; that's probably
> not a valid assumption.
>
> I already run an aux ATA controller card, so maybe I'll switch
> the boot to that card temporarily. Then mirror the boot partition
> (on the old system), install an identical ATA card in the new system,
> move the new drive over, and hope she boots from it.
>
> I can switch the drive back to the motherboard ATA ctlr later
> after the system has settled in.
>
>
>>Since I don't own or use WinXP (I refuse to own an OS that
>>requires a phone call to get it to work),
>
>
> You're running Linux?
>
> MS is apparently going to enforce SP2 for dial-in software
> updates as of Apr 12. Anyone who is paranoid about SP2
> (like me) may want to do an update before that.
>
> It's often Microsoft's best customers that get bit with this stuff.
> I've spoken to people who had no access to their keys for
> [word/excell/whatever] when the software decided to ask
> for them. Plane flights, business trips, etc.
>
> Musicians (a world plagued by dongles) often buy the software,
> then find a hacked version to bypass the silly dongle. Ironically
> it's usually more reliable than the legit code *with* the dongle.
> I had to turn on my HP printer every time I wanted to use Cubase.
> The parallel port dongle would get confused if its external lines
> were not powered up.
>
>
>>You can also do yourself another favor, and while the disk
>>is connected to the old computer, uninstall the old video
>>driver(s), and other custom sound hardware drivers from the
>>old system.
>
>
> I have two identical video boards for that. I'll be keeping
> the old system around, but swapping stuff incrementally
> before the final move. I was going to leave the sound card
> drivers and others intact and remove them after the new
> system installs its own.
>
> I'd love to know how MS gauges hardware changes. I
> changed a NIC card without XP complaints. I just wonder
> if there's a timeout involved, or if new stuff could be swapped
> in 5 min intervals.
>
>
>>Also, before executing any of the suggestions above, I
>>recommend imaging your old boot disk. I always buy a spare
>>hard drive that I keep for emergencies
>
>
> Yep, I have a lot of spares at the moment. Acronis has a
> migration utility. I was thinking about checking into that.
> I doubt that it does much more than imaging, but I trust
> that it won't write a drive signature that will screw up the
> boot process.
>
> ,>Try a search on - "motherboard swap" activation
>
>>in Google, to find examples of the results of other
>>people trying the same thing.
>>
>>http://groups.google.ca/groups?threadm=3C671AAF.5435398%40shaw.ca
>
>
> Good thread. Sounds like there's a way out even if I
> mess up the process.
>
>
>>If the MS IDE driver trick doesn't work, the next thing to
>>try is Kevin's Repair Install suggestion, being careful
>>to get to the right screen to do the repair install.
>
>
> Kevin? I missed that.
>
>
>>One thing a repair install might not handle too well, is if your
>>old computer wasn't set up for ACPI. If the old install was
>>for a "Standard PC", you could potentially have all manner
>>of subtle problems.
>
>
> Make that *two* things I would have forgotten.
>
>
>>HTH,
>
>
> Certainly does. Thanks again, Paul!
>
0l651lhi0f6v50ktv93nn9kjlr017onlh@4ax.com...
Facebook
Twitter
Instagram