bigfoot wrote:

I use offlinesysprep to change the hal. the latest version works great. I haven't had any yet that it wouldn't work on.

as for your process, I have a couple of questions.

step 5: why do you copy the xp cd to sysprep/i386?
you sysprep.bat:
devpath is for adding drivers to the registry. You should be executing devpath on the drivepacks folder not on c:
you don't need the enabling image for amd/intel. you are building in vmware which doesn't even have intelppm.

for -bmsd
The drivers for bmsd never change so you only need to run it once. As for scanning the drivepacks for mass storage, are you only choosing certain ones? like ide only. If you try to add them all you will definitely run in to memory issues.

I copied the XP i386 folder to c:\sysprep\i386 because in a previous universal image everything worked great except during the sysprep stage on reboot it would throw up a dialog box wanting to know the location of 3 different files from the i386 folder and was looking for them under c:\sysprep\i386.

Just figured I'd save myself the hassle and put it all where it wanted it.


As far as Mass Storage drivers go, if I knew how to just give it the Intel drivers and the drivers for the new Acer Aspire One that my image doesn't work on I would be happy. But I've been really busy with other things and just don't have the time to sit down and figure it out.

Spoke too soon.

When I put the machine on the domain, I get the NTFS.SYS error at boot.

Alright, got a successful image!

Something about using OfflineSysprep to do the actual sysprep breaks the Driverpacks finisher on startup.

I ended up running the "sysprep -bmsd" command, then ROE, then using regular sysprep to reseal, THEN running OfflineSysPrep without sysprep to do the HAL and I injected the Driverpacks Mass Storage drivers with it for giggles. Not sure if the driver injecting works that way or not, but so far the image appears to do what it needs to do.

New version of OfflineSysPrep fixed that problem, thanks!

Now my only snag is the Driverpacks finisher isn't working correctly. It starts, but at the same time Windows brings up the New Hardware Wizard. It brought it up twice, for the audio and the video, and I hit cancel on both.

Driverpacks finisher completed but didn't install any drivers for audio and video.


Edit: Think I've found the problem, I'll check back in soon.

Ok, I've taken it upon myself to provide some sort of updated walkthrough for this.

Here's what I've done so far.

1. Install XP with SP3 slipstream

2. Install updates and needed software for my personal build

3. Extracted deploy.cab to c:\sysprep

4. Copied I386 folder to c:\sysprep\I386

5. Built sysprep.inf using setupmgr.exe

6. Followed skinlayers' guide, skipping the makePNF step, set KTD to "False", and completely skipped Step 10 in favor of using OfflineSysPrep

7. Ran the ROE.exe command and shut down my source machine.

8. Downloaded and Installed BartPE's pebuilder.

9. Downloaded OfflineSysPrep and built the plugin according to documentation from Galepo including the Driverpacks Mass Storage option.

    -edited user_settings.ini to skip some of the drivers for sake of not running out of memory

10. Built and burned a CD with BartPE containing OfflineSysPrep

11. Ran OfflineSysprep on my source machine with the following options:

     Administrator user
     Auto update HAL on first boot
     No path for additonal drivers
     Under "Advanced" I selected to inject standard IDE drivers and Driverpacks non-IDE Mass Storage drivers.

     In the actual sysprep program, I checked mini-Setup and clicked Reseal.




Edit:

Have hit a new snag. On first reboot, Windows starts, I see my background image and the mouse pointer. Within a couple of minutes, it drops to the Windows XP logo "It is safe to turn off your computer" screen. Upon restart, I get back into Windows and am greeted with the following message:

The system is not fully installed. Please run setup again.


While I would really love to get OfflineSysPrep working, it's becoming a severe hassle. I think I may just stick with MySysPrep.