Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
JAX said:After installing SP2, will sfc still work with the original XP SP1
disk, or will it be necessary to create a "slipstreamed" CD to
perform the task? I was unable to locate any information directed to
this question on a Google search.
TIA, JAX
Quaoar said:SP2 appears to update the existing SP1 i386 folder so that sfc /scannow
SP2 does not need the CD. If you do not have i386 on the HD prior to
installing SP2, you can simply copy it from the Windows install CD to the
Windows folder, and change the install directory location.
http://www.petri.co.il/change_default_location_of_the_i386_folder.htm
Q
Jim Byrd said:Hi JAX - Just a small FYI - Be aware that if you've slipstreamed SP2 into
an
on-disk i386 folder (or any other SP in either XP or Win2k, for that
matter), you will need to re-install the Recovery Console (if you want it
installed, which is usually a good idea).
--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP
In
Quaoar said:SP2 appears to update the existing SP1 i386 folder so that sfc /scannow
SP2 does not need the CD.
Alex Nichol said:What happens is that it makes a 'ServicePackFiles' folder in Windows
(containing an i386 one). that has the SP2 files, and there is a
registry entry that tells things like SFC, new hardware, File
Protection etc to look there first for needed files. But that is not
every file in the system, so it still may need to fall back in the
original CD if it fails to find one
Alex Nichol said:What happens is that it makes a 'ServicePackFiles' folder in Windows
(containing an i386 one). that has the SP2 files, and there is a
registry entry that tells things like SFC, new hardware, File
Protection etc to look there first for needed files. But that is not
every file in the system, so it still may need to fall back in the
original CD if it fails to find one
Alex Nichol said:What happens is that it makes a 'ServicePackFiles' folder in Windows
(containing an i386 one). that has the SP2 files, and there is a
registry entry that tells things like SFC, new hardware, File
Protection etc to look there first for needed files. But that is not
every file in the system, so it still may need to fall back in the
original CD if it fails to find one
This might be a 2nd msg with the first one blank -- was looking for a ne msgAlex Nichol said:What happens is that it makes a 'ServicePackFiles' folder in Windows
(containing an i386 one). that has the SP2 files, and there is a
registry entry that tells things like SFC, new hardware, File
Protection etc to look there first for needed files. But that is not
every file in the system, so it still may need to fall back in the
original CD if it fails to find one
Miles said::
This might be a 2nd msg with the first one blank -- was looking for a ne msg
screen which didn't appear! SFC /scannow does not work on my machine --
continuously asks for the WinCD and won't accept the SP2 CD. Do you happen
to know what the settings should be in the reg to fix this?
Miles
So could my reg be incorrect in that it is looking at C:\ as the sourceMiles said:
Ran it three times and each time it needed the WinXP CD and I had to hitRock said:See this article:
http://www.updatexp.com/scannow-sfc.html
Ran it three times and each time it needed the WinXP CD and I had to hit
"retry" 10 times -- meaning that it was missing at least 10 files in
C:\Windows\DVD cache and in C:\windows\i386, and they were not added.
This suggests that every time SFC /scannow is run it will require the
CD. Running it weekly prior to imaging, plus whenever a program is
installed, certainly will cause it to wear out or I'll somehow damage
it. This means that I will no longer run SFC on a regular basis.
Hopefully, MSFT has a fix or soon will have a fix for this, but I
haven't yet found it on their site -- haven't even found complaints!
Miles
Historically installing programs would replace a dll with one of theirRock said:Miles wrote:
I don't know why you have run sfc on a regular basis anyway. In over
two years I ran it twice, once under SP1 to see if it would resolve an
issue (it didn't) and then under SP2 just to see if it worked (after
the SP2 upgrade I moved several of the directories to CD and changed
the registry to point to them). I wanted to make sure sfc saw the
right location and ran properly, in case I someday do need it. If the
system is maintained properly and safe computing is practiced then
there is no reason to run it.
Miles said:Ran it three times and each time it needed the WinXP CD and I had to
hit "retry" 10 times -- meaning that it was missing at least 10 files
in C:\Windows\DVD cache and in C:\windows\i386, and they were not
added. This suggests that every time SFC /scannow is run it will
require the CD. Running it weekly prior to imaging, plus whenever a
program is installed, certainly will cause it to wear out or I'll
somehow damage it. This means that I will no longer run SFC on a
regular basis. Hopefully, MSFT has a fix or soon will have a fix for
this, but I haven't yet found it on their site -- haven't even found
complaints!
Miles
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.