On Fri, 05 May 2006 05:35:04 GMT, "Cymbal Man Freq."
Looks like you need a much bigger drive. How about an 80 GB, or a 160 GB drive.
Give yourself a break.
Nope, because the cause of this may matter for other reasons...
"Krazy Katt" <
[email protected]> wrote in message
| I have this damn OS (Windows XP) installed on a 14 GB drive and it still
| manages to fill up my drive. I've turned off system restore, moved all the
| WIndows update restore files to another drive, and yet my free space will
| go from about 600M to almost 5 -- oh, I've moved my Documents and
| Settings to a new drive too, so I cant' for the life of me figure out what
| the hell keeps filling up my C-drive -- I hope MS gets their shit together
| with Vista, or we'll all end up having to reserve 40 GB just for the damn
| OS.
Actually, Vista will prolly need 32G or so for itself... when was the
last time a software vendor wrote *less* software?
I routinely run XP in 8G with 40% of that C: volume free, so let's
check out what may be happening here...
1) System Restore
By default, hogs a lot of space, but you've waxed that; OK.
2) Pagefile and hibernation storage
For a given task set, the more RAM you havem, the LESS page file you
need to swap to - but this is a concept MS can't grasp. According to
MS logic, if you want to aviod paging altogether, have zero RAM; after
all, with 128M RAM you magically need only 172M or so, right?
However, swapping to disk is not the only thing the pagefile is used
for, e.g. crash dumps of memory may be written to it.
The more RAM you have, the more disk XP will use for pagefile and will
need to store the RAM state if you hibernate the system. So if you
have a lot of RAM (512M+) it's up to you to kill hibernation and limit
pagefile; I generally use 512M pagefile irrespective of amount of RAM.
3) Web caches
Most browsers will be content with 20-50M, but not IE; that dumbo hogs
a ton of space for yesterday's web scraps. The logic escapes me; any
connection fast enough to populate a 100M web cache in a time short
enough for the contents to not go stale, is a connection that's fast
enough not to need caching to disk. I use 20M for IE's cache.
4) Per-account overhead
Each user account repeats the same per-user stores, including the
massive IE web cache mentioned in (3). In addition, disk space may be
used to preserve account context when switching between concurrent
users. For this and other reasons, I have only one user account, and
I kill off any "fast user switching" feature.
5) Windows update stores
The whole of SP2 may be around 220M, but it's easy to find you have 1G
of disk space wasted on patch material that is never actually used and
just clogs up the works - like carrying 5 tons of cement in the boot
of your car, wherever you go. The stores in %WinDir% are...
- $hf_mig$ (can be large)
- $NTUninstall*$ (not large, but one per patch)
- Downloaded Installations (may be big)
- Registered Packages (may be large)
- SoftwareDistribution (large and "difficult")
- ServicePackFiles (large, if present)
Don't pick a fight with Driver Cache, and you may find
SoftwareDistribution will not be moved either. I move (rt-click,
drag, click Move) the $*$ and ServicePackFiles off C: to another
available HD drive volume; the consequences may be difficulties with
uninstalling patches, or finding replacement files (from
ServicePackFiles, most likely) if XP wants to "heal" itself.
6) Temp files
Not just in your user profiles, but also %WinDir%\Temp and within the
Local Settings subtree of System32\Config\SystemProfile
7) CD Burning
This buffer is repeated per user account, and I kill it in two ways; I
rt-drag and Move it off C: to another HD volume, and I disable CD
writing in the Properties for the drive (using Nero instead).
8) Desktop
Users dump all manner of junk on the desktop, which is often the
duhfault Save location for web browsers, etc. Then XP will scrape
everything off to a single desktop icon, which the user will forget to
look in, and the same junk will be dumped there again. The desktop is
repeated per user account, as well as the AllUsers one; I rt-drag,
Move this off to a HD volume other than C:
9) The "My..." ghettos
Also repeated per user account. I run Movie Maker to create "My
Videos", then I rt-drag, Move My Vids / Pics / Music off C: to another
HD volume, then I do the same for what is left of My Docs.
Do this BEFORE you install or use any other sware, so that these will
derive their own settings based on the relocated paths you want - esle
you may have to chase after them via Options or Regedit.
10) Email stores
Outlook.pst is best moved off C: for a number of reasons, though it
can be tricky to do so; not using it is even better. OE's mail is
easy to relocate once you figure out to create the empty dir first,
point OE at it, and then exit and re-enter OE to effect the move.
Mail stores often become huge because folks don't empty the Trash and
don't compact the mailboxes.
11) Recycle Bin
Flush regularly. I use Shift+Del to delete directly.
12) Other stores
As above, including some that store things under themselves. Remember
the shared directories for p2p tools, workspaces for archivers and
download accelerators, and games that create massive saved states.
13) File system corruption
This can bleed away space, especially where a chunk of arbitrary data
is used as a "directory", with huge values for "size" hi-order bytes.
14) Hidden files
Set Explorer to show all hidden and system files, DUH
15) Very hidden files
NTFS allows stuff to be stored, and even "opened" as raw code, within
ADS (Alternate Data Streams) that cannot be visualized via the shell.
If you lose space and can't find it in any Select All, Properties,
etc. then you may have an entire malware FTP site running as ADS
attached to arbitrary files. Tools such as HiJackThis can scan for
ADS and help you manage the problem, or you can kill the whole issue
altogether by using FATxx instead of NTFS.
--------------- ----- ---- --- -- - - -
Error Messages Are Your Friends
