Sysprep migration problem

StormRider90aStormRider90a
edited April 2006 in Science & Tech
I found this forum by googling for "APIC HAL", and it looked like there are people here who may know how to solve my problem. I'm trying to move my Win2k installation from my old '99 Dell Inspiron 7000 laptop to my new IBM/Lenovo R52 laptop. The sysprep'd image was blue-screening on the new machine until I found the sysprep version 1.1 update which supports multiple drive controllers. Now it gets through the initial setup screen and is "installing devices", but locks up when the progress bar is about 1/3 of the way across. I suspect it's due to different HALs on the two machines, which the sysprep docs say is not supported. Is there any way around this?

Thanks.

Comments

  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited April 2006
    Too bad Win2K doesn't have a "repair" installation available. Hmm, I'm trying to think of a solution for you.
  • QCHQCH Ancient Guru Chicago Area - USA Icrontian
    edited April 2006
    There are ways to do it but it is VERY tough and the results are normally not stable. The HAL's on the two systems are WAY different. I have been able, in the past, to force the "Computer" driver (The HAL... Device Manager, Computer object) to use "standard PC" instead of ACPI or Uniprocessor (depends on what your Dell listed.). Standard PC drivers work fine but some of the devices o the IBM may not get picked up correctly. The laptop's power controls and system health may suffer. The correct HAL can interface the hardware and allow the system to reduce power, CPU, ramp up fans, etc... The HAL's even manage how the system shuts down. Standard PC HAL may not have the necessary interfaces to allow the system to run stable.

    Why are you trying to use such an old OS on a new laptop? The R52 is a great laptop and should really be using WinXP.
  • StormRider90aStormRider90a
    edited April 2006
    What I'm really trying to accomplish is just migrate my zillion applications to the new machine without having to search for all the installation packages on my CDs, and re-install and re-customize the apps. I've been successful with this in the past, but these two machines apparently are too different for sysprep to handle. I'll happily upgrade to XP once the installation has been moved to the new machine, hoping the upgrade process is smart enough to install the new HAL. I could also do the upgrade first if you think XP would successfully migrate, but I'd have to merge two partitions first on the old machine to have enough space for the upgrade.
  • QCHQCH Ancient Guru Chicago Area - USA Icrontian
    edited April 2006
    I guess my first impulse as a corporate IT guy...

    In running a forced migration install on a new system, you CAN cause physical damage to the hardware do to incorrect settings that monitor and adjust the hardware. Basically, you could kill or at least shorten the life on the laptop.

    A very new laptop designed to run the latest operating system with the latest drivers will be very unstable if you force an old W2K migration on to it. Basically, you may not be happy with the performance and I would expect numerous mysterious crashes that will be very difficult to fix.

    The time you have spent research how to migrate, the time it will take to successfully migrate, the time it takes to get the system to run, the time you spend waiting for the system after all the crashes, and the time you spend trying to fix all the errors... it would better used finding the original installations of the applications.

    That's my opinion as an IT guy...
  • StormRider90aStormRider90a
    edited April 2006
    Yeah, I'm getting to that point with no return on my time so far...

    I wish the corporate IT guys would complain to Microsoft a little louder that the users don't really care what hardware they're running on. They just want their applications to run on a newer faster machine, without wasting a couple of weeks getting everything running again. A week's pay times 30K employees becomes tens of millions of $$$ of lost productivity for every upgrade cycle.
  • StormRider90aStormRider90a
    edited April 2006
    I should also say that IBM/Lenovo has a nice utility that will download and install/upgrade all the drivers with minimal effort. So the only incorrect drivers that would be left running after a migration and XP upgrade would be the things that MS didn't identify as needing replacement. But you're right, I don't know how thoroughly the XP upgrade scans the machine, it could conceivably not replace everything that would be different in a fresh install. I'd probably want to go through the Device Manager afterward and verify that all the drivers are the same ones picked by a fresh install in another partition.
Sign In or Register to comment.