Has anyone had any success with this OS?

If so, any chance of a link, or a brief description of your process to make a working, universally deployable image with it?

Thanks

Jim

I have here a small issue of what driverpacks I must insert using wintoolkit. When I use all driverpacks some computers are well formated and installed but they don't boot and don't show the welcome and desktop. They keep just rebooting. But when I use just the following packs all computers boot with no problem

Graphics A
Graphics B
Graphics C
LAN
Modem
Sound A
Sound B
Webcam
WLAN

So why using chipset and mass storge packs cause some computers to not boot properly?

Thank you for any help and hints.

I installed a reference Windows XP system in a VirtualBox virtual machine, and with SAD was able to integrate DriverPacks into the deployment process. I was able to see during mini-setup that dp_Inst_tool.cmd was run (BTW, does it matter if I run dp_Inst_tool.cmd during the Run Once VS the Additional Commands stage?) and the relevant DriverPacks installing windows showed up. However, the test deployment of the sysprep-resealed image was also on a virtual machine.

When I used Symantec Ghost 11.5 to make an image of the system, and deployed it to a bare metal test machine, the OS would repeatedly reboot without even getting to the Windows logo screen. I described the issue here, and a response suggested that it is because lack of AHCI support in Windows XP, and that changing the bare metal system's BIOS setting to IDE should work. Even if this solves this issue, however, I don't want to have to manually change the BIOS settings in a bunch of my organisation's computers during deployment which would be a big hassle. Therefore I am wondering if there is a way to pre-load the relevant AHCI/SATA drivers into my Windows XP reference system in VirtualBox before running sysprep?

I know there is the Mass Storage DriverPack, and there is a checkbox for it in DriverPacks Base when running SAD using method 2. The problem is my current setup runs dp_Inst_tool.cmd *during* mini-setup, but the system wouldn't even boot and wouldn't reach mini-setup to begin with. So:

(1) I'd like to confirm that the Mass Storage DriverPack contains the relevant AHCI drivers I am looking for.

(2) Is there a way to pre-load/pre-install AHCI drivers into Windows XP in VirtualBox? If so, and if it can be done with DriverPacks, how do I do it? BTW, I found two posts (here and here) that shows how to install an AHCI driver in an existing Windows XP installation. But they are specific to the chipset of that machine, while I'd like to prepare a sysprepped image that can be deployed to different hardware that might have different AHCI chipsets (so this is where I am hoping DriverPacks might be able to help).

I confess I am very new to DriverPacks so I'd appreciate any specific suggestions you can give me. Thank you very much!

I am creating a new corporate image for our workstations which are a mixture of Dell Optiplex 745, 755, Vostro laptops and desktops and Latitude D610, D620, D630 and other laptops.  I created the image on an Optiplex 755 and used the following driverpacks:

DP_Bluetooth_wnt5_x86-32_910.7z
DP_Chipset_wnt5_x86-32_1209.7z
DP_Graphics_A_wnt5_x86-32_1206.7z
DP_Graphics_B_wnt5_x86-32_1206.7z
DP_Graphics_C_wnt5_x86-32_1206.7z
DP_Graphics_PhysX_wnt5_x86-32_1206.7z
DP_HID_wnt5_x86-32_1209.7z
DP_LAN-RIS_wnt5_x86-32_1011.7z
DP_LAN_wnt5_x86-32_1205.7z
DP_MassStorage_wnt5_x86-32_1209.7z
DP_Modem_wnt5_x86-32_1205.7z
DP_Sound_A_wnt5_x86-32_1111.7z
DP_Sound_B_wnt5_x86-32_1111.7z
DP_WebCam_wnt5_x86-32_1107.7z
DP_WLAN_wnt5_x86-32_1202.7z

I have used driverpacks and sysprep in the past numerous times and now I am having a huge issue.  I unzipped the drivers into a folder and use spdrvscn to add the appropriate registry entries for the drivers.  Installed and configured all of my applications and ran all updates.  Nothing strange so far.  I customized my sysprep.inf and execute sysprep -bmsd, then sysprep clicking the "Use Mini Setup" option.  The workstation image was then captured and deployed to the D630 laptops.  Mini setup runs as expected, however, I am not able to use the laptop's keyboard and touchpad.  I have to connect a USB keyboard and mouse to complete the setup.  After the setup is complete, device manager shows an unknown device with a yellow exclamation mark under the keyboards key.  The device's status states that "The drivers for this device are not installed. (Code 28)"

If I try to delete the device and have windows redetect and install it, I get an error saying that "There was a problem installing this hardware.  Dell Touchpad.  The system cannot find the file specified."  Another error then pops up for the PS/2 keyboard (106 keys ctrl + caps).  "Cannot create a file when that file already exists."

Has anyone seen this before.  I took an image of the system before running sysprep and I have tried running sysprep with and without the "Detect Non Plug and Play Devices" checked.  I get the same result.  I also added the official dell drivers for the various workstations and laptops and ran the spdrvscan pointing the the dell drivers first before pointing to the driverpacks drivers.

The strange thing is that I did a similar image earlier in the year and I did not get this issue on the laptops.  This seem to affect just the laptops.  I deployed the image to a desktop and it works fine.

Any assistance in solving this would be greatly appreciated.

Thanks.

DP_AMDfilter_wnt6-x64_1110
DP_Audio_wnt6-x64_1111
DP_CardReaders_wnt6-x64_11041
DP_Chipset_wnt6-x86_1212
DP_Gaming_wnt6-x64_812
DP_Graphics_A_wnt6-x64_1203
DP_Graphics_B_wnt6-x64_1203
DP_Graphics_Mobile_wnt6-x64_1203
DP_LAN_wnt6-x64_1208
DP_MassStorage_wnt6-x64_12121
DP_Misc_wnt6-x64_1202
DP_Monitors_wnt6-x64_911
DP_Touchpad_Mouse_wnt6-x64_1203
DP_Webcam_wnt6-x64_1103
DP_WLAN_wnt6-x64_1203

I got few errors adding some but nothing i felt important (but maybe it was).
But after a reboot i got a beautiful blue screen of the death.
Is there anyone that could advise me to not install a pack or driver that could crash the system ?

I've been struggling with MassStorage drivers for a while now and I was hoping someone can help me out ..

What I want to do is include only the storage drivers in my XP image, so it can boot on any controller using IDE (and if possible AHCI)

I've tried to only use "sysprep -bmsd" to populate [SysprepMassStorage] section, I also tried to follow some guides (like this) with no luck.

In all my tests, I had these entries under [Unattended] section:
UpdateInstalledDrivers=Yes
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

It also seems to me that "Sysprep -clean" does nothing, because it finishes instantly (added "CMD.exe /k" in cmdlines to test) and the criticaldevicedatabase is still the same.

Note that I can't add the "-pnp" switch to the sysprep reseal command, because I'm capturing the Image through SCCM.

not sure, where to ask this.

I want to make a wim image file to deploy windows xp in my AD domain via WDS with preinstalled software.
My actions:
1. I've patched vanila win xp sp3 image with DriverPacks BASE (with KTD on)
2. Installed this in vm. Drivers seems to be in %WINDWS%\DriverPacks folder.
3. created sysprep.inf with setupmgr, pointed that drivers cache in %windows%\driverspacks, etc.
4. ran sysprep -bmsd
5. captured image with WDS.

Looks good - I mean, when I try to deploy this on my vm - all great. But, when I try to deploy it on any physical pc - it fails. Even in safe mode Windows is unable to boot.

So if anyone can point where to dig (not to bury myself, though) - I'll appreciate.

My problem is with the AHCI drivers.
If use the image I've created on a PC with AHCI enabled, i get a BSOD 0x0000007B
If i change the AHCI to IDE, everything works great.
I've been searching for a week now to find what's wrong.

I've tried somebody's guide:
http://forum.driverpacks.net/viewtopic.php?id=4849

Here is what i have done to create the image:

# Tools:
Windows XP SP3
Sysprep SP3 (deploy.cab)
DriverPacks BASE (DPs_BASE_1006.exe)

# Driver packs:
DP_CPU_wnt5_x86-32_1005.7z
DP_Chipset_wnt5_x86-32_1206.7z
DP_LAN_wnt5_x86-32_1205.7z
DP_MassStorage_wnt5_x86-32_1206.7z
DP_Sound_A_wnt5_x86-32_1111.7z
DP_Sound_B_wnt5_x86-32_1111.7z

01. Install Windows + Updates + Programs + Customization
02. Extract deploy.cab to C:\Sysprep
03. Copy from Windows CD the folder i386 to C:\Sysprep\i386
04. Extract DPs_BASE_1006.exe to C:\DPBase
05. Copy CPU DriverPack inside "C:\DPBase\DriverPacks" folder (C:\DPBase\DriverPacks\DP_CPU_wnt5_x86-32_1005.7z)
06. Copy MassStorage DriverPack inside "C:\DPBase\DriverPacks" folder (C:\DPBase\DriverPacks\DP_MassStorage_wnt5_x86-32_1206.7z)
07. Run C:\DPBase\DPBase.exe > Standalone Drivers > DriverPack CPU > Method 1 > Slipstream
08. Run C:\DPBase\DPBase.exe > Disc > DriverPack MassStorage text mode > Method 1 > Slipstream
09. Move all contents of C:\DriverPacks.net to C:\
10. Extract all other DriverPacks to C:\
11. Extract DevPath.exe from "C:\DPBase\bin\wnt5_x86-32\M2.7z" to C:\
12. Run "C:\DevPath.exe C:\D"
13. Delete file C:\DevPath.exe and folders C:\DPBase and C:\DriverPacks.net
14. Edit C:\DP_Inst_Tool.cmd and delete the line "Echo DPsRootDel  = "false" >> %DPFL%"
15. Use Setup Manager to create a sysprep.inf (C:\sysprep\setupmgr.exe)
16. Edit C:\Sysprep\sysprep.inf and add:

[Unattended]
UpdateInstalledDrivers=Yes
DriverSigningPolicy=Ignore

[GuiRunOnce]
Command0=C:\DP_Install_Tool.cmd

[Sysprep]
BuildMassStorageSection=Yes
    
[SysprepMassStorage]

17. Run "C:\Sysprep\sysprep.exe -bmsd"
18. Run "C:\Sysprep\sysprep.exe" check "Use Mini-Setup" and "Detect non-plug and play hardware", select "Shutdown" and press "Reseal"
19. Grab your generic image

Here is my sysprep.inf before i run -bmsd (I have removed AdminPassword and ProductKey)

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    InstallFilesPath=C:\sysprep\i386
    DriverSigningPolicy=Ignore
    NonDriverSigningPolicy=Ignore
    UpdateInstalledDrivers=Yes
    TargetPath=\Windows
    OemPreinstall=Yes
    
[GuiUnattended]
    AdminPassword="XXXXX"
    AutoLogon=Yes
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    TimeZone=130
    OemSkipWelcome=1

[UserData]
    ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
    FullName="TEST"
    OrgName="TEST"
    ComputerName=PC-001

[Display]
    Xresolution=1280
    YResolution=1024
    Vrefresh=60

[RegionalSettings]
    LanguageGroup=4
    SystemLocale=00000408
    UserLocale=00000408
    InputLocale=0409:00000409

[SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=windist

[Identification]
    JoinWorkgroup=TEST

[Networking]
    InstallDefaultComponents=Yes

[Sysprep]
    BuildMassStorageSection=Yes
    
[SysprepMassStorage]

Any suggestions?
I've already tried to enter manually the SysprepMassStorage with no success. BSOD again!

Thanks in advance.

The following is a brief summary of my template computer preparation:
- machine is on a fully patched vmware esxi 5 update 1 box
- 2-core cpu, 512mb ram, 15gb ide
- xp pro w/sp3 vl iso installed using vlk
- machine never on domain
- no windows updates nor software as i'm only testing driverpacks
- wga never installed
- manually downloaded latest driver packs
- have pared down the mass storage drivers after each unsuccessful test to just \d\m\i*
- disabled system restore, page files, and hibernation
- sysprep cab files are sp3
- using spdrvscan132- using the older hwids.cmd rather than findhwids.exe
- running sysprep -bmsd after hwids
- sysprep.inf file is the same file as it's been for the past 3 years
- > sysprep -mini -pnp -quiet -reseal
- alternately used -forceshutdown with the same results

[update] Solved:

after eliminating the driverpacks one-by-one, the problem is with the intel mass storage drivers \D\M\I2 and \D\M\I3 with hwids.cmd.  rather than deleting those folders, i moved them to an alternate location and modified spdrvscn and sysprep.inf as follows:

> spdrvscn132 /p %systemdrive%\sysprep\d /d %systemdrive%\sysprep\op #OemPnPDrivers

[sysprep.inf]
OemPnPDriversPath=%systemdrive%\sysprep\op\m\

FWIW, i don't know if all this is necessary or whether it makes a difference.  simply removing D\M\I2 and D\M\I3 should work

My understanding:
1. Image one laptop with the source image and remove non-related laptop drivers and change IDE to standard controller...etc
This is from the post "DriverPacks with Sysprep HOWTO"
2. Run DPBase. Choose 'Standalone Drivers' as platform, next check only the CPU driver pack and choose 'Method 1' and finally click 'Slipstream'
3. Move the contents of thus created folder 'DriverPacks.net' to the root of disc C: Then unpack all remaining driver packs to the root of disc C:

Question, what should I do for all the laptop drivers?
Create my own 3rd party driver pack?

4. Extract DevPath.exe from DPBase\bin\wnt5_x86-32\M2.7z and run DevPath.exe C:\D
5. Edit dp_Inst_tool.cmd and REMove the line 'Echo DPsRootDel  = "false"            >> %DPFL%'
6. Delete DPBase, DriverPacks.net, DevPath.exe and compressed driver packs
==The Sysprep part==
6. Place sysprep files to C:\sysprep
7. Create sysprep.inf with setupmgr.exe and open it in an editor. To the [Unattended] section add the two lines: UpdateInstalledDrivers=Yes and DriverSigningPolicy=Ignore
8. Add a new section [GuiRunOnce] to sysprep.inf, under which add a line Command0=C:\DP_Install_Tool.cmd
9. Add a new section [SysprepMassStorage] to sysprep.inf, save the file, then execute sysprep.exe -bmsd
10. Finally, launch sysprep.exe, check 'Use Mini-Setup' and 'Detect non-plug and play hardware' and hit 'Reseal'.

Thank you for your help.

I was trying numerous ways to sysprep a vista system, but unfortunately, if i am here, its because i didnt succeed.

I tried SPAT which is working for XP, 7. NOT for Vista
I tried EASY SYSPREP, which is working for XP, 7. not for Vista
Offline sysprep doesn't work for Vista and Win7.
MySysprep which is verry... useless...
Newprep which is causing me problems with Vista...

Any idea on a working universal sysprep image for Vista ?
I have made many universal images for XP and Win7, but i cannot build one for Vista.

Help...

Thanks !

Been messing around with DriverPacks and the many DriverPacks/sysprep guides out there.  Many thanks to the DriverPacks team, an amazing idea implemented well (so for so good at least!).

I have everything set up and running as desired, except for one thing.  When I run ROE.exe to create the registry entry it creates the appropriate key; however, the value points at a network drive I have.  Instead of being 'C:\DPsFnshr.exe' it creates the key with the value 'X:\DPsFnshr.exe'.  Needless to say, this drive does not exist on the machines we're deploying.  How can I change the value ROE creates?

I know I could (fairly easily) create a script/registry key to create/change the appropriate key.  However, I'm kind of just the setup guy, I won't be the one using these tools to re-image machines.  And, I would like to stick as close to on-line documentation as possible (they won't bother to read the documentation I'll give them; but, they'll google it) if a problem/change arises.

Thanks.

I suggest to driverpacks.net team to make new driver pack that only contain drivers that compatible with sysprep, as current mass storage DP contain tons of drivers that some even not XP compatible. This is only to make it easier to universal images builders.

I successfully made my image with all intel's mass storage by following this http://www.symantec.com/connect/article … ta-support

I hope this will help.

I read this topic http://forum.driverpacks.net/viewtopic.php?id=5443
I excluded I5 but I get same error even tried only I9 no luck same error.

I did some search about mass storage related problems the answer is to do offlinesysprep.
I read Galapo's sticky topic about offlinesysprep, prepared all the requirements.

I tried few times.

1st try:
-HAL update option: AUTO configuration
-Install standard IDE Mass Storage Devices
-Install all DriverPack non-IDE Mass Storage Devices
-Generate new SID

After clicking apply then sysprep.exe started I chose use Mini-Setup, Detect non-plug and play hardware and shut down mode: Quit, generate new SID: OK and then just freeze there.
Is this because the needed server service? At first when running offlinesysprep I get a message bout starting required service.

2nd try:
-HAL update option: AUTO configuration
-Install standard IDE Mass Storage Devices
-Install all DriverPack non-IDE Mass Storage Devices
-Generate new SID
-Complete offlinesysprep operations without running sysprep.exe

Operation finish when reboot to test get error before loading windows: "system32\drivers\ntf.sys missing or corrupt". I did some search about that, found ntldr should be replaced with one from XP 64bit, this is due to memory limitation on 32bit ntldr.

I'm confused I want to know, is sysprep.exe should behave at offline same as online?
is this will work if I do first sysprep as normally only include windows standard mass storage then reseal, after that use offlinesysprep to only inject DriverPacks mass storage?

Thanks to all driverpacks.net members.
I really learned a lot.