1 Reply by Clutch125

(5 replies, posted in Universal Imaging)

9 out of 10 times the vanilla ACPI HAL works for a base image but I've found there are rare exceptions where you must a have a multiprocessor HAL when you seal with sysprep to have mini-setup run on the target machine.  In one case I spent nearly a week trying to figure this one out. The only change I made to get a certain 'universal' image to boot up was to switch from ACPI to Multi prior to running sysprep.  It's probably not the issue the original poster is seeing but it's definitely worth a try in situations where everything else has been verified.


bdurkee wrote:

If you are using ACPI PC for your base HAL, then it should boot at least once on everything. If your image is not booting even once (i.e., before Sysprep mini-setup), then the mass storage drivers are most likely your problem. Specifically, the [SysprepMassStrorage] section in the sysprep.inf, in my experience, does not work. At all. Just delete it from the file.

The quick way to work around this issue is to boot into the BIOS configuration and change the SATA mode to "Legacy" or "IDE Compatibility" (or something like that). The image should boot up fine and work like normal, but you won't get some of the fancy SATA features like hot-plugging or NCQ.

The better way, as others have suggested, is to use OfflineSysprep inject the MassStorage drivers. It takes a few extra steps (you have to create a BartPE plug-in from the driverpack), but it works very well.

Go to forum: Universal Imaging

2 Reply by Clutch125

(15 replies, posted in Vista-Tool)

McStarfighter wrote:

dpinst.exe can not help me, because it only install drivers for detected hardware. But I want to expand the driver rep for future hardware installations. Any idea? It would be very nice how to integrate the Vista DriverPacks post-install into the default driver rep ...

On Vista/2008/w7 dpinst will install drivers for non-detected hardware.  You might want to look into that possibility again.

Go to forum: Vista-Tool

3 Reply by Clutch125

(5 replies, posted in Universal Imaging)

This may not even be your issue but I thought I'd mention the possibility because I spent a ton of time trying to figure out why my images didn't work on one machine even though it had the correct mass.  Post-sysprep, updating HAL from ACPI to Multiproc does not work in all cases. Slick as it was I had to get away from doing that because I ran into some problems with one system as well.  After that I moved to making separate images for ACPI and Multiproc.  These days I'm about to ditch ACPI images altogether because anything better than a P4 non-hypertherading is fine with a multiproc HAL.  Plus the newer gen Windows OSs pick the correct HAL anyway.

Go to forum: Universal Imaging