HKBoySiR

I packaged it into an MSI file. Let me know if you still need it or not via PM.

I will be on MSN in just a minute

One more question, which version of the OPK tools are you using to build WinPE? I'm using 1.2, or the one that comes with Server 2003.

Do you have an ftp site I can drop it on?

Could you PM or post your email address? I need to send you a zip file.

Crossing fingers! Hope this works for you as it did got me.

Try running inosetup.exe /S. Unfortunately, you will still have a GUI, but it will be completely seamless. No prompts or anything.

The only time I've seen that is when I forgot to add the Win51, Win51ip, and Win51ip.sp1 files in my cd root.

Hi all, this is my 1st post, so please don't be too harsh. :/ I stumbled upon this whitepaper, if it helps the whole process any. Seems like a lot of the scripts are leaving out a step or two. This scenario describes how to add a service pack and hotfixes to a distribution folder. Once complete, you will not need to perform separate installations of the operating system or the any hotfixes. When you install Windows, the Service Pack AND hotfixes will be applied during install. To create and set up the required folders and files 1. Connect to the network or computer on which you want to create the distribution folder. 2. In the shared folder on the network, create a distribution folder for the Windows 2003/XP installation files. For example, to create a distribution folder named W2003, type the following: mkdir Drive:\W2003\ Ensure that only the system administrator has full access to this folder. Other users should have only Read and Execute permissions. To verify that you have assigned the appropriate permissions, use steps 3 through 7 in the preceding procedure, “To install a hotfix by running a hotfix package from a shared distribution folder.” 3. Copy the contents of your Windows 2003 (or XP) CD, and then, using the following syntax, copy the contents of the CD to the distribution folder that you created in step 2: xcopy /E /I /V D:\i386 Drive:\W2003\i386 Note: You can also use the Windows Explorer to copy these files. Just be sure that you have “Show hidden files” turned on, as well as, the “Show system files” option. 4. Edit Drive:\i386\dosnet.inf to add svcpack to the [OptionalSrcDirs] section as follows: [OptionalSrcDirs] svcpack 5. Create a Drive:\i386\svcpack subfolder. 6. Copy the hotfix package (Windows2003-KB######-x86-LLL.exe ) to the Drive:\i386\svcpack folder by using the 8.3 naming format (KB######.exe), where ###### represents the actual hotfix number. If you are deploying multiple hotfixes, copy and rename all of the hotfix executable files. 7. Expand the hotfix to a unique temporary location. For example, to expand the files to a folder called samplefolder, type the following: Drive:\i386\svcpack\KB###### /X:Drive:\samplefolder 8. From samplefolder, for each hotfix, copy a catalog file (KB######.cat) and hotfix binary files (such as .exe, .dll, or .sys) as follows: a. Copy KB######.cat to the Drive:\i386\svcpack folder. If you are deploying multiple hotfixes together, copy the catalog file from each of the hotfixes to be deployed. Each hotfix has a unique catalog file that you must copy in the format KB######.cat. Do not copy empty.cat. b. If the same binary file exists in multiple hotfix packages, keep only the file with the highest version number. c. For each binary file included in the package, determine whether the same file exists in the i386 folder. (You can usually identify these files in the shared folder by the underscore (_) at the end of each file name.) Delete these binary files that will be replaced in the i386 folder. d. Copy the hotfix binary files and any subfolders for the hotfix to the i386 folder. For example, i386\uniproc\* files in the hotfix must be copied to the i386\uniproc folder of the shared installation folder. You do not need to copy Update.exe, Update.inf, SPmsg.dll, SPcustom.dll, SPuninst.exe, Update.ver, or symbols files. 9. For each file copied in step 10 (except for KB######.cat), check Dosnet.inf to determine whether each hotfix binary file name is listed under the [Files] section. All files listed under [Files] are preceded by “d1,”. This appears as follows: d1,Filename If a hotfix binary file name is not listed for each hotfix under the [Files] section, add an entry using the syntax: d1,Filename. For example, if a hotfix contains Win32k.sys, because Win32k.sys is not listed in Dosnet.inf, “d1,win32k.sys” must be added under the [Files] section of Dosnet.inf. This ensures that the hotfix version of Win32k.sys will be copied during Windows 2000 Setup. There are several files sections. Do a search to determine if the entry exists. You should find a large [Files] section that contains a list of all the files in the i386 folder. 10. Delete the Drive:\i386\Svcpack.in_ file. 11. Create a new Svcpack.inf file in Drive:\i386 by using the applicable following content, depending on whether you want to deploy a single hotfix or multiple hotfixes. (Replace ###### with the numbers for your hotfix.cat file). To deploy a single hotfix, set up your file as follows: For Windows XP: [Version] Signature=”$Windows NT$” MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir=”\i386\svcpack” [ProductCatalogsToInstall] KB######.cat [SetupHotfixesToRun] KB######.exe /options For Windows 2003: [Version] Signature=”$Windows NT$” MajorVersion=5 MinorVersion=2 BuildNumber=3790 [SetupData] CatalogSubDir=”\i386\svcpack” [ProductCatalogsToInstall] KB######.cat [SetupHotfixesToRun] KB######.exe /options The recommended options for hotfixes are /Q, /N, and /Z. These options prevent messages from being displayed on computers to which you are deploying the hotfixes. This makes the hotfix installation invisible to user. To deploy multiple hotfixes, set up your file as follows: If you are deploying multiple hotfixes simultaneously, add an entry for each hotfix under both [ProductCatalogsToInstall] and [SetupHotfixesToRun] (as shown in the example that follows). The following lines illustrate how these sections they would appear for an installation in which multiple hotfixes are installed. If you are installing a service pack, you do not need to include details about the service pack because it is included in the installation, independent of this process. [ProductCatalogsToInstall] KB123456.cat KB123478.cat KB123490.cat [SetupHotfixesToRun] KB123456.exe /options KB123478.exe /options KB123490.exe /options The recommended options for hotfixes are /Q, /N, and /Z. Deploy the Combination Installation You can deploy Windows 2003/XP and the hotfixes to multiple computers from a shared distribution folder on a network. During the standard installation process, Windows 2003/XP Setup installs the operating system and applies the hotfixes. You are now ready for installation. Once you have installed Windows 2003/XP, the hotfixes will automatically be installed