BillW50 wrote:
On 2/25/2014 10:34 PM, Paul wrote:
Good Guy wrote:
There are valid reasons for making a slipstreamed version.
For example, if your original WinXP installer CD is very old,
there might be limitations on initial disk drive size, or
a limitation on a built-in driver. (Can be tricky adding
the OS as a dual boot, fitting it to a partition located
on the high end of the disk, and so on.)

Great idea if you plan on installing it on other machines. Although if
we are talking about just one machine, backup and recovery does even
better. As not only do you have the latest SP, but also all of the
latest security patches, installed applications, all necessarily
drivers, etc.

The sad thing about backup and recovery method, is it's hard to test to
see if the recovery actually works. What I like even better is cloning
drives for backing up. Thus after cloning, I use the cloned one and put
the original away for safe keeping.

I did slipstreaming for that reason on Win2K, and made myself
a Win2K SP4 CD so I would be ready for anything. It would accept
drives over 137GB, no problem.

I am surprised you didn't include the Unofficial SP5 for Windows 2000
too. That includes all patches that was released after SP4.


Is the Rollup in a format suited to slipstreaming ? Or is your
"SP5" different than the Rollup ? AFAIK, the Rollup doesn't
materially change the Win2K OS, in terms of installation issues.
Your install would work as well, if only SP4, and then you
could run the Rollup .exe after that.

*******

Slipstreaming is for cases where the behavior of the initial
installation is potentially improved. Nobody wants to spend
their day using an old installer CD, and reading crap like this.

"EnableBigLba"
http://support.microsoft.com/kb/303013

It's just easier to use a slipstreamed installer CD, to
get past that point.

Paul