• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Any way to use Sysprep to migrate Win2K installation between hardware systems with non-matching HALs?

K

Kwad Guy

Diamond Member
Here's the deal:

I have Windows 2000 installed on a dual processor machine that ACPI.
I want to image the installation and migrate it to a dual processor
system that is non-ACPI. The normal Sysprep -> Image (Drive Image) ->
Install-on-new-machine method won't work because the HALs of the
two machines are different (ACPI vs non-ACPI). If I try, the new
machine will hang at the "Windows 2000 is starting up" screen.

I tried to circumvent the problem on the new machine by then doing
a Win2K repair after booting from the Win2K CD. I choose "install",
followed by "R" after getting the report that a Windows2000 installation
had been found (i.e. I didn't use the repair console tract). This
copied over a new set of Win2K system files and then the system
came up OK after redetecting all the hardware.

HOWEVER, for some reason when I did this, the "Standard PC" HAL,
not the MPS non-ACPI hal, was installed. So when I eventually got
up and running with Win2K on the new machine, it didn't see the
second processor. Trying to go into the device manager and updating
the driver for the computer to the MPS dual processor (not ACPI) driver
basically hosed the entire installation...

Any suggestions/tips on how you can do a migration between machines
with non-matching HALS?

Kwad
 
Yes, it's in a FAQ I'm about to put up.

If you can't wait, look at SaigonK's article at the bottom of this thread, since that is what is going up in the FAQ.
 
Hi Andy:

I just read SaigonK's article, but didn't see anything that
addresses the HAL issue. I always use the -pnp flag with Sysprep, but
that doesn't solve the non-matching HAL problem...

Kwad
 
Convert the ACPI installation to STANDARD PC and allow it to redect everything. I've had much luck going from ACPI to STANDARD PC but poor results going from STANDARD PC to ACPI.

Just make a image (ghost) of the ACPI machine before converting so you can revert back to ACPI when you're done.

Cheers!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top