Re: Corrupted File
From: Len Dolby (lsdolby_at_ignore.ntlwor.com)
Date: 03/20/04
- Next message: Len Dolby: "MSXML in XP, which one ?"
- Previous message: Austin M. Horst: "Re: mmf files"
- In reply to: Sharon F: "Re: Corrupted File"
- Next in thread: Sharon F: "Re: Corrupted File"
- Reply: Sharon F: "Re: Corrupted File"
- Reply: Sharon F: "Re: Corrupted File"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 20 Mar 2004 12:34:42 -0000
Sharon, my XP (HE) installation is now 2 years old (re-installed once, early
days). SP1 installed when it became available, somewhat later. So, unlike
yours, my XP CD did/does not have SP1 included.
Your explanation has seemingly conflicting statements (most unusual for you,
I may add)
1/ ".... source paths stored in the registry - SFC will use those (option to
select only appears when needed)" implication being that source paths
(should be) updated in the registry.
2/ "You have personally used the source dialog to redirect ..." (which
conflicts with 1/ , in itself a conflict - either the paths are stored, or
not - either way, the stored path in my set-up is the XP CD, with no option
to redirect).
When I ran SFC (from a CMD DOS window) the ONLY source possible was the XP
CD - not editable.
Plus - it ran for some considerable time, then just closed at end with no
comment (should there not be a courtesy "No Problem found" (or "problem
fixed" info message, for courtesy?). That would reassure users, who have
posted same concern.
I do run MBSA, fairly often. Last run, same probs as before, posted before -
answer was the "problems" it highlighted are still probs, to be fixed in
SP2.
Sorry to be a pain, but my aged brain (poetry, yet!) can't quite grasp what
you say, on this occasion
Sincerely, Len
"Sharon F" <sharonfDEL@ETEmvps.org> wrote in message
news:uUQrVeeDEHA.624@TK2MSFTNGP10.phx.gbl...
> On Fri, 19 Mar 2004 12:57:02 -0000, Len Dolby wrote:
>
> > There is NO option to source the files from anywhere except the CD -
> > pointing to another source is not an option..
>
> There are source paths stored in the registry. SFC will use those. The
> option to select a source only appears when needed. I've used SFC a few
> times. Have the original XP installed with SP1 added. I have personally
> used the "source" dialog to redirect it to the Windows\ServicePackFiles
> folder. Then had to redirect it back to the XP CD again.
>
> If you are using a version of XP that included the SP1 files, it would
only
> have to check one source. In that case, it is very likely that you would
> not be prompted for a source since there is only one.
>
> After running SFC, I revisit the Update site. The presence of an update is
> detected in various manners: registry entries, presence of certain file
> versions. So Windows Update does sometimes prompt to install an update
> again. Usually at this point you are current with the file versions for
the
> most critical updates.
>
> If you want to dig a little deeper, HFNetchk and MSBSA (MS Base Security
> Analyzer) are good tools to run too. They will catch most other other
files
> that SFC might have overwritten with with older files. Both of those
tools
> are available for downloading from the Download center here:
> http://support.microsoft.com/default.aspx
>
> The point of using SFC is to get good working copies of core system files
> when you suspect there has been damage from viruses, hardware trouble etc.
> Even though you may have to play catchup with some updates, the basic
> functionality of any files replaced by SFC should be restored.
>
> --
> Sharon F
> MS-MVP ~ Windows XP Shell/User
- Next message: Len Dolby: "MSXML in XP, which one ?"
- Previous message: Austin M. Horst: "Re: mmf files"
- In reply to: Sharon F: "Re: Corrupted File"
- Next in thread: Sharon F: "Re: Corrupted File"
- Reply: Sharon F: "Re: Corrupted File"
- Reply: Sharon F: "Re: Corrupted File"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
