PDA

View Full Version : Slipstreaming to build XP-SP2 recovery disc


Bob Fliegel
January 23rd 05, 05:47 PM
PC Magazine of Feb 8, 05 includes instructions on building an XP-SP2 recovery
disc that requires slipstreaming SP2. Those instructions conclude with the
following statement: "(If it doesn't work, then your copy of Windows XP can't
be slipstreamed.)"

After running the integration routine, I received an error message that said
in effect the process could not be completed. I interpret this to mean that
my copy of Win XP Pro cannot be slipstreamed, but why not? Nowhere in the PC
"solutions" article does author David Karp explain why some copies can and
others can't. When I posted this query in PC mag's forum, I got the following
response:

"MS has put code into SP2 that checks the version of Windows you are
running. If it finds that you are using a copy of Windows that MS thinks has
been leaked (corporate version), it will not slipstream that version. If you
are not running the corporate version, and have tried to upgrade to SP2
[which I had done long ago] (or slipstream a copy of the disk) and failed,
contact MS and check out the help files."

I have searched the MS knowledgebase, but found not a single reference to
slipstreaming. Has anyone else here had this experience and, if so, how did
you get the slipstreaming process to run to completion?

Bob Fliegel
January 23rd 05, 05:55 PM
I misspoke when I wrote that the MS knowledgebase contains no reference to
slipstreaming. What I meant was that there's no reference that's directly on
point with regard to SP2.

"Bob Fliegel" wrote:

> PC Magazine of Feb 8, 05 includes instructions on building an XP-SP2 recovery
> disc that requires slipstreaming SP2. Those instructions conclude with the
> following statement: "(If it doesn't work, then your copy of Windows XP can't
> be slipstreamed.)"
>
> After running the integration routine, I received an error message that said
> in effect the process could not be completed. I interpret this to mean that
> my copy of Win XP Pro cannot be slipstreamed, but why not? Nowhere in the PC
> "solutions" article does author David Karp explain why some copies can and
> others can't. When I posted this query in PC mag's forum, I got the following
> response:
>
> "MS has put code into SP2 that checks the version of Windows you are
> running. If it finds that you are using a copy of Windows that MS thinks has
> been leaked (corporate version), it will not slipstream that version. If you
> are not running the corporate version, and have tried to upgrade to SP2
> [which I had done long ago] (or slipstream a copy of the disk) and failed,
> contact MS and check out the help files."
>
> I have searched the MS knowledgebase, but found not a single reference to
> slipstreaming. Has anyone else here had this experience and, if so, how did
> you get the slipstreaming process to run to completion?
>
>
>

Carey Frisch [MVP]
January 23rd 05, 06:12 PM
Slipstreaming a Service Pack requires a conventional Microsoft
retail or OEM installation CD. If you have a PC manufacturer's
Restore CD, such as a HP Restore CD, that will not work.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

----------------------------------------------------------------------------

"Bob Fliegel" wrote:

| PC Magazine of Feb 8, 05 includes instructions on building an XP-SP2 recovery
| disc that requires slipstreaming SP2. Those instructions conclude with the
| following statement: "(If it doesn't work, then your copy of Windows XP can't
| be slipstreamed.)"
|
| After running the integration routine, I received an error message that said
| in effect the process could not be completed. I interpret this to mean that
| my copy of Win XP Pro cannot be slipstreamed, but why not? Nowhere in the PC
| "solutions" article does author David Karp explain why some copies can and
| others can't. When I posted this query in PC mag's forum, I got the following
| response:
|
| "MS has put code into SP2 that checks the version of Windows you are
| running. If it finds that you are using a copy of Windows that MS thinks has
| been leaked (corporate version), it will not slipstream that version. If you
| are not running the corporate version, and have tried to upgrade to SP2
| [which I had done long ago] (or slipstream a copy of the disk) and failed,
| contact MS and check out the help files."
|
| I have searched the MS knowledgebase, but found not a single reference to
| slipstreaming. Has anyone else here had this experience and, if so, how did
| you get the slipstreaming process to run to completion?

Bob Fliegel
January 23rd 05, 06:51 PM
I do have a conventional MS retail CD of XP Pro and installed SP2 some time
ago.

"Carey Frisch [MVP]" wrote:

> Slipstreaming a Service Pack requires a conventional Microsoft
> retail or OEM installation CD. If you have a PC manufacturer's
> Restore CD, such as a HP Restore CD, that will not work.
>
> --
> Carey Frisch
> Microsoft MVP
> Windows XP - Shell/User
>
> Be Smart! Protect Your PC!
> http://www.microsoft.com/athome/security/protect/default.aspx
>
> ----------------------------------------------------------------------------
>
> "Bob Fliegel" wrote:
>
> | PC Magazine of Feb 8, 05 includes instructions on building an XP-SP2 recovery
> | disc that requires slipstreaming SP2. Those instructions conclude with the
> | following statement: "(If it doesn't work, then your copy of Windows XP can't
> | be slipstreamed.)"
> |
> | After running the integration routine, I received an error message that said
> | in effect the process could not be completed. I interpret this to mean that
> | my copy of Win XP Pro cannot be slipstreamed, but why not? Nowhere in the PC
> | "solutions" article does author David Karp explain why some copies can and
> | others can't. When I posted this query in PC mag's forum, I got the following
> | response:
> |
> | "MS has put code into SP2 that checks the version of Windows you are
> | running. If it finds that you are using a copy of Windows that MS thinks has
> | been leaked (corporate version), it will not slipstream that version. If you
> | are not running the corporate version, and have tried to upgrade to SP2
> | [which I had done long ago] (or slipstream a copy of the disk) and failed,
> | contact MS and check out the help files."
> |
> | I have searched the MS knowledgebase, but found not a single reference to
> | slipstreaming. Has anyone else here had this experience and, if so, how did
> | you get the slipstreaming process to run to completion?
>
>

Bill James
January 23rd 05, 06:59 PM
Perhaps you just need to make a new slipstreamed CD. Instead of mucking =
around with all the specific file copies for manually making a =
slipstreamed CD, do a Google search for autostreamer and use that =
application. Much easier and less change for errors.

--=20

Bill James
Microsoft MVP - Shell/User

Windows VBScript Utilities =C2=BB www.billsway.com/vbspage/
Windows Tweaks & Tips =C2=BB www.billsway.com/notes_public/

"Bob Fliegel" > wrote in message =
...
>I do have a conventional MS retail CD of XP Pro and installed SP2 some =
time=20
> ago.
>=20
> "Carey Frisch [MVP]" wrote:
>=20
>> Slipstreaming a Service Pack requires a conventional Microsoft
>> retail or OEM installation CD. If you have a PC manufacturer's
>> Restore CD, such as a HP Restore CD, that will not work.
>>=20
>> --=20
>> Carey Frisch
>> Microsoft MVP
>> Windows XP - Shell/User
>>=20
>> Be Smart! Protect Your PC!
>> http://www.microsoft.com/athome/security/protect/default.aspx
>>=20
>> =
-------------------------------------------------------------------------=
---
>>=20
>> "Bob Fliegel" wrote:
>>=20
>> | PC Magazine of Feb 8, 05 includes instructions on building an =
XP-SP2 recovery=20
>> | disc that requires slipstreaming SP2. Those instructions conclude =
with the=20
>> | following statement: "(If it doesn't work, then your copy of =
Windows XP can't=20
>> | be slipstreamed.)"
>> |=20
>> | After running the integration routine, I received an error message =
that said=20
>> | in effect the process could not be completed. I interpret this to =
mean that=20
>> | my copy of Win XP Pro cannot be slipstreamed, but why not? Nowhere =
in the PC=20
>> | "solutions" article does author David Karp explain why some copies =
can and=20
>> | others can't. When I posted this query in PC mag's forum, I got the =
following=20
>> | response:
>> |=20
>> | "MS has put code into SP2 that checks the version of Windows you =
are=20
>> | running. If it finds that you are using a copy of Windows that MS =
thinks has=20
>> | been leaked (corporate version), it will not slipstream that =
version. If you=20
>> | are not running the corporate version, and have tried to upgrade to =
SP2=20
>> | [which I had done long ago] (or slipstream a copy of the disk) and =
failed,=20
>> | contact MS and check out the help files."
>> |=20
>> | I have searched the MS knowledgebase, but found not a single =
reference to=20
>> | slipstreaming. Has anyone else here had this experience and, if so, =
how did=20
>> | you get the slipstreaming process to run to completion?
>>=20
>>

Carey Frisch [MVP]
January 23rd 05, 07:13 PM
If you slipstreamed any previous hotfixes into your Windows XP CD,
that will prevent slipstreaming in a Service Pack. Use your original
Windows XP CD to begin the slipstream process.

Either one of the following utilities makes slipstreaming
(integrating) SP2 into Windows XP a breeze:

Windows Slipstreaming and Bootable CD Guide
http://www.msfn.org/articles.php?action=show&showarticle=49

AutoStreamer 1.0.33
http://www.wbeta.com/comments.php?shownews=1063&catid=2

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

----------------------------------------------------------------------------

"Bob Fliegel" wrote:

> I do have a conventional MS retail CD of XP Pro and installed SP2 some
time
> ago.

Bob Fliegel
January 23rd 05, 07:45 PM
I found, downloaded, installed, and ran AutoStreamer, using my original XP
Pro disc in drive E:/, and the process appeared to run to completion, but
then the resultant .iso file never got copied to my RW disc in drive G:/.
Isn't that what's supposed to happen after the integration runs its course?

"Carey Frisch [MVP]" wrote:

> If you slipstreamed any previous hotfixes into your Windows XP CD,
> that will prevent slipstreaming in a Service Pack. Use your original
> Windows XP CD to begin the slipstream process.
>
> Either one of the following utilities makes slipstreaming
> (integrating) SP2 into Windows XP a breeze:
>
> Windows Slipstreaming and Bootable CD Guide
> http://www.msfn.org/articles.php?action=show&showarticle=49
>
> AutoStreamer 1.0.33
> http://www.wbeta.com/comments.php?shownews=1063&catid=2
>
> --
> Carey Frisch
> Microsoft MVP
> Windows XP - Shell/User
>
> Be Smart! Protect Your PC!
> http://www.microsoft.com/athome/security/protect/default.aspx
>
> ----------------------------------------------------------------------------
>
> "Bob Fliegel" wrote:
>
> > I do have a conventional MS retail CD of XP Pro and installed SP2 some
> time
> > ago.
>
>
>

Marko
January 23rd 05, 08:26 PM
Bob Fliegel wrote:
> I found, downloaded, installed, and ran AutoStreamer, using my original XP
> Pro disc in drive E:/, and the process appeared to run to completion, but
> then the resultant .iso file never got copied to my RW disc in drive G:/.
> Isn't that what's supposed to happen after the integration runs its course?

no, your cd writting software does that, it has to be compatible with
iso files, but then it won't recognize it otherwise
> "Carey Frisch [MVP]" wrote:
>
>
>>If you slipstreamed any previous hotfixes into your Windows XP CD,
>>that will prevent slipstreaming in a Service Pack. Use your original
>>Windows XP CD to begin the slipstream process.
>>
>>Either one of the following utilities makes slipstreaming
>>(integrating) SP2 into Windows XP a breeze:
>>
>>Windows Slipstreaming and Bootable CD Guide
>>http://www.msfn.org/articles.php?action=show&showarticle=49
>>
>>AutoStreamer 1.0.33
>>http://www.wbeta.com/comments.php?shownews=1063&catid=2
>>
>>--
>>Carey Frisch
>>Microsoft MVP
>>Windows XP - Shell/User
>>
>>Be Smart! Protect Your PC!
>>http://www.microsoft.com/athome/security/protect/default.aspx
>>
>>----------------------------------------------------------------------------
>>
>>"Bob Fliegel" wrote:
>>
>>
>>>I do have a conventional MS retail CD of XP Pro and installed SP2 some
>>
>>time
>>
>>>ago.
>>
>>
>>

--
Marko Jotic
"Common sense is anything but common".
From the notebooks of Lazarus Long. Robert A. Heinlein.
Handmade knives, antique designs, exotic materials at
http://www.knifeforging.com/

Carey Frisch [MVP]
January 23rd 05, 08:51 PM
IsoBuster 1.7
http://www.smart-projects.net/isobuster/

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

----------------------------------------------------------------------------

"Bob Fliegel" wrote:

| I found, downloaded, installed, and ran AutoStreamer, using my original XP
| Pro disc in drive E:/, and the process appeared to run to completion, but
| then the resultant .iso file never got copied to my RW disc in drive G:/.
| Isn't that what's supposed to happen after the integration runs its course?

Bob Fliegel
January 23rd 05, 08:59 PM
I discovered that the SP2 .enu file that I'd placed in c:/xp before
attempting the integration has been replaced by a folder entitled WXPCCP_EN
(319MB), which I next wrote to my RW disc. Am I on the right track here?


"Carey Frisch [MVP]" wrote:

> IsoBuster 1.7
> http://www.smart-projects.net/isobuster/
>
> --
> Carey Frisch
> Microsoft MVP
> Windows XP - Shell/User
>
> Be Smart! Protect Your PC!
> http://www.microsoft.com/athome/security/protect/default.aspx
>
> ----------------------------------------------------------------------------
>
> "Bob Fliegel" wrote:
>
> | I found, downloaded, installed, and ran AutoStreamer, using my original XP
> | Pro disc in drive E:/, and the process appeared to run to completion, but
> | then the resultant .iso file never got copied to my RW disc in drive G:/.
> | Isn't that what's supposed to happen after the integration runs its course?
>
>

Google