I thought I should finally explain this not that I will be using it anymore but sysprep + driverpacks is VERY achievable AND miraculous and I've used it hundreds of times. Explaination The key to this is using the "keep the driver" option on your base ghost system that you sysprep and image. When you take this image and use it on another system all bts's drivers are scanned through when the system boots and therefore all the drivers are detected. The really miraculous part is that if you integrate the massstorage drivers this image can even work on sata systems. I was totally shocked when my lazy technician decided to use it on a sata nforce4 system and told him he was wasting his time. Instructions Prepare a bts slipstreamed windows xp install cd. You must include the massstorage driverpack manually in the OEM folder even though it's integrated in the slipstreaming process! You must also select the ktd option and method 2. To explain when you run bts's slipstream process it decompresses the massstorage pack and integrates it into windows. I just wanted to stress that the massstrorage pack also needs to go in the OEM folder on the CD. OEM is the bts created folder with all the other packs in NOT the OEM folder for oem preinstall. Install cd on the lowest spec machine most generic machine with the least hardware and ide interface (general good practice for sysprepping.) After installing you must edit c:\D\BTS_DPs_finish.cmd and remove all the ktd lines. :KtD_M2M3 SET tagfile=\I386 FOR %%i in (c d e f g h i j k l m n o p q r s t u v w x y z) do if exist "%%i:%tagfile%" set CDDRIVE=%%i: IF NOT EXIST %CDDRIVE%\I386\presetup.cmd GOTO KtD_M1 IF EXIST %DPS%\SetupCopyOEMInf.exe ( START %CDDRIVE%\OEM\bin\WatchDriverSigningPolicy.exe START /WAIT %DPS%\SetupCopyOEMInf.exe %DPS% TASKKILL /F /IM WatchDriverSigningPolicy.exe ) ELSE ( %CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemRoot%\Inf ) GOTO Cleanup :KtD_M1 IF EXIST %DPS%\SetupCopyOEMInf.exe ( START %DPS%\WatchDriverSigningPolicy.exe START /WAIT %DPS%\SetupCopyOEMInf.exe %DPS% TASKKILL /F /IM WatchDriverSigningPolicy.exe DEL /Q %DPS%\*.exe ) GOTO Cleanup :Cleanup IF EXIST %DPS%\BTS_DPs_cleanup.cmd START %DPS%\BTS_DPs_cleanup.cmd I was asked whether you could remove the drivers after the sysprep and yes you can if you leave the cleanup lines and put the cleanup file on c:\d. However this goes against ktd, windows will still think you have drivers installed for any hardware as the information files will still exist in c:\windows\inf create your c:\sysprep\sysprep.inf with a guirunonce line to trigger bts_dps_finish.cmd and buildmassstorage to support all massstorage devices. This is so when the sysprep runs on the target systems the right control panels will be installed but the drivers won't be integrated for a second time. run sysprep reseal. and image system. try it on a really complicated target!sysprep.inf [data] msdosinitiated="0" floppyless="1" AutoPartition="1" ;don't verify any files (allow patched windows files) UseSignatures=no InstallDir="\WINDOWS" EulaComplete=1 winntupgrade=no win9xupgrade=no ;no add users stuff unattendswitch=yes AutomaticUpdates=yes [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes ; allow f6 drivers OEMPreinstall=No WaitForReboot="No" UnattendSwitch="yes" Repartition=No DUDisable=Yes TargetPath=\Windows KeyboardLayout="United Kingdom" unused=unused NoWaitAfterGuiMode=1 NoWaitAfterTextMode=1 NonDriverSigningPolicy=Ignore DriverSigningPolicy=Ignore OemPnPDriversPath = KeepPageFile=0 [GuiUnattended] AdminPassword="xxxx" EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=85 OemSkipWelcome=1 [UserData] ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" FullName="test" OrgName="test" ComputerName=* productid="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" [Display] BitsPerPel=16 Xresolution=800 YResolution=600 Vrefresh=60 ;disable annoying is this resolution right box AutoConfirm=1 [TapiLocation] CountryCode=44 AreaCode=0113 Dialing=Tone [RegionalSettings] LanguageGroup=1 Language=00000809 SystemLocale=00000809 UserLocale=00000809 UserLocale_DefaultUser=00000809 InputLocale=0809:00000809 InputLocale_DefaultUser=0809:00000809 [FavoritesEx] Title1="http://www.google.co.uk.url" URL1="http://www.google.co.uk" [URL] Home_Page="http://www.google.co.uk" [Components] msnexplr=off AutoUpdate = On Media_clips = Off Media_utopia = Off Mousepoint = Off [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes [GuiRunOnce] command9= "%SystemDrive%\D\BTS_DPs_finish.cmd" [Sysprep] BuildMassStorageSection=yes [SysprepMassStorage] ---------------------- BUGS One bug I forgot to mention is when the sysprep image is starting up I sometimes get prompted for a cd at the first screen of the gui install. You must select cancel or everything goes tits up. ---------------- I've been asked whether you can run the integration on an already created image and i think it is possible. Just decompress all the packs to c:\D and copy all the 2 exes for bts's integration setupoem.exe and ignore...exe and the bts_finish.cmd. run the bts finish and the ktd process should kick off. THEN you edit the bts_finish.cmd and remove the ktd lines so it doesn't get kicked off after the sysprep. another qu :- Also while doing the actual sysprep, I got the driver signing pop up that asked me to "continue installation" or "Stop installation" of the drivers. Have you had that happen, if so how were you able to get rid of that? I have had this before. I think i got round it by using the simplest hardware config I could, also obviously make sure that all the drivers are found for the base image hardware. g.
