Re: XP version SFC /SCANNOW

You're welcome, Silvabod. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:xap4i.83$VS.17@xxxxxxxxxxxxxxxxxxxx,
Silvabod <nospam@xxxxxxxxx> hunted and pecked:
OK Wes, thanks a lot for all the help, advice and explanations.
Sil;vabod.
"Wesley Vogel" <123WVogel955@xxxxxxxxxxx> wrote in message
news:uSEsa%238mHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
Good news, I think.
Having read the article you referenced, created folder c:\I386 and
copied the ENTIRE I386 folder from my OEM CD - this includes subfolder
SP2. And,
"regedited" to point to C:\.

Super!

Rebooted, ran sfc/ scannow (which took about a half-hour to run, with
much
hdd activity) and no apparent error, it just c;osed on completion.

If SFC.EXE did anything it will be listed in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK | Click System |

Windows File Protection will be listed under the Source column. Look at
any
Windows File Protection entries.

BUT - I am still a little confused. I have NO directory folder
"ServicePackFiles" anywhere on my system, so (clip) Start | Run | Paste
this in the Open box: %windir%\ServicePackFiles |
Click OK (end clip) yields error message "cannot find it".

Cannot find it means it does not exist. The ServicePackFiles folder only
exists in certain conditions. I do not have one on either of my
machines. The ServicePackFiles folder only exists if you have upgraded to XP SP1 or
XP
SP2 and they were not included in the original install and the SP1 or SP2
upgrade was done by downloading it from Microsoft. If the Service Pack
is installed by means of a CD-ROM or a distribution share, the
ServicePackFiles
folder is not created. Same for slipstreaming a Service Pack.

%windir%\ServicePackFiles\i386 folder exists if the following conditions
are
true:
* You installed Windows XP SP2 from a Windows XP SP2 CD that included SP2
as
part of the base installation.
* You downloaded and installed Windows XP SP2 from the Microsoft Web
site. * Windows XP SP2 was included with the computer.

If the ServicePackFiles folder exists %windir%\ServicePackFiles\i386 is
used
instead of %windir%\system32\dllcache for Windows File Protection. If
the ServicePackFiles folder does not exist %windir%\system32\dllcache
folder is
used for Windows File Protection.

Please advise recommended path forward - should I create directory
"ServicePackFiles" and if so, exactly what should it contain?

Fugetaboutit. Keep having fun.

Most files that are protected by Windows File Protection are in the
System32
folder. If one of those files gets messed up WFP replaces that file with
a
copy from system32\dllcache folder or from ServicePackFiles\i386.

The thing is that WFP or sfc.exe has to know where to get the replacement
files from, which folder or the CD or where. That's what was messing you
up.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:A9g4i.1809$jr6.651@xxxxxxxxxxxxxxxxxxxx,
Silvabod <nospam@xxxxxxxxx> hunted and pecked:
Wes,
Good news, I think.
Having read the article you referenced, created folder c:\I386 and
copied the ENTIRE I386 folder from my OEM CD - this includes subfolder
SP2. And,
"regedited" to point to C:\.

Rebooted, ran sfc/ scannow (which took about a half-hour to run, with
much
hdd activity) and no apparent error, it just c;osed on completion.

BUT - I am still a little confused. I have NO directory folder
"ServicePackFiles" anywhere on my system, so (clip) Start | Run | Paste
this in the Open box: %windir%\ServicePackFiles |
Click OK (end clip) yields error message "cannot find it".

I'm a bit confused as to what the missing folder "Service Pack Files"
should contain. If it's SP2, then that now exists - in C:\I386/SP2.
There
have been at least 77 updates since SP2, many of which I believe
contain updated DLL's - all reported as being installed.

Please advise recommended path forward - should I create directory
"ServicePackFiles" and if so, exactly what should it contain?

I'm also slightly concerned about volume - I'd like to remove all
duplicate files (copying I386 and all subdirectories from OEM CD to C:/
must have left all the originally loaded system files in whatever
directory the manufacturer set up, and (my logic) must now be redundant?

"Wesley Vogel" <123WVogel955@xxxxxxxxxxx> wrote in message
news:O%230uackmHHA.4848@xxxxxxxxxxxxxxxxxxxxxxx
There is a registry entry that points sfc.exe to what folder to use to
replace damaged files. There are several. The question is what does
yours
need to point to?

Start | Run | Paste this in the Open box: %windir%\ServicePackFiles | Click OK

Does a ServicePackFiles folder open or do you get this error?

Windows cannot find 'C:\WINDOWS\ServicePackFiles'. Make sure you typed
the name correctly, and then try again. To search for a file, click the
Start button, and then click Search.

If %windir%\ServicePackFiles exists, the folder opened...

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

ServicePackSourcePath should be pointing to the location
C:\WINDOWS\ServicePackFiles (assuming C:\ is the boot drive).

Start | Run | Paste this in the Open box: %systemdrive%\I386 | Click
OK Does a %systemdrive%\I386 folder open or do you get this error?

Windows cannot find 'C:\I386'. Make sure you typed the name correctly,
and then try again. To search for a file, click the Start button, and
then click
Search.

If %systemdrive%\I386 exists, the folder opened...

This assumes C: is the hard drive and these are the settings that you
need.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
Value Name: CDInstall
Data Type: REG_DWORD
Value Data: 0

Value Name: ServicePackSourcePath
Data Type: REG_SZ
Value Data: C:\

Value Name: SourcePath
Data Type: REG_SZ
Value Data: C:\

If %windir%\ServicePackFiles and %systemdrive%\I386 do not exist...

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

Set both ServicePackSourcePath and SourcePath to your CD drive letter,
for example, D:\

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:URG3i.5583$GX1.1576@xxxxxxxxxxxxxxxxxxxx,
Silvabod <nospam@xxxxxxxxx> hunted and pecked:
I followed Wesley Vogel's advice (Thanks, Wesley!) and edited the
FP40*.inf entry. The IMS.inf entry didn't need an edit - already
contained "XP Home". (this latest post wasn't visible at the time).

Result - well, at least it's no longer asking for the XPPro/SP2 disk!

So - ran SCANNOW again, with manufacturers system disk in (it has a
separate file for SP2 on it) but, still no joy, it's still asking for
SP2 disk. I happen to have a separate Microsoft SP2 disk, so inserted
it - it doesn't like that one, either. (disk from when MS were giving
them out - it's for Home, Professional, Media Center and Tablet PC,
dated 2004) So, I'm still stuck - can't get "scannow" to work with
either the OEM XP
disk, or Microsoft's own SP2 disk, and no possibility of a "clean"
install. What now?

"Mark L. Ferguson" <MarkLFerguson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:4E2C8D69-49BE-4E44-9FE6-6788AD880AE9@xxxxxxxxxxxxxxxx
Those two articles change the 'cosmetics" of the [STRINGS] entry, or
write a
new path for the files. Those won't work if your 'recovery' is a
'mirror copy' of your original factory setup system, (which is likely
to be the case.)
--
Was this post helpful to you? Then click the "Yes" button, below.
Voting helps others who use the web interface.
Mark L. Ferguson



"Silvabod" wrote:

Sorry, Iceman - still asking for XP Pro/S[2 disk (and reporting
"wrong
disk"
And - I cannot exit Scannow - going to hyave to shut down/reboot to
get out,
it seems!

"Iceman" <ismand_57@xxxxxxxxxxx> wrote in message
news:u04L22hmHHA.3888@xxxxxxxxxxxxxxxxxxxxxxx
On Sat, 19 May 2007 13:10:03 GMT, Silvabod wrote in message
<news:LGC3i.2697$qQ1.355@xxxxxxxxxxxxxxxxxxxx>:

My OEM PC has XP Home/SP2 pre-loaded.
Have the "Product Recovery" manufacturer's CD incl XP and drivers,
which
"recovers", but cannot do a "clean" install.

I've posted earlier (problem with CHM files) but further reading
prompted
me
to run CMD = SFC /SCANNOW.

SCANNOW prompts me to insert the CD for XP PRO/SP2 - which I don't
have.

This PC has never had any OS other than the originally loaded and
genuine
XP
Home. I did a "recovery" a while back (subsequently
downloaded/installed
77
updates, so now allegedly completely up-to-date, with Auto-update
on).
Both
internal and external virus checks confirm no intections or
malware.

Following the SCANNOW prompt for CD, inserted the recovery
XPhome/SP2 disk,
no good, "wrong CD".

HELP!! Where's the need for "XP Pro" come from? How to correct?

Try inserting the CD *before* you run SCANNOW, not when XP calls
for it.

.