C
clyde barrow
The files on the "Restore CD" of some OEMs (but not all)
can be copied. I have an eMachines (they no longer answer
my queries) and I suspect that it's one that uses an image
of the O/S. Some files/folders can be copied, but not the
system files. I used Find "i386" (Drive E and found
nothing. I need the original i386 folder copied to the
hard disk from the CD so that I can direct SFC to the
address from which corrupted/deleted system files can be
replaced. eMachines places a folder called Drivers (mostly
device drivers) on the hard disk, but it isn't by any
means all at which SFC needs to look.
Incidentally, SFC doesn't offer a browse feature; and
doesn't identify the bad file it detected.
I'm aware of the fact that I could use a copy of the i386
folder from a retail Windows XP Home CD, but I don't
really know anyone who would burn it for me.
Is there an applet, systems program, report - anything! -
that I could use to identify the bad file? That seems to
be my only hope.
can be copied. I have an eMachines (they no longer answer
my queries) and I suspect that it's one that uses an image
of the O/S. Some files/folders can be copied, but not the
system files. I used Find "i386" (Drive E and found
nothing. I need the original i386 folder copied to the
hard disk from the CD so that I can direct SFC to the
address from which corrupted/deleted system files can be
replaced. eMachines places a folder called Drivers (mostly
device drivers) on the hard disk, but it isn't by any
means all at which SFC needs to look.
Incidentally, SFC doesn't offer a browse feature; and
doesn't identify the bad file it detected.
I'm aware of the fact that I could use a copy of the i386
folder from a retail Windows XP Home CD, but I don't
really know anyone who would burn it for me.
Is there an applet, systems program, report - anything! -
that I could use to identify the bad file? That seems to
be my only hope.