Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Installing ATI2MTAG.SYS
Type in the following paths for the requested files:
ATI2MTAG.SYS -> C:\WINNT\SYSTEM32\DRIVERS
ATI2DVAG.DLL -> C:\WINNT\SYSTEM32

The file is in both locations as well and it's still looking on the D drive when it shouldn't sad

Fixed this stupid sysprep

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

post your sysprep.inf and maybe we can help.

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Oh I fixed it no worries

Here it is anyways tho

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    OemPnPDriversPath=C:\i386\drivers 
    OemPnPDriversPath=C:\sysprep\i386
    UpdateInstalledDrivers = Yes
    DriverSigningPolicy=Ignore
    NonDriverSigningPolicy=Ignore

[GuiUnattended]
    AdminPassword="XXXXXX"
    EncryptedAdminPassword=NO
    AutoLogon=Yes
    AutoLogonCount=1
    OEMSkipRegional=1
    TimeZone=4
    OemSkipWelcome=1

[UserData]
    ProductKey=XXXXXXXXXXXXXXXXXXXXXX
    FullName="Smart Classroom"
    OrgName="XXX"
    ComputerName=

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=60

[TapiLocation]
    CountryCode=1
    Dialing=Tone
    AreaCode=510
    LongDistanceAccess="1"

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

[Identification]
    JoinWorkgroup=SmartClassroom

[Networking]
    InstallDefaultComponents=Yes

[GuiRunOnce]
Command8="C:\Documents and Settings\wsadmin\Desktop\firstboot.cmd"

[SysprepMassStorage]
*pnp0a00=c:\windows\inf\machine.inf
*pnp0a01=c:\windows\inf\machine.inf
*pnp0a04=c:\windows\inf\machine.inf
*pnp0a03=c:\windows\inf\machine.inf
pci\cc_0604=c:\windows\inf\machine.inf
pci\cc_0601=c:\windows\inf\machine.inf
pci\cc_0602=c:\windows\inf\machine.inf
pci\cc_0600=c:\windows\inf\machine.inf
pci\cc_0500=c:\windows\inf\machine.inf
root\ftdisk=c:\windows\inf\machine.inf
root\swenum=c:\windows\inf\machine.inf
root\update=c:\windows\inf\machine.inf
root\mssmbios=c:\windows\inf\machine.inf
root\dmio=c:\windows\inf\machine.inf
lptenum\microsoftrawport958a=c:\windows\inf\machine.inf
root\rdpdr=c:\windows\inf\machine.inf
root\rdp_mou=c:\windows\inf\machine.inf
root\rdp_kbd=c:\windows\inf\machine.inf
*pnp0000=c:\windows\inf\machine.inf
*pnp0001=c:\windows\inf\machine.inf
*pnp0003=c:\windows\inf\machine.inf
*pnp0004=c:\windows\inf\machine.inf
*pnp0100=c:\windows\inf\machine.inf

alot more then this

edit = code tags added

Last edited by OverFlow (2010-02-05 09:04:13)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Anyone who loves Steady State Here is my bat as well

:: 
::  firstboot.bat
::  

@echo Installing Bomgar Jump 

runas /trustedlevel:unrestricted ""bomgar-RA"

@echo Running Bginfo

runas /trustedlevel:unrestricted ""Bginfo.exe" /accepteula /timer:0

@echo Locking D Drive Documents

runas /trustedlevel:unrestricted ""REGEDIT.EXE /S "Reg_My_Documents_Fixed.reg"

@echo Setup Auto Login

runas /trustedlevel:unrestricted ""REGEDIT.EXE /S "autologon.reg" 

@echo L Key SPSS 18

runas /trustedlevel:unrestricted ""spssactivator.exe" OUR KEY"

@echo Open Steady State and User Must Set Disk Protection to On

runas /trustedlevel:unrestricted "C:\Program Files\Windows SteadyState\SCTUI.exe /enableandreboot"

I have it log into as admin run these scripts, lock the drive with some reg and start up steady state. We use steady state on our smart classroom shared PC's where I work.

Last edited by Quad-Damage (2010-02-05 09:06:39)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Here is a nice autologin script if people use local machines that want autologin

 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="Smart Classroom"
"AutoAdminLogon"="1"
"ForceAutoLogon"="1"

This auto logs into a machine called Smart Classroom with no password

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Ok here is what I'm trying to do

I want to run my firstboot.bat as soon as windows loads into desktop

Many of my reg files are on the local admin desktop and need to be run after syprep

Anyways

Here is what I have currently

In my C:sysprep\i386\$oem
I have the runonce.cmd
and i have my cmdlines.txt


Here is my runconce.cmd

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
REG ADD %KEY% /V runtwiceex /C "C:\firstboot.cmd"

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Here is my CMDlines.txt

[COMMANDS]
"C:/VBSscripts.\hal_Update.bat" 
"C:/sysprep\i386\$oem$\runonce.cmd"

If you look back one page you can use my script to update the hal, has been working great for myself.

Last edited by Quad-Damage (2010-02-05 09:21:01)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Good afternoon,

I come here in desperation and a little bit of frasutration smile. Over the past few weeks I have been tasked with setting up our WSUS and WDS Server at work (YAY IS ME... haha) and after successfully implementing WSUS I moved onto WDS.

This is were the hair pulling begins. We currently have a number of PCs around the Office used by Employees (Ranging from Dells to HPs, and one or two old school Compaqs - they range from UP to MP so where it all began). I than have to deal with our Thin Clients which are deployed to our Customers.

First things first, we'll deal with Employee PCs/Laptops:

Shortly after I began my new venture, I learnt of HAL and the issues of Drivers the hard one, here I am, Sysprep'in a PC, capturing the image with WDS and then imaging the 10 or so of those HP machines - I'm thinking BRILLIANT couldn't be easier - WRONG haha.

Long story short (so as not to make this a WALL OF TEXT) - I discovered DriverPacks, tried following the instructions posted on the first page of this Sticky (well outdated I'm sure), tried various applications like MySysPrep etc to no avail.

After reading through this sticky, I'm somewhat even more lost now (haha) - hearing good things about OfflineSysPrep but don't quite understand it fully, or think it suits what I'm trying to do. Here is what I have atm, and hope someone can point me in the right direction - I would be more than happy to write an update HOWTO guide for the public once this DILEMMA is over.

1. Installed XP Pro on fresh machine
2. Installed SP3 - various Hotfixes/Patches
3. Installed our companys' various required Applications (Anti-Virus, Altiris, VNC etc)
4. Downloaded all the 'latest' DriverPacks packages and extracted them all to C: (C:\D, with the .inf in C: )
5. Have all the SysPrep tools from the Deploy.cab extracted to C:\sysprep
6. ROE.exe in C:\sysprep, DPsFnshr.ini and extract DPsFnshr.7Z to C:, DevPath.exe in C: and also ATICCC.ins in there.

Then gone ahead and imaged it with Ghost (learnt the hardway, had to rebuild the above setup numerous times after 'bad' images) - and awaiting your feedback.

On a sidenote: I hope to go completly 'unattended' with WDS as I had done when I was imaging those 20 or so PCs I did successfully before (Using sysprep.inf and an unattended .xml on the WDS server).

Looking forward to hearing where I've been going wrong.

Last edited by Jack_F (2010-02-05 10:44:01)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Post your sysprep

Don't do the inf files, this saved me some problems

Setup everything like the directions say but skip the makepnf.

Before you sysprep in command cd/sysprep/roe.exe 3937
Make sue that file is there

and then run this bat file to start your sysprep. Make sure you are changing your HAL file with either a script. offlinesysprep, or this

@echo off
cd C:\SYSPREP

echo Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

echo Running sysprep and shutting down.
sysprep.exe -forceshutdown -mini -reseal -quiet -activated

For the Hal this works about %90 of the time

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    OemPnPDriversPath=C:\i386\drivers 
    UpdateInstalledDrivers = Yes
    DriverSigningPolicy=Ignore
    NonDriverSigningPolicy=Ignore
    UpdateUPHAL="ACPIAPIC_MP,%WINDIR%\inf\hal.inf"

This would be added to the sysprep

Build the PC on a Uni Processor and this will switch to a Muti or Uni works well most of the time. I like my bat script better but this works as well.

Last edited by Quad-Damage (2010-02-06 07:18:08)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Thanks for the reply Quad-Damage, couple questions though:

Before you sysprep in command cd/sysprep/roe.exe 3937

Should that be ROE.exe 937 or actually 3937?

I'll give this ago tomorrow when back in the office and report back.

Thanks!

Last edited by Jack_F (2010-02-08 12:55:19)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

No? 3937? I always do 937 and it works for me

Just before you run the sysprep (I like the bat file I provided above)

Make sure you have extracted the driver path to the C: (D) folder and make sure you have all the correct devon and driver pack finisher files in the correct location. The 1st page has information on how to do this.

Open command, in Run type cmd
Then type cd ..
cd ..
cd ..
cd ..
untill you are in the root C: drive
Then type CD sysprep
Then in the folder type ROE.exe 937

In Command you are running
C:\sysprep\ROE.exe 937

This calls for the computer to install the driver packs after the next reboot.
I do a mini setup that just promps for a name and then adds the computer to my Active Directory.

Make sure you have a file called ROE.exe in your sysprep folder as well

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Thanks so much for your help Quad-Damage - however I am alittle confused as to what .bat scripts of yours I should be running.

Firstly I see this one (on Page 6):

--------------------------------------------------------------------------------------------------------------------------------------
@echo off

:DRIVER_HAL_UPDATE
    SET HAL=

    IF %NUMBER_OF_PROCESSORS%==1 (
        devcon.exe /find @ROOT\ACPI_HAL\0000 | find /i "Multiprocessor" > NUL && SET HAL=ACPIAPIC_UP
        devcon.exe /find @ROOT\PCI_HAL\0000 | find /i "Multiprocessor" > NUL && SET HAL=MPS_UP
    ) ELSE (
        devcon.exe /find @ROOT\ACPI_HAL\0000 | find /i "Uniprocessor" > NUL && SET HAL=ACPIAPIC_MP
        devcon.exe /find @ROOT\PCI_HAL\0000 | find /i "Uniprocessor" > NUL && SET HAL=MPS_MP
    )

    IF NOT "%HAL%"=="" (
        ECHO.
        ECHO ----------------------------------------
        ECHO Installing %HAL% HAL
        ECHO ----------------------------------------
        ECHO.

        devcon.exe sethwid @ROOT\PCI_HAL\0000 := !E_ISA_UP !ACPIPIC_UP !ACPIAPIC_UP !ACPIAPIC_MP !MPS_UP !MPS_MP !SGI_MPS_MP !SYSPRO_MP !SGI_MPS_MP
        devcon.exe sethwid @ROOT\ACPI_HAL\0000 := !E_ISA_UP !ACPIPIC_UP !ACPIAPIC_UP !ACPIAPIC_MP !MPS_UP !MPS_MP !SGI_MPS_MP !SYSPRO_MP !SGI_MPS_MP
        devcon.exe sethwid @ROOT\PCI_HAL\0000 := +%HAL%
        devcon.exe sethwid @ROOT\ACPI_HAL\0000 := +%HAL%
        devcon.exe update %windir%\inf\hal.inf %HAL%
        devcon.exe ReScan

        ECHO.
        ECHO ----------------------------------------
        ECHO Rebooting
        ECHO ----------------------------------------
        ECHO.
        devcon.exe Reboot
    ) ELSE (
        ECHO.
        ECHO ----------------------------------------
        ECHO Correct HAL Detected
        ECHO ----------------------------------------
        ECHO.
    )
GOTO :EOF
--------------------------------------------------------------------------------------------------------------------------------------

Then just above you mention:

@echo off
cd C:\SYSPREP

echo Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

echo Running sysprep and shutting down.
sysprep.exe -forceshutdown -mini -reseal -quiet -activated

And you also mention to add the line "UpdateUPHAL="ACPIAPIC_MP,%WINDIR%\inf\hal.inf"" to my SysPrep.inf - Should I just be using the last .bat or both or...?

Thanks

Last edited by Jack_F (2010-02-11 21:09:09)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

The second script

This is what I run right before I sysprep. This script syspreps my system with a few flags and tools I use. I use this tool to disable the intel ppm, so I can image AMD and intels. There is also a script re enables it called checkforintel.vbs\

This reenabled the intel ppm, if you are not doing AMD's don't worry about it.

http://blog.doylenet.net/?p=91

Has some good info here as well

I have this .bat in my sysprep folder

I also found you can script it to run the roe command before system if you ever forgot. I have done this before. Sysprep and didn't set the driver packs to run lol.

echo Driver Pack Scanner to run after next boot up
C:\Sysprep/ROE.exe 937

@echo off
cd C:\SYSPREP

echo Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

echo Running sysprep and shutting down.
sysprep.exe -forceshutdown -mini -reseal -quiet -activated

This is just used to sysprep the machine inside of running sysprep and selecting mini setup ect, this does everything for you with 1 click of a bat file.


Anyways for the 2 hal scripts. I'm just showing you 2 different ways to change the hal.
There is the offlinesysprep way (I can't get it working correctly as well)
The method i jacked off the net the 1st code (Works well)
And the lazy way UpdateUPHAL="ACPIAPIC_MP,%WINDIR%\inf\hal.inf
^ this just changes all cpus to muti, but works on uni just says it's a muit. (I have not see anything wrong with the way it works on a uni process, even tho it says it's a muti, they boot up and run fine, it's just the 1/2 assed way of doing things.

You can either do 1 or the other, i wouldn't do both.
-Quad

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Ok Guys

I thought this would be helpfull

Build your Images with VMware Server 2.0 or 1.9 doesn't matter
Download the Driver Packs and Applications the same as it says in the forums.
Use my scripts. And sysprep files, I deleted my personal info, just add in for yourself
You are more then welcome to use my scripts, this will switch over the hal and sysprep for you
No need to run ROE.exe 937 this does it for you, done via script.
Just run my RUN sysprep Scripts and follow the directions.
Please give it a shot and let me know.

Info Here
http://sites.google.com/site/sysprpeallday/

Files here
http://sites.google.com/site/sysprpeall … prepallday
I hope it's not a problem using my sysprep files and files I use to pervent sysprep errors
I did not put the devcon.exe in the script folder (Due to being a windows file) I don't want to cause any issues let me know if this is a problem.

I use winrar to rar the needed files. Use winrar and let me know how it goes
I didn't put much time into this so let me know if it's helpful.
Quad-Damage

Last edited by Quad-Damage (2010-02-25 06:57:20)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

http://sites.google.com/site/sysprpeallday/driverpacks

I do mine this way BTW

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

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.

Last edited by beltaine (2010-03-19 07:00:58)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

beltaine wrote:

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.

There's some glitch that I don't know why it happens for some that produces this issue. I have it fixed in my local version and there's a test version at 911cd forums. It happens with the option of automatically setting HAL upon first boot.

I hope to upload a new version soon. I would like to include the option of injecting out-of-the-box HWIDs first.

Regards,
Galapo.

Last edited by Galapo (2010-03-19 10:54:30)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

New version of OfflineSysPrep has now been uploaded at 911cd and boot-land.

Regards,
Galapo.

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

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.

Last edited by beltaine (2010-03-23 02:43:59)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

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.

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Spoke too soon.

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

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

There is a limit to the number of Mass Storage drivers you may add to a sysprep image. NTFS.SYS = You exceeded it wink (Out of memory Error)

the finisher does not install drivers - I repeat the DriverPacks Finisher does not install drivers.
the finisher installs related software for ALREADY INSTALLED drivers...
IE if the finisher finds an ATI card it installs the ATI control panel.
If it finds a sound blaster it installs/runs the SBSetup.exe, it "Finishes" installing drivers (that are already installed) where it is required.

the finisher DOES NOT install drivers wink... if it did we would have named it "installer" not "finisher" LOL

DP_Inst_Tool.cmd does install drivers

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Hi everyone,

firstly there is alot of information on here I have been reading through and it's been a steep learning curve for a first time sysprep'er

I am having a little trouble building a universal image (seems to be a HAL issue black screen on bootup before mini-setup)

I just wanted to show the way I have been doing it and ask for some pointers.

Windows XP x86 Sysprep image

1. I created a uni processor virtual machine in VMWare Workstation
2. Install all my windows updates the long way from windowsupdate.com
3. I copied the Windows XP service pack 3 sysprep to C:\SYSPREP
4. Extracted the Driver packs to C:\SOFTWARE\DRIVERPACKS\
5. Copied the Windows XP SP3 CD to C:\SYSPREP\i386
6. Edited my Sysprep.inf as follows

 

[Unattended]
    OemSkipEula = Yes
    OemPnPDriversPath = C:\SOFTWARE\DRIVERPACKS\D
    UpdateInstalledDrivers = Yes
    InstallFilesPath = C:\SYSPREP\i386
    DriverSigningPolicy = Ignore
    NonDriversSigningPolicy = Ignore
    
[GuiUnattended]
    AdminPassword="**********"
    EncryptedAdminPassword=NO
    AutoLogon=Yes
    AutoLogonCount=1
    OEMSkipRegional=1
    TimeZone=255
    OemSkipWelcome=1

[UserData]
    ProductKey=**************
    FullName="**********"
    OrgName="**********"
    ComputerName=WINXP-01

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=60

[TapiLocation]
    CountryCode=61
    Dialing=Tone
    AreaCode=02

[RegionalSettings]
    LanguageGroup=13,17,3,2,5,16,4,12,15,11,1
    SystemLocale=00000c09
    UserLocale=00000c09
    InputLocale=0c09:00000409

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

[Identification]
    JoinWorkgroup=WORKGROUP

[Networking]
    InstallDefaultComponents=Yes

[GuiRunOnce]
    Command0=%SYSTEMDRIVE%\SOFTWARE\SCRIPTS\SYSPREP\CheckForIntel.vbs

[SysPrepMassStorage]

7. In my CMD Lines I use this

[COMMANDS]
"%SYSTEMDRIVE%\SOFTWARE\SCRIPTS\SYSPREP\HalUpdate.cmd"
"%SYSTEMDRIVE%\SYSPREP\SYSPREP.exe -clean"

The Halupdate.cmd is the one from QuadDamage

I have also copied devcon.exe to C:\Windows so it's in the Path for that script.
I have copied all the relevant scripts to C:\SOFTWARE\SCRIPTS\SYSPREP
I have copied the Driverpacks exe's to C:\
I have edited the DriverPacks ini to be as follows:

[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot	= "%SystemDrive%\SOFTWARE\DriverPacks"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = "False"
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation	= "%SystemRoot%\SOFTWARE\DriverPacks\KTD"
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%\SOFTWARE\DriverPacks"
; enables/disables debug mode (enabled by default)
debug = "true"

I am using the Hal files supplied by Quad Damage and have copied those to C:\Windows\System32\

and then finally I run this batch file to start the process after stopping unnessary processes etc

C:\sysprep\sysprep.bat

ECHO.
ECHO This will tell Driver Packs to run after next reboot
%SYSTEMDRIVE%\DevPath.exe C:\

ECHO.
ECHO ROE Time
%SYSTEMDRIVE%\Sysprep\ROE.exe 937

ECHO.
cd %SYSTEMDRIVE%\SYSPREP

ECHO Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

ECHO.
ECHO Flushing data to disks (preliminary):
sync -r -e

ECHO.
ECHO Cleaning up old driver caches:
del /s /q %SYSTEMDRIVE%\WINDOWS\INF\Infcache.1

ECHO.
ECHO Closing open SMB connections:
net use * /delete /yes

ECHO.
ECHO Terminating unneeded processes:
pskill -t vptray
pskill -t ccapp
pskill -t explorer
pskill -t alg
pskill -t ati2evxx
pskill -t ccevtmgr
pskill -t ccsetmgr
pskill -t defwatch
pskill -t lucoms~1
pskill -t mdm

ECHO.
ECHO Stopping unnessary services:
net stop alerter /yes
net stop wuauserv /yes
net stop browser /yes
net stop cryptsvc /yes
net stop dhcp /yes
net stop mdm /yes
net stop trkwks /yes
net stop protectedstorage /yes
net stop remoteregistry /yes
net stop seclogon /yes
net stop samss /yes
net stop wscsvc /yes
net stop lanmanagerserver /yes
net stop "symantec antivirus" /yes
net stop defwatch /yes
net stop ccevtmgr /yes
net stop sndsrvc /yes
net stop ccpwdsvc /yes
net stop ccsetmgr /yes
net stop sens /yes
net stop srservice /yes
net stop schedule /yes
net stop lmhosts /yes
net stop ups /yes
net stop uphclean /yes
net stop webclient /yes
net stop audiosrv /yes
net stop sharedaccess /yes
net stop msiserver /yes
net stop w32time /yes
net stop wzcsvc /yes
net stop lanmanworkstation /yes
net stop spooler /yes

ECHO.
ECHO Flushing data to disks (finalization):
sync -r -e

ECHO.
ECHO Executing system preparation tool (reseal / minisetup)...
ECHO.
start sysprep -forceshutdown -reseal -mini -quiet

So what have I stuffed up?

It seems to get to the point before mini setup and sit there with a black screen - so it's a HAL issue I figure?

Also I am doing that correct for Driver packs to install the relevant drivers?

Once the sysprep is finished, I create an image using FOG, and then deploy that image also with FOG

EDIT: Forgot to mention, before I run sysprep.bat I run sysprep -bmsd and then use the FindHWID to scan the driver packs for Mass Storage drivers and add them to Sysprep.inf

Last edited by StylusPilot (2010-03-24 10:54:36)

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

Ok I changed a few things and it's working better

I am now using mysysprep with the CPU option for UP Hal or MP Hal and seems to work on a few more machines.

does anyone have a success rate of 90% and above? in a single universal image?

what do you guys do for the ones which don't work - make a complete seperate image?

Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04)

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.