Migrating windows from non-ACPI to ACPI mobo

  • Thread starter Thread starter Tom Del Rosso
  • Start date Start date
T

Tom Del Rosso

I have a new Athlon 64x2. According to several sites including MS, you can
use the repair option on the Win2k CD to move from a single CPU to muti-CPU
system, but not from a non-ACPI system to a ACPI system. Either way it has
to change the HAL, so it seems odd that it can do it only sometimes. Is it
really impossible?
 
AFAIK you must reinstall.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I have a new Athlon 64x2. According to several sites including MS, you can
| use the repair option on the Win2k CD to move from a single CPU to
muti-CPU
| system, but not from a non-ACPI system to a ACPI system. Either way it
has
| to change the HAL, so it seems odd that it can do it only sometimes. Is
it
| really impossible?
|
|
| --
|
| Reply in group, but if emailing add another
| underscore and remove the last word.
|
|
 
Tom said:
I have a new Athlon 64x2. According to several sites including MS, you can
use the repair option on the Win2k CD to move from a single CPU to muti-CPU
system, but not from a non-ACPI system to a ACPI system. Either way it has
to change the HAL, so it seems odd that it can do it only sometimes. Is it
really impossible?
Click to expand...

Clones/ hard transfers from dissimilar systems, even if successful,
often ROT, performance wise. If you mnage to get past the the BSOD that
I think you'll get if you try, you'll have to go through maybe 8 or 10
reboot cycles, at least four of which will be your system installing
new drivers, maybe five or ten minutes each with no feedback. You'll
lose a pint of sweat wondering if each reboot cycle will be the last.
If you manage not to panic, and let it do it's thing, you may get to
the point where you want to resolve the ghost hardware issues--
leftovers from your old system. Your remaining reboot cycles will be
spent removing old driver crap. You may spend the next few weeks
finding the remaining odd glitches.

Clean install is the way to go.

If you don't want to lose your old files, I suggest getting a new hard
drive to be used as your new system drive, and setting the old one as a
slave.
 
Back
Top