Removing .TMP files

[rada...@nospam.com]

Searching for *.TMP, I found 56 of them. Over 40 are in the AVG folder
and are all 1K in size. There are 3 large ones in the WINDOWS folder
around 2500K in size. I already deletd all the ones in the AVG folder,
and several mor tha were 0 bytes, but what about those bigger ones in
the WINDOWS folder. Can I delete them?

This is in XP Pro Sp3.

[Michael]

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/disk_cleanup_overview.mspx?mfr=true

[rada...@nospam.com]

On Wed, 22 Jul 2015 14:56:30 +0200, Michael <Conjure...@t-online.de>
wrote:

Go there to get this message .. .. .. ..

"We are sorry, the page you requested cannot be found".

[Paul]

Use CCleaner to automate some of these cleaning tasks.
*Don't* use anything on the registry. The registry
takes care of itself, and I've never used anything
on any registry here.

http://www.piriform.com/ccleaner

You can find an Environment variables dialog in the
System control panel. It will give you a path to your
account temporary directory, as well as a system one.
A total of two different paths.

%USERPROFILE%\Local Settings\Temp ==>
C:\Documents and Settings\Username\Local Settings\Temp

C:\WINDOWS\Temp

Temporary files which you can delete, when you attempt
it, they will go. Temporary files which are still in
usage, should have a file lock on them, to prevent deletion.
The system will "burp" an alert, and the files will
remain in the temp. (Until after the next reboot,
when they'll be released.) Right after a reboot, is
the best time to clean out the pig pen.

*******

To free up disk space (emergency cleaning)

1) Turn System Restore off and on. See the
System control panel, for the Tab that has the
System Restore dialog in it. There is also a place
to set the size of disk (max) that can be used for
restore points. One valuable resource that SR keeps
for you, is copies of the Registry. Those are
collected, one a day, for you. A setting of 3GB for
SR space, should be enough as a max.

2) In Adobe Reader, go to Preferences, and locate the cache.
There should be a button to clear it. That'll save a
few hundred megabytes. The cached info speeds up document
searches.

3) Disable hibernation, so that the system no longer
needs a hibernation file. On Win7, this would be
"powercfg -h off", dunno about WinXP.

4) Adjust pagefile. I've set my pagefile to a fixed
size, and made it half the size "recommended" by
Windows. On one of my other machines, the one with
gobs of RAM, I set it to 1GB (since the OS didn't
like my attempts to set values in the hundreds of
megabytes range).

5) Internet Explorer (obviously) has a cache. Some people
dial that up for some reason, and it can contain
hundreds of thousands of files if you do that. I
don't use IE, and have no idea what a "reasonable"
setting is for the cache. Use the preferences to
adjust it.

6) Get a copy of Windirstat and have a look around.
There must be more places you can look.

https://en.wikipedia.org/wiki/WinDirStat

http://windirstat.info/ (0.6MB download)

7) A copy of 7ZIP, and using the 7z compressor, can
free up space too. But things like movies are already
compressed 100:1. Many modern formats, you cannot compress
and squeeze any more fat from them. It's only a few
things, like some text log files I've created on
occasion, where you can save a lot of space. For
example, 300MB of directory listings generated yesterday,
are squeezed down to 4MB today.

Version 9.20 is good

http://www.7-zip.org/

Note that 7ZIP uses a palpable amount of energy. It
costs around $1 in electricity, to compress an entire
disk drive for archival storage. That's when my 156W
CPU runs all day, doing the compression, and uses all
cores while doing so. 7ZIP loves CPU cache, fast memory,
and is one of the few programs to show differences between
the various CPUs you bought. For example, two otherwise
similar CPUs ("feel the same" when browsing), one
does 7ZIP at 60% of the speed of the other CPU.
One CPU had a 2MB cache, the other a 6MB cache.
For most other software, you wouldn't even know the
CPU had a cache :-)

Compression isn't a particularly effective way to manage
space. You need room to decompress later. Room to juggle
stuff. It's a nightmare.

And the NTFS full disk compression setting (causes the
color of filenames to change to blue), that's a piss poor
compressor. It's something like LZO, a lightweight
compression method, which slows down the disk a lot.
It isn't even remotely close to compressing as much
as 7ZIP. Yet Microsoft continues to invoke that
stupid thing. Microsoft does know how to do compression - see
the Win10 download delivery, for an example of how good
a job they can do when they put their minds to it.

Rules for compression:

1) Only compress once. Don't "WinZIP then 7ZIP". Start
with raw files, then 7ZIP them. The highest compression
ratio comes from giving a compressor the raw files to
look at. 7ZIP has a pre-processor that looks for ways
to do a better job (it re-codes EXE files to save space).
7ZIP is lossless, so the files will not be damaged.

2) You have space-time tradeoff options. Things like
GZIP flavor compression, the compression runs faster,
but it doesn't save as much space (it's better than the
NTFS disk compressor though). Sometimes, this is
the right answer for the situation. A parallel GZIP
compressor called PIGZ exists, if you have a multi-core
processor and want speed. But the Windows port of PIGZ
doesn't do a good job on the file header, and if you want
to use PIGZ, use the Linux version. The person who did the
Windows port, it was a one-off effort. It's probably
a three line code change, to make it as good as the
Linux one. The size fields need to be fixed.

And even Linux has a 7z compressor, if you need it.

Happy cleaning,
Paul

[Nil]

On 22 Jul 2015, rada...@nospam.com wrote in
microsoft.public.windowsxp.general:

>>http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs /en-us/disk_cleanup_overview.mspx?mfr=true
>
> Go there to get this message .. .. .. ..
>
> "We are sorry, the page you requested cannot be found".

Works for me. Be sure to unwrap the URL.

[Nil]

On 22 Jul 2015, Nil <redn...@REMOVETHIScomcast.net> wrote in
microsoft.public.windowsxp.general:

A spurious space crept into my last post. Use this link instead:

>> http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/disk_cleanup_overview.mspx?mfr=true

[rada...@nospam.com]

On Wed, 22 Jul 2015 16:02:19 -0400, Paul <nos...@needed.com> wrote:

>
>Use CCleaner to automate some of these cleaning tasks.
>*Don't* use anything on the registry. The registry
>takes care of itself, and I've never used anything
>on any registry here.
>

CCleaner was already on this computer.... That was handy!

I've used an older version of that on Win98 for years too.

[Henry]

CCleaner +1

You can get rid of the temp files by going to run and typing %temp%

That will bring up the temp folder. Highlight them all and right click
delete. Some may not delete
because they are being used by a program. That's OK

Henry

[micky]

In microsoft.public.windowsxp.general, on Wed, 22 Jul 2015 07:05:02

I tend to leave tmp files that are less than 3 months old, as if it was
in the miiddle of doing something and got interrupted and it will come
back and do it later. But that's never happened. Once it gets
interrupted, like by a crash, or by my restarting the computer when it's
working on something, it doesn't restart that sort of thing.

The only thing that restarts probably doesn't use a tmp file, and that's
restarting Firefox, and it says that it lost all the previous tabs, but
then sometimes when it starts the next time, they're back.

And sometimers they're all gone, along with all the time I put in.

[Bill Cunningham]

"Paul" <nos...@needed.com> wrote in message
news:moospg$dev$1...@dont-email.me...

You know I use ccleaner and puran's cleaner and have to remove registry
entries. I have never had a problem. Some times I wonder if removing hive
keys is too overrated. idk.

Bill

[Bill Cunningham]

<rada...@nospam.com> wrote in message
news:1e1vqapcofrhlbeus...@4ax.com...

I will tell you what you can do if you don't mind messing up your system
possibly. Do this at your own risk. Go to \windows\system32\dllcache and
rename the sfc*.* files. Go to \windows\system32 and remove the sfc*.*
files. You have disabled system file protection. I have a right to possibly
corrupt your OS if you want. Of course you can reset those dllcache sfc
files and you sfc protection will be back on.

Bill


Bill