I do not have a KB reference for you, though there
may be one covering this. What follows is the recipe
that I use - but I do not recall who/where all credits are
due any longer - but it works.
In your source tree make a new subdir i386\svcpack
Say you have a downloaded hotfix such as
x:\tmp\Q876543_w2k_sp4_x86_en.exe
copy /b this to i386\svcpack\Q876543.exe
(notice filename change)
Now in some work/scratch space unpack the hotfix
(can usually do this by running it with the /x switch)
Now, looking at the unpacked hotfix just obtained,
you will probably see some dirs, like sp1, sp2, common
and a couple files at the top.
Go to the sp2 dir if you are adding fixes that apply on
top of XP Sp1 (fixes that will be in Sp2)
From there copy the .cat file (or files) to i386\svcpack
Copy all other files (other than those that are part of the
update installer; that is copy the dll, sys, exe etc files or
an .\uniproc if existing) into \i386 (that is not i386\svcpack)
You can compare a few unpacked hotfixes to start to get an
idea of what is the fix code (to be copied) compared to what
is the update installer files.
OK, now final step is to edit i386\svcpack.inf
Here is example with MinorVersion, BuildNumber shown for w2k
[Version]
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=0
BuildNumber=219
[SetupData]
CatalogSubDir="\i386\svcpack"
[ProduactCatalogsToInstall]
Q876543.cat
[SetupHotfixesToRun]
Q876543.exe /q /n /z
To add more hotfixes, unpack, copy cat and files and
edit to add one line to each of last two sections.
Some hotfixes use different switches for unattended
install with no reboot, so check the KB article for
guidance (you will want to use /n:a syntax with some)
After you have added new fixes to the i386 tree, load
the source into SIS under a new name, adjust the sif
and commandlines.txt as usual, etc.
