Systems Deployment

If it installs on a PATA\IDE HDD for a 5100, it will install on a PATA\IDE HDD in a DC7600. XP uses a generic IDE Device Driver that is natively supported by XP. The issue is that a SATA driver (present in a DC7600) needs to be specified in the sysprep.inf at the time that the image is created, and it needs to be present on the box, as mentioned in my earlier post.

Creating a second image defeats the "Universal Image" premise.

Any chance you could post your sysprep.inf file for your master image? I add a bunch of custom entries under the Mass Storage section to accomodate SATA controllers, and if you don't have the right ones specified, it's game over.

The idea to create the second image is for testing purpose.

But this case looks rather dim. After all it has been weeks and we still don't have much useful information from the poster. I really doubt if he still needs to create this image anymore.

Thanks for the support, sorry have not been in touch recently. The image works ok on a HP5100. I will update my sysprep to include the sata drivers, which I thoughtit had found.

No worries! The SATA thing is a pain, and I know that I had to learn it the hard way. Good to know it isn't an issue in Vista\Windows 7.

Have you added the XP Uberbug reg hit to your task sequence?
http://www.deployvista.com/Blog/tabid/70/EntryID/17/Default.aspx

Thanks for the reply. I got the fix from MS and went to run it, the message comes back, that "Setup has detected that the SP versions of this system in newer that the Update you are applying.

I am running SP3

We need more info here, when do you get the error message. Have you checked your version of PE, AIK, WDT etc?

Do you get a BSOD? Did you include any needed mass storage devices for the new hardware? Is the HAL from your source machine (old) compatible with your target machine (new) ?

Imaging on a 5100 works on everything up to a DC7100, after that you need to get into HAL Swapping.
What model is your build failing on?

is that agp400.sys or some other file?

Hi

Its failing on a dc 7600

dc 7600 seems to be a very ordinary SFF desktop. What driver is the image failing on?

If you have a working DC7600 around, grab the following files:
Hal.dll
ntoskrnl.exe
ntkrnlpa.exe

from the system32 dir.
Stick them on a USB drive.
Boot your 7600 test machine from WinPE and copy the files to the system32 dir.

The machine should boot fine.

if you have a look on www.deployvista.com, Johan has a bunch of scripts for HAL swapping.
It is pretty straight forward to set up, you are using the Microsoft Deployment Toolkit for your deployment?

The machine I have tried it on is dc 5700. It seems to be failing on mfedisk.sys. If you disable auto restart if generates a BSOD, with Stop 0x0000007B. I have been using Windowds Deployment as means of rolling out

mfedisk.sys or mfetdik.sys? Is it McAfee? This seems to be a known condition but the file name is slightly different

the file name to confirm is mfehidk.sys

Mcafee (8.7) is intalled as part of the build

You could have come up with this name yesterday and then the correct name today.

Anyway it is a known issue and hope that you can find a solution in google and let us know how it went for you. Because you are a Corp customer, you may even get access to their knowledgebase.

And the same build works on a DC5100? A 7B stop error is an "inaccesible Boot Device", which means you don't have the correct SATA controller driver installed. When you built your XP Image, did you have the latest SATA controller drives for all required models included in your sysprep.inf, and have them available on the reference machine (i.e. \drivers\SATA\Intel\aahci.*) .

Another question, in the Bios, see if you can run the SATA in "legacy Mode".

Q1: If he can put a PATA drive in this PC and install the image on it then the SATA issues can be ruled out? After all, AFAIK, this PC does have IDE/PATA.

Q2: If the base image is is not working on this PC, can another base image created on this very PC work with the mfe*.sys file/service?