Show Posts
1
Tech Clinic / WinMe Hidden files
« on: February 21, 2005, 01:02:08 PM »
Hello, all-
I'm running a small PC here with limited resources. Up to a few months ago, everything OK. Recently, and only by accident, did I discover a hidden directory : C:\_restore and two hidden subdirs, C:\_restore\temp and C:\_restore\archive. These are filled with .tmp and .cpy files.
I'm watching my HD space diminish at an alarming rate; the PC is more sluggish than I recall. I have resorted to moving entire applications to the D: drive to lessen the load on the C: drive; I've removed unwanted cache and .tmp files, even gone to the point of removing .pdf files and the like that I no longer want.
These directories cannot be seen from normal WinME views, a search for *.tmp or *.cpy files shows nothing, and it it impossible to reset the attrib bits on these files to -r -a -s -h. "Access Denied"..
I want these files removed, and I'd really like to have control over the spawning of these files in the future.
At this point, the only option I can think of is to slick the HD and reload. I would not consider an OS change b/c of resource limits.
Can anyone help?
I'm running a small PC here with limited resources. Up to a few months ago, everything OK. Recently, and only by accident, did I discover a hidden directory : C:\_restore and two hidden subdirs, C:\_restore\temp and C:\_restore\archive. These are filled with .tmp and .cpy files.
I'm watching my HD space diminish at an alarming rate; the PC is more sluggish than I recall. I have resorted to moving entire applications to the D: drive to lessen the load on the C: drive; I've removed unwanted cache and .tmp files, even gone to the point of removing .pdf files and the like that I no longer want.
These directories cannot be seen from normal WinME views, a search for *.tmp or *.cpy files shows nothing, and it it impossible to reset the attrib bits on these files to -r -a -s -h. "Access Denied"..
I want these files removed, and I'd really like to have control over the spawning of these files in the future.
At this point, the only option I can think of is to slick the HD and reload. I would not consider an OS change b/c of resource limits.
Can anyone help?