mm said:
Most people seem to have no trouble with the various means of
slipstreaming, but I tried all but one of them and couldn't get it.
It kept failing at the step just before making the .iso file. (I
tried several times on more than one box, wth both 2000 and XP,
with more than one version of Slipstream (even though I'm sure they
were all identical.))
Is it possible to do it myself "by hand". That is, expand the file
on the XP CD and the file on the SP2 CD, each to their own directory
tree, and then copy** all the files from SP2 to each's appropriate
XP directory. So that new files are added, and files with the same
name are replaced.*** Then do the same thing with SP3, and then do
the final steps (borrowed from the detailed slipstream procedure)
to make a bootable .iso file, and burn it.
**Using Windows Explorer Copy to copy multiple files, or DOS XCOPY,
or XXCOPY, which is similar but has more options. With Windows
Explorer for each file one is replacing, one might have to answer
"You already have a file of this name with this date and length.
Do you want to replace it?" But with XCOPY I think and for sure
with XXCOPY, there is a parameter that says "Always replace it".
Doesn't one *always* want to replace a file on the original CD with
one from a later Service Pack?
***Would replacing the files be a problem? IIRC the files are at
the same place in the folder heirarchy as the files they are meant
to replace. So just saying XCOPY C:\SP2\*.* C:\XP /S plus
whatever parameters make it copy hidden and system files and
I'm done with the first step. Then do the same thing with SP3.
Would this work?
My suggestion (made elsewhere as well):
Many people utilize tools like AutoStreamer or nLite to intgrate/slipstream
updates into the installation media. nLite (I believe) has a way/hack that
'integrates' Internet Explorer 7 - but to be honest, _I_ would not do that.
Getting the updates - that is fairly simple.
One way...
You can see the critical (security and other) patches released for a given
month using the following:
http://www.microsoft.com/technet/security/bulletin/ms##-***.mspx
At the end of this line you see "ms##-***.mspx" .. If you simply replace ##
with the two-digit year and the *** with the three character month
abbreviation, you will see the list of "critical" and "important" patches
for that month (since it only happens once a month usually, if you check by
the second Tuesday (wait until afternoon) of each month - you should be
fine) - note that future months will not work - although they may have an
"Advance Notification for" in place when the actual time approaches.
Example:
November 2009
http://www.microsoft.com/technet/security/bulletin/ms09-nov.mspx
Another way...
Windows Updates Downloader
http://www.windowsupdatesdownloader.com/
Another way...
Security updates are available on ISO-9660 DVD5 image files from the
Microsoft Download Center
http://support.microsoft.com/kb/913086
The second is truly the easiest for most people. Most of the updates you
can get have an /integrate switch. Pretty much the same way you do the
service packs.
Although many people use the nlite/autostreamer and other similar tools - I
stick with the original.
Copy the installation CD files to a directory on a Windows XP system (I
prefer doing the integration on a working system of the same version,
although it is not usually necessary...) - preferably a short path like
"C:\WinXP". Downloading the full latest service pack and the patches I want
to integrate using one of the methods above and putting them all into a
different (but short as well) path like "C:\XPPatch" - no sub-directories.
Integrating the service pack first - in this case, given what I have, the
command would be:
"C:\XPPatch\WindowsXP-KB936929-SP3-x86-ENU.exe" /integrate:C:\WinXP
and after some time, it would be done.
Then I would integrate the other patches that I could. There would be
*quite a few* updates, so I could either do them one-by-one using this
command with the appropriate substitutions...
"C:\XPPatch\WindowsXP-KB??????-x86-enu.exe" /integrate:C:\WinXP
Or I could create a batch script to run through and do them for me:
<start batch script here - copy below this line>
set sourcedir=C:\WinXP
set patchdir=C:\XPPatch
for %%U in (%patchdir%\WindowsXP-KB??????-x86-enu.exe) DO (
if not exist %svcpackdir%\%%U (
@ECHO Now integrating %%U . . .
@ECHO.
start /wait %%U /integrate:%sourcedir%
)
)
@ECHO Windows XP Updates Integrated into your Installation Media.
@ECHO Burn your new media.
<end batch script here - copy above this line>
And running that would integrate the majority of the available patches and
automatically integrate them - only pausing for me to click OK on each of
the patches "Success" or "Failure" messages. You could make it silent with
a little modification.
The reason it cannot get them all is that some patches do not integrate and
some do not use the same naming scheme (although you could rename them so
they do...)
I then use BBIE (Bart's Boot Image Extractor) to take the 'boot image' off
the original Windows XP CD and save it to a file so I can burn a bootable
Windows XP CD with the integrations I have made. Depending on what CD
burning software or ISO creation software you use - the instructions can
differ a bit here... This part is important when burning to CD: Set Load
segment of sectors (hex) to 0000 and set Number of loaded sectors to 4. Or
at least that is something I always remember.
That's just the way I have done it - even though I have used the other
methods, I find that one the most reliable.
That help?
