Here's ONE file that just will NOT delete

[David Cook]

I had two separate Win-XP systems (separately bootable in the boot menu).

So, now I'm cleaning up the 2nd one (to get back to just one system).
And, I've removed it from BOOT.INI, etc, and I've managed to delete
ALMOST everything from that sub-tree.

(It was named C:\WINDOWS, but I've renamed it to C:\BROKEN_WINDOWS.
The good system is over in C:\WINXP.)

The file that defies being deleted is:
C:\broken_windows\Temp\hsperfdata_SYSTEM\3224
and I've used the utility 'attrib' to remove all the special 'S','R','H'
bits
off of this sub-tree. But the bottom-most file named '3224' just WILL
NOT DELETE.

What's the trick? (Or, is this file somehow super-important?)
I've always THOUGHT is was allowable to delete this unwanted
system-trees entirely.

TIA...

Dave

 

[Will Denny]

Hi

See if the following link to Kelly's web site helps:

Line 39 - right hand side:
http://www.kellys-korner-xp.com/xp_tweaks.htm

 

[David Cook]

Will -

Thanks, but no thanks. Sorry to turn my nose up at
what might solve the problem. But, I want to UNDERSTAND
the reason behind the problem (as well as to solve it). And, many
of those 'magic' little tweaks use binary mechanisms that only
deepen the mystery. I am also a 'student' of Windows NT and Win-XP
and I like to UNDERSTAND what is happening.
Stated yet another way, I believe that a solution exists that does
NOT require me to bring/install yet more executable widgets onto
my system. So, I will continue to look for that type of solution.

Any other ideas?

Cheers...

Dave

 

[Will Denny]

Hi

Did you click on the link to see where it goes?

 

[JAX]

All of Kelly's downloads, that I have taken, have offered the opportunity to
download and save. You can r-click and choose edit and see where and what
they are doing to the registry.

FWIW, JAX

 

[David Cook]

Ah, but that is yet another reason for caution.

If a 'fix' or 'change-of-behavior' is controlled by a registry-value,
then the usual caveat about damaging a system applies. I would argue that
it the only
thing keeping a file from being deleted is some registry-value, then
maybe there are excessive negative implications to un-doing it. Otherwise,
one
would think that they would use more obvious and well-understood
technique like 'attrib' values to keep one from deleting the file.

(In this case, you would think a file down in some sub-dir named 'TEMP'
would
be innocent enough. But, then why do they use such extreme technique to
prevent its deletion?)

 

[JAX]

Verbose is the word that comes to mind when reading your reply. If you
follow what I said, you can see which registry entry would be modified and
copy/remember what it was before the change.

JAX