[dlpirl]

Its not just me. I found some one else with the exact same problem at http://www.tek-tips.com/viewthread.cfm?qid...6715&page=2

I am using nLite 1.4.6 which is supposed to fix XP SP3 issues. I hate to abandon service pack slipstreaming using nLite. It looks like a great tool to simplify our new hardware builds. But does anyone have a solution to this issue?

This post has been edited by dlpirl: 20 June 2008 - 05:17 PM

[Yurij]

i think there is a commandline switch to slipstream sp3 with xp.
there is one for ordinary uppdates, it should be the same
example: updatefile.exe -s:<path to xp-cd files>
maybe that will work

[E-66]

Yurij, on Jun 21 2008, 05:50 PM, said:

i think there is a commandline switch to slipstream sp3 with xp.

Yep.  Here are two websites with a couple ways of slipstreaming by command line.  No doubt Google would find dozens more.

http://www.helpwithwindows.com/WindowsXP/S...ice_Pack_3.html

http://www.winsupers..._slipstream.asp

[Outcast]

Yurij, on Jun 22 2008, 05:50 AM, said:

i think there is a commandline switch to slipstream sp3 with xp.
there is one for ordinary uppdates, it should be the same
example: updatefile.exe -s:<path to xp-cd files>
maybe that will work

'-s' is the argument for old version of update.exe. Microsoft do not allow you to run update.exe directly for new hotfixes/updates. You'll have to run the integrate argument directly from the hotfix/update download.

WindowsXP-KB936929-SP3-x86-ENU.exe /integrate:<XP source path>

I don't know if nLite use the same method. Even though i use nLite but i don't 'trust' the built-in slipsteam funciton so I do it manually.

This post has been edited by Outcast: 23 June 2008 - 05:18 AM

[dlpirl]

Yes, I know about /integrate. I was hoping nLite would take care of this, but I no longer trust it, and also will need to do it "manually" using /integrate.