How to slipstream hotfixes that replace pre-existing driver files
To slipstream the hotfixed file into a distribution share and make sure that Windows Setup does not use the pre-existing (in-box) version of the file instead of the hotfixed version of the file, follow these steps:
- Connect to the network or computer that you want to create the distribution folder on.
- Create an i386 distribution folder by typing the following (using the appropriate drive name): MD E:\i386
- Use the xcopy command-line utility to copy the files and subfolders from the Windows 2000 SP3, Windows XP, or Windows Server 2003 CD-ROM (integrated installation) to the E:\i386 folder. For example, if your CD-ROM drive is drive D, type the following: XCOPY /E /I /V D:\i386 E:\i386
- Create an E:\i386\svcpack folder. For example, to create a svcpack subfolder in the i386 folder, type the following: MD E:\i386\SVCPACK
- Copy the hotfix executable program (Qnnnnnn_XXX_YYY_ZZZ_LL.exe) to the E:\i386\svcpack folder by using the 8.3 naming format (Qnnnnnn.exe), where nnnnnn represents the actual hotfix number.
If you are deploying multiple hotfixes, rename all of the hotfix package files.
- Expand the hotfix to a unique temporary location. For example, to expand the files to a folder named samplefolder, type the following: E:\i386\svcpack\Qnnnnnn /X E:\samplefolder
- Copy the catalog files (.cat) and hotfix binary files (such as .exe, .dll, .sys), as follows:
- Copy Qnnnnnn.cat to the E:\i386\svcpack folder. If you will be deploying multiple hotfixes together, make sure that you copy all catalog files from each of the hotfixes to be deployed. Each hotfix has a unique catalog file that you must copy in the Qnnnnnn.cat format.
- If any binary files exist in multiple packages, keep only the file with the highest version number.
- Delete any binary files to be replaced in the i386 folder (typically you can identify these files in the shared folder by the underscore [_] at the end of each file name).
- Copy the hotfix binary files into the i386 folder.
You do not have to copy Update.exe, Update.inf, SPmsg.dll, SPcustom.dll, SPuninst.exe, Update.ver, or symbols (.pdb) files.
- Delete the E:\i386\Svcpack.inf file.
- Create a new Svcpack.inf file at E:\i386\Svcpack.inf, using the following content: [CatalogHeader]Important If you plan to deploy multiple hotfixes together, add an entry for each hotfix under both [ProductCatalogsToInstall] and [SetupHotfixesToRun] (as shown following this paragraph). The following lines are a sample of these sections for an installation that multiple hotfixes are installed in. If you are installing a service pack, you do not have to include details about the service pack because it is included in the installation independent of this process.
Q810400.exe /q /n /z[ProductCatalogsToInstall]
Q123456.exe /q /n /z
Q123478.exe /q /n /z
Q123490.exe /q /n /z
- Edit the E:\i386\Dosnet.inf file by making the following changes:
- Add the svcpack folder name to the [OptionalSrcDirs] section: [OptionalSrcDirs]
- Add the names of the hotfixed files to the [ForceCopyDriverCabFiles] section. This section is located at the end of the Dosnet.inf file. For example: [ForceCopyDriverCabFiles]
- Add the svcpack folder name to the [OptionalSrcDirs] section:
Note The instructions in this article are intended for slipstreaming driver-related hotfixes only. Non-driver hotfixes or security hotfixes must be slipstreamed by using the instructions that are documented in the following Knowledge Base article: For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Article ID: 814847 - Last Review: 12/03/2007 04:55:00 - Revision: 9.2
- kbhowto kbmgmtservices KB814847