Tom Jones
January 6th 04, 12:02 AM
After I install Windows XP Pro I copy the I386 to the C: drive and change
the Installation Sources and SourcePath Keys in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Setup to point
at the C: drive so you never get asked to insert your Windows XP cd again.
When you run sfc /scannow to repair faults it fails because the folder is
read only (don't ask me why the system file checker needs the file to be
writable, but that's what I found on a microsoft site) but as far as I can
see there is no way to stop the folder being read only.
I think I have done everything. I've unchecked the 'read only' box and
applied the changes to the folders underneath, it appears to do it but the
next time you open the folder it's read only again. I've copied the folder
using XCOPY making sure not to copy the file attributes from the CD which
would obviously be read only. I've disabled 'simple file sharing' and
ensured I've full control, but none of this makes any difference, as far as
I'm concerned it's a bug in Windows XP Pro. My machine has all the latest
service packs and patches and I'm an administrator.
If anyone can throw some light on this I'd be more than grateful.
the Installation Sources and SourcePath Keys in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Setup to point
at the C: drive so you never get asked to insert your Windows XP cd again.
When you run sfc /scannow to repair faults it fails because the folder is
read only (don't ask me why the system file checker needs the file to be
writable, but that's what I found on a microsoft site) but as far as I can
see there is no way to stop the folder being read only.
I think I have done everything. I've unchecked the 'read only' box and
applied the changes to the folders underneath, it appears to do it but the
next time you open the folder it's read only again. I've copied the folder
using XCOPY making sure not to copy the file attributes from the CD which
would obviously be read only. I've disabled 'simple file sharing' and
ensured I've full control, but none of this makes any difference, as far as
I'm concerned it's a bug in Windows XP Pro. My machine has all the latest
service packs and patches and I'm an administrator.
If anyone can throw some light on this I'd be more than grateful.