Re: Sfc /scannow

John,
I have a related question for you.
A minor problem started when I started to make SlipStream SP2 disks

We have two Dell computers at home ( for my self and wife).
Mine is XP Pro SP1 and my wife, XP Pro SP1a.
While copying the XP Pro SP1 disk to a hard drive (at c:\xp\i386), one
file could not be read.
That was I386\LANG\SIMSUN.TT_ (5,321,389).
What I did was that I copied the same file from my Wife's XP SP1a disk and
pasted to c:\xp\i386. The file size was the same between two XP disks but
the date was different.
Then, SP2 was integrated without any hitch.

I wonder whether the replacement of the Simsun.tt_ from a different XP would
matter when I use the slipstreamed disk for sfc/ scannow or reinstalling
windows?
(I feel that the original XP SP1 probably cannot be used for installing
windows because of the corrupted file).

Regards,

Roman






"John John" <audetweld@xxxxxxxxxxx> wrote in message
news:O6gD8cZEIHA.536@xxxxxxxxxxxxxxxxxxxxxxx
You're welcome. It's a very good idea to have a CD with the same Service
Pack, if you ever need to do a repair install you will need it anyway, so
it's best to be prepared. One less hassle to deal with when disaster
strikes!

John

Roman King wrote:

John,

Since I did not have a slipstreamed SP2 CD, I did not try sfc /scannow
when I had problems with HDs two weeks ago.
Upon reading your post, I made a slipstreamed CD yesterday by following
Paul Thurrott's instruction.
I also created slipstreamed SP2 CD for my Dell computer (for home use).
Thanks again for the suggestion about slipstream.

Regards,

Roman




"John John" <audetweld@xxxxxxxxxxx> wrote in message
news:eh2FYZMEIHA.4880@xxxxxxxxxxxxxxxxxxxxxxx

Hi Gerry;

If you don't have a slipstreamed cd or if you don't have one at all (you
only have a service partition or a "restoration" cd) you can just change
the "SourcePath" in the registry and change the location of files so that
SFC will look in the i386 folder instead of the cd.

http://www.pchomecall.org.uk/support/sfc.htm

Regards;

John

Gerry wrote:


Roman

Before you move on regarding System File Checker. A lot of problems
resolve down to problematic drivers or memory. Where this is the case
you often do not know which it is so you work through the easier
solutions. If your Window XP CD contains the SP2 update using System
File Checker is an easy task. It's not easy if your original Windows XP
CD is pre SP2 as you need a slipstreamed CD to run System File Checker.
A slipstreamed CD is a CD where the contents of the original XP CD and
the SP2 update have been merged.







.

Relevant Pages

  • Re: Sfc /scannow
    ... copying files from a different computer wouldn't make any difference providing that it is the same Windows version and same service pack level. ... I can't be 100% sure but I don't think that it will make too much difference because when you slipstream SP2 the files in the i386 folder will be replaced with the ones from the newer SP2, but I don't know if that particular file will be replaced. ... What I did was that I copied the same file from my Wife's XP SP1a disk and pasted to c:\xp\i386. ...
    (microsoft.public.windowsxp.newusers)
  • Re: Internet Backgammon problem
    ... I'm using XP Pro SP2. ... || You WILL need a Windows XP installation CD that includes an I386 folder ... || How to slipstream Windows XP and Windows XP SP2 with AutoStreamer ...
    (microsoft.public.windowsxp.games)
  • Re: Create Slip Stream Win-xp in CD or only in DVD?
    ... You only need to slipstream Windows XP and SP2. ... > A full version of the Service Pack you want to slip stream. ...
    (microsoft.public.windowsxp.basics)
  • Re: not correct XP Pro OS
    ... So far all I have is 4 Slipstream copies of SP2 ... you can easily make a new Windows XP Pro ... the repair install. ...
    (microsoft.public.windowsupdate)
  • Re: not correct XP Pro OS slipstream not working
    ... the file copy fro xp pro disk locked up halfway ... and still got a SP2 CD-ROM. ... So far all I have is 4 Slipstream copies of SP2 ... you can easily make a new Windows XP Pro ...
    (microsoft.public.windowsupdate)