D
Doug W.
Three weeks ago, and after a half dozen attempts to install XP
SP3 using different scenarios and subsequent crashes on re-boot
and BEFORE I found out about the screw-up with the intelppm.sys
in regard to AMD 64 Athlon, a whole raft of system files were
left in windows/system32 folder with appended
(2),(3),(4),(5),(6) as well as the correct one with the new
version number that SP3 called for. Some were as
(3) to (7) consecutively appended.
This left many, many useless executables and .dlls which take up
a lot of space and are unnecessary.
As far as I have checked all of the appended files have the OLD
version number (pre SP3).
-
example:
lsass(2).exe
lsass(3).exe
lsass(4).exe
lsass(5).exe
lsass(6).exe
lsass.exe
What would be the best procedure to use to clean this mess up? I
don't believe Windows XP will allow me to delete legitimate
files but I don't want to take a chance either.
-
Doug W.
-----------
SP3 using different scenarios and subsequent crashes on re-boot
and BEFORE I found out about the screw-up with the intelppm.sys
in regard to AMD 64 Athlon, a whole raft of system files were
left in windows/system32 folder with appended
(2),(3),(4),(5),(6) as well as the correct one with the new
version number that SP3 called for. Some were as
(3) to (7) consecutively appended.
This left many, many useless executables and .dlls which take up
a lot of space and are unnecessary.
As far as I have checked all of the appended files have the OLD
version number (pre SP3).
-
example:
lsass(2).exe
lsass(3).exe
lsass(4).exe
lsass(5).exe
lsass(6).exe
lsass.exe
What would be the best procedure to use to clean this mess up? I
don't believe Windows XP will allow me to delete legitimate
files but I don't want to take a chance either.
-
Doug W.
-----------