It is a little different depending on how SP1 was done. I believe that if you just make a registry change for the SourcePath, your issue will be sorted. But investigate Kelly Theriot's notes thoroughly under "S" here:
I have clipped what I think are the relevent portions, but your circumstances may differ from mine, as I use a slipstream of SP1 on some clients, but in all cases create an \i386 directory and modify the registry to point towards it for when a SFC operation is required:
Quoting the remarkable Kelly Theriot now:
SP1 - Slipstream and Repair (upgrading to SP1 (before), running a slipstreamed repair (after).
Before running a repair: C:\ServicePackFiles\i386
After running a repair: C:\Windows\Driver Cache\i386
If you perform a slipstreamed repair with a slipstreamed CD, the files are moved to C:\Windows\Driver Cache\i386. That is were windows stores the drivers so you don't need the CD and C:\ServicePackFiles\i386 is were SP1 stores the drivers.
Note: Once SP1 is installed, it places the system files of SP1 in a backup folder. If a repair is initiated, the files modified by SP1 are refreshed from this backup folder while the remaining non-SP1 affected files are refreshed from the WinXP CD.
SP1 - System File Checker
Q. Will running an SFC /Scannow on an XP SP1 machine *keep* all updated system files (found only on the hard drive and *not* on the XP CD) and leave SP1 intact?
A. The updated files are in the folder Windows\ServicepackFiles. The .inf files that tell SFC where to get copies from are modified so that for relevant files it goes there first.
One thing you can do (best if you have two CD drives) is to burn that folder complete to CD; then with go to Start/Run/Regedit and navigate to this key:
In the right pane, change the value of 'ServicePackSourcePath' accordingly; using the CD drive letter different from the original CD in 'SourcePath'. Then if files are needed you can have one CD in each drive.
********* end quote
Essentially I just slipstream SP1, then leave a full copy either on the local machine or a network share. I make the registry edit discussed above to unambiguously point to the \i386 folder wherever it is located for that client.
There is what I call the "Ultimate Slipstream", and access to the site is at times iffy. But it has incredible advice about how to slipstream nearly everything:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.