K
KenV
I tried to do a repair install (/not/ the recovery module) on a system with XP
Pro SP2 installed. but using the original XP disk with SP1. There were numerous
files that the installation process couldn't copy, despite the fact that in each
case I could see the file on the CD ROM that the install process was looking
for. For example, it wanted to copy a file I'll call "mdinit.dll". On the browse
screen it showed "mdinit" without the dll extension, but under file types grayed
out below, it said "mdinit.dll,mdinit.dll" as the files it was looking for, all
without the quotes, of course. It is as if it couldn't see the extensions and
thought the file wasn't on the CDROM under the i386 directory, which it was.
In regular Windows operation, under View, you can set it to view files with or
without showing the extension, and in this case, on the XP CDROM, it doesn't
show the extension, even though it is obviously there.
My XP repair install obviously didn't work well because of this. I even tried a
sfc /scannow with the XP CDROM in place, and it ran through that, but didn't
help.
Any way to get around this? I am trying to avoid a reformat and clean install in
order to keep my add-on progams, but it doesn't look promising.
Ken
Pro SP2 installed. but using the original XP disk with SP1. There were numerous
files that the installation process couldn't copy, despite the fact that in each
case I could see the file on the CD ROM that the install process was looking
for. For example, it wanted to copy a file I'll call "mdinit.dll". On the browse
screen it showed "mdinit" without the dll extension, but under file types grayed
out below, it said "mdinit.dll,mdinit.dll" as the files it was looking for, all
without the quotes, of course. It is as if it couldn't see the extensions and
thought the file wasn't on the CDROM under the i386 directory, which it was.
In regular Windows operation, under View, you can set it to view files with or
without showing the extension, and in this case, on the XP CDROM, it doesn't
show the extension, even though it is obviously there.
My XP repair install obviously didn't work well because of this. I even tried a
sfc /scannow with the XP CDROM in place, and it ran through that, but didn't
help.
Any way to get around this? I am trying to avoid a reformat and clean install in
order to keep my add-on progams, but it doesn't look promising.
Ken