Contrary to the Microsoft Knowledgebase article, my encounter with this problem was caused by an overloaded Temp directory on the user’s computer. See How to clear the temp directory.
Monthly Archive for August, 2008
This is such a simple thing that nobody would ever consider writing a blog entry or howto about it, right? The thing is though, I frequently see IT support technicians using Windows Explorer, clicking through into the user’s temp folder, highlighting everything and attempting to delete. They are interrupted (and the process aborted) by a message stating that a particular file was in use and could not be deleted, so they de-select that one file, and try again. Some more files are deleted but once again they are interrupted and told that another file couldn’t be deleted. They de-select that file and try again. This can go on for ages..
Here’s how to do it properly.
Go to a command prompt (Start -> Run -> cmd [enter])
At the command prompt type:
cd %tmp%
and press enter. This will change you into the current user’s temp directory.
Then type:
rd /s .
(that’s rd space slash-S space dot)
then press enter. Don’t forget the . at the end. This means “remove the current directory and all subdirectories, including all files.”
What will happen is that the contents of the temp directory and all subdirectories will be removed, but not the temp directory itself, because you are currently working in that directory (via the CD command) and therefore it can’t be deleted.
You’ll receive access denied messages for all in-use files, plus the temp directory itself. That’s fine. Those access denied messages would have been showstoppers if you were using Windows Explorer.
The above is clearing out the current user’s temp directory, which is located within that user’s profile directory (Documents and Settings\username). To clear out the system temp directory, which is located under the Windows directory, type:
cd %windir%\temp
and press enter. This will change you into the Windows temp directory.
Then just like before, type:
rd /s .
All done! You can type “exit” to close the command prompt.
I was ripping/encoding some DVDs with Handbrake/GTK, when the CPU temperature monitoring applet started complaining that it couldn’t read the temperature of core 1. I looked at the array of temperature readings on the top panel, and all four cores were between 97 - 100˚C. That’s not good.
dmesg showed
kernel: CPU0: Temperature above threshold, cpu clock throttled (total events = 270544)
(which explains why things started to get real slow while Handbrake was still ripping/encoding)
I didn’t believe it and suspected lm-sensors or whatever monitors the sensors was going screwy, so I took off the computer’s side panel and touched the side of the CPU heatsink. I discovered the computer was telling the truth (it was very hot!).
I had an idea where I wanted to look first…
This is the Intel supplied heatsink. I always buy retail boxed CPUs for the 3x warranty and fans that are built to last. For a short while, some time around the Athlon XP 3000+, AMD were supplying a heatsink with very fine fins which had a tendancy to block up like this. Toshiba laptops are famous for it too.
If you leave your computer running 24/7, and you don’t have some means of monitoring CPU temperature and fan speeds, I suggest you find something. I used to use something called MBM5 on Windows. Gnome has sensors-applet (see screenshot) below.


Recent Comments