Re: sfc says I have wrong disk?!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: t.cruise (t__cruise_at_[NoSpam)
Date: 05/23/04


Date: Sun, 23 May 2004 12:53:58 -1000

Carefully read the page at the following link, and you should find the
solution to your problem:

http://www.updatexp.com/scannow-sfc.html

--
T.C.
t__cruise@[NoSpam]hotmail.com
Remove [NoSpam] to reply
"Tumbleweed" <tumbleweednews@mysockshotmail.com> wrote in message
news:40b11d68$0$1864$afc38c87@news.easynet.co.uk...
> Any ideas what to do if this doesnt work? I have Windows File Protection
> insistently asking for 'XP Pro Service Pack 1 CD to be inserted, but it
> doesnt like it even when it is. Have altered the various reg keys (as
below
> and in the rest of this thread) and copied the i386 folder, to no effect.
>
> I get this message every now and again after a reboot, or if i try sfc
> /scannow. cancelling out seems to cause no issues, but its getting
annoying
> enough I may go back to an earlier system restore version or even an
entire
> C: partition backup.
> --
> Tumbleweed
>
> Remove my socks for email address
> "R. McCarty" <PcEngWork-NoSpam_@mindspring.com> wrote in message
> news:ADSrc.19155$zO3.1335@newsread2.news.atl.earthlink.net...
> > Sorry, getting tired. The instructions are reversed. Switch
> > the change to values around make SourcePath = C:\ &
> > CDInstall = 0.
> >
> > "R. McCarty" <PcEngWork-NoSpam_@mindspring.com> wrote in message
> > news:GBSrc.19153$zO3.18113@newsread2.news.atl.earthlink.net...
> > > If you have adequate space on your drive do this.
> > > Copy the entire folder i386 from the CD-ROM to your
> > > disk drive. Place it in the Root Directory (Where Windows
> > > and Program Files are).
> > >
> > > Then type Start, Click Run (in the Box type ) Regedit
> > > Go to the following key
> > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
> > > (You navigate in Regedit just like Explorer by expanding
> > >   levels using the + & - symbols.
> > >
> > > Look in the Right Pane for two entries
> > > SourcePath
> > > CDInstall
> > >
> > > Place your mouse pointer over SourcePath and Right Click
> > > then Left click Modify
> > > Change the 1 to a 0
> > >
> > > Place your mouse pointer over CDInstall and Right Click
> > > then Left click Modify
> > > Change the value to read C:\
> > >
> > > Exit the Registry Editor, Reboot and re-try SFC, it should
> > > now work without the Nag screen about the CD.
> > >
> > > "dev" <dev@null.invalid> wrote in message
> > > news:OcAmr6FQEHA.628@TK2MSFTNGP11.phx.gbl...
> > > > /Linda/ said:
> > > >
> > > > > I have xp home upgrade version.  It is a legit copy, that
> > > > > was bought at staples.not to mention, it has the sticker
> > > > > also. When I go to RUN and type in sfc/scannow, it comes
> > > > > up to put my disk in. I do that then it tells me that it
> > > > > is the wrong disk, put xp pro in. I've never had xp pro.
> > > > > It was a new hard drive to begin with. A maxtor 120gb.A
> > > > > friend of mine, who went to school to become a tech guy(
> > > > > he graduated)told me to put on the hard drive xp. Not
> > > > > 98se then install xp home upgrade. He said that in the
> > > > > drop down menu to put in for a full install. I did that,
> > > > > of course, it asked for a legit OS, in which I did,
> > > > > 98se.Since I did not put 98se on first, would that make
> > > > > sfc not work in my xp home upgrade? i liked when it was
> > > > > on 98se. It used to keep 98 working great. I only needed
> > > > > to reinstall when our hard drive would go out. Thank You
> > > > > very much, Linda
> > > >
> > > > The query for PRO is a known oddity.  Pay it no mind, and simply
> > continue
> > > > the SFC /scannow process.
> > > >
> > > > If you are continually bugged for a disk, or receive a cryptic
prompt,
> > > > then it's likely that the registry entry for SourcePath is
incorrect.
> > It
> > > > should be pointing to the drive or directory (folder) on the hard
disk
> > > > from which XP was installed.  Here that's  H:\.
> > > >
> > > > If you are familiar with registry editing, correct that path, by
> > searching
> > > > for SourcePath.  There may be several, but ignore any that refer to
> > > > specific programs.  You want the entry that points to the drive or
> > > > directory on the hard disk from which the operating system was
> > installed.
> > > >
> > > > Caution:  Incorrect editing of the registry can cause XP to fail.
> > > >
> > > > --
> > > > For most XP answers and tweaks...
> > > > http://www.kellys-korner-xp.com/xp_abc.htm
> > > > http://dougknox.com     http://aumha.org
> > > > http://support.microsoft.com
> > >
> > >
> >
> >
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.690 / Virus Database: 451 - Release Date: 5/22/2004


Relevant Pages

  • Re: understanding function parameters
    ... fact a pointer to a daisy chain of standard pairs, ... structure and never modify any already-existing structure. ... The second function didn't modify the binding of its local copy of your ...
    (comp.lang.lisp)
  • Re: string litterals and char * and standard c
    ... that i can modify the string litteral through a pointer) ... string literal in the source code is char. ... any attempt to modify such an array invokes undefined ... welcome to clc: http://www.ungerhu.com/jxh/clc.welcome.txt ...
    (comp.lang.c)
  • Re: More pointer clarification
    ... If I declare a function and that function accepts int *x, ... The parameter receives a copy of a pointer which ... Your function 'doubleInt' does *not* modify ... For 'doubleInt' to modify what 'x' points to, ...
    (alt.comp.lang.learn.c-cpp)
  • Re: Can I modify a constant variable through a pointer obtained from const_cast?
    ... > if I could modify a constant variable through a pointer which has been ... If the original object is const, the compiler can substitute its values into ...
    (comp.lang.cpp)
  • Re: sfc says I have wrong disk?!
    ... CDInstall = 0. ... > disk drive. ... > SourcePath ... >> then it's likely that the registry entry for SourcePath is incorrect. ...
    (microsoft.public.windowsxp.general)