Re: SFC /SCANNOW asking for files from non existent sources...

From: Ms. Linda A.W. (msnews_at_earthlink.net)
Date: 07/24/05 

Date: Sun, 24 Jul 2005 13:42:52 -0700

Peter wrote:
> ..Also, I just copied and pasted the i386 folder on C:\ not into any options
> folder.
> It's outlined here: http://www.updatexp.com/scannow-sfc.html
>
===
        Made further progress, but still have problems. The first I've run into
has SFC looking in the wrong place in "Service Pack 1" for a missing file:
"coadmin.dl_" (or .dll). On my SP1 CD (turns out it was included with a
book (Microsoft XP Inside/Out). The file is located at
<servicepack>/i386/ip/coadmin.dl_>.

Thinking my SP1 copy might be odd or corrupt, I just downloaded it just
now, again -- and have figured out "why", but not "why" (!?).
SFC is looking for a file COADMIN.DL_ (or .DLL). It is looking in the "i386/"
directory of the "ServicePackFiles" location, but in SP1, this file is located
at <servicepackpath>\"i386\ip\coadmin.dl_". I.e. not "i386\[filename]",
but in the subdirectory "ip/" under "i386/".

Thinking my SP1 copy might be "weird" for some reason, I just re-downloaded
the 126M SP1 patch. It still has the file "coadmin.dl_" located in the
subdirectory "ip".

Obviously, I can "kludge" around this by moving files from their proper location
to where "SFC" wants to see them, but this would involve me "corrupting" the
the SP1 image. I'm sure some of my other problems were (are) of this ilk as
well. Looking at the "DLL Help Database" for this file
(http://support.microsoft.com/dllhelp/?dlltype=file&l=55&alpha=coadmin.dll&S=1),
it seems only a small-business-edition has it in such a subdirectory, but I
can see the file in the "ip/" sub dir in the "xpsp1a_en_x86.exe" I just downloaded.

This seems a bit "whacked" that I should need to move ServicePack files around
to get SFC to work properly. The "coadmin.dll" is in the "i386" directory of
the original XP release.

I suppose I'll make a 2nd copy of the SP1 dir to contain my "modified" SP1
files, but this makes for a ugly hack -- especially since I have to run
sysinternal's "Filemon" to see what file it is looking for...(amongst tons of
output). 

---
Email:        to send me email, then my address would be like
                  'earthlink' was 'tlinx' and 'net' was 'org'

Relevant Pages

  • Re: Corrupted File
    ... SP1 installed when it became available, ... installation created from an original XP CD. ... The source paths in this situation are: One for the source at the time XP ... SFC has not seen the path ...
    (microsoft.public.windowsxp.basics)
  • Re: SFC SOURCE PROBLEM (THE COMMON ONE)
    ... John John wrote: ... your Windows XP quetions to an appropriate XP group. ... SFC problems. ... for the xp sp1 cd and I never had one to begin with. ...
    (microsoft.public.windows.server.general)
  • Re: Corrupted File
    ... Sharon, my XP installation is now 2 years old (re-installed once, early ... SP1 installed when it became available, ... When I ran SFC the ONLY source possible was the XP ... > There are source paths stored in the registry. ...
    (microsoft.public.windowsxp.basics)
  • SFC SOURCE PROBLEM (THE COMMON ONE)
    ... SFC SOURCE PROBLEM (THE COMMON ONE) ... for the xp sp1 cd and I never had one to begin with. ...
    (microsoft.public.windows.server.general)
  • Re: sfc says I have wrong disk?!
    ... Q. Will running an SFC /Scannow on an XP SP1 machine *keep* all updated ... SP1 intact? ... One thing you can do (best if you have two CD drives) is to burn that folder ... value to your hard disk path. ...
    (microsoft.public.windowsxp.general)