Jump to content

Recommended Posts

Posted

A few days ago I started searching for a solutions for my +25 ghost images I'm using. We are using Computer Associates OS Installation Management to deploy our images to the new computers.

In this system we are using Norton Ghost images becauses of the speed. We don't want fully unattended windows installation because those are to slow for our environement (nothing can be changed about that at the moment :/).

But there is one big problem. We have to create a new image for every new model of computer that we have. And I would like to create only a few WIndows XP images for all the computers. While I was searching why those images never boot up on different systems I read everything about the hal.dll's being different (again) and concluded that we only have systems with 2 different hall.dll's. (older IBM P4 systems without HT and new DELL's with HT). So I only need 2 images for those hal.dll's, I guessed ?

And that still is my problem, I create an image for a IBM 6349-74G. Deployed that images after a sysprep to the IBM 8187-D1G. It runs the mini-setup automated as it should and on the first boot it locks up and reboots. (in save mode it stops on agp440.sys, the known ghost problems for hal.dll ? :/)

Can anyone explain my why this is happening ?

Why is can't I clone Windows XP from one system with halaacpi.dll to another ?

Are there more of those files ?

(I'm only looking for the reason why it happens, if it isn't possible to solve I will keep on creating ghost images because it has to be faster then unattended installs)

thanks


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...