I would suggest that you add another drive to your system and offload some of the stuff off your C: drive. Then if you still feel compelled to defrag, it shouldn't be a problem. In my opinion, all desktop users should have 'at least' two hard drives.
100M of TIF space is plenty and some folk have a good bit less than that. It all depends how often you go back to webpages.
If it is too small then you will have to wait until webpages build (not long with broadband and so forth). If it is too large then it will take longer to find webpages already on the machine than it would be going straight to them online.
The 15% free space requirement was only for the antiquated manual/scheduled defragmenters. Apart from wasting time and using too many system resources to defrag, these older defraggers also demanded a lot of disk space in order to work properly. The XP defragger is one such example.
In contrast, the latest automatic defraggers use barely any resources and defrag in the background in real-time. Depending on the fragmented file size and actual disk space, auto defraggers can function properly even with less than 4 to 5% free disk space. Very effective in tackling fragmentation, and highly efficient at the same time. Google 'fully automatic defragmenter' for more info to get downloadable trial versions.
Defragmenting a drive is quite a nice thing to do. Having said that is has limited effect and certainly has no bearing on the free space available afterwards.
If you need more HD then you have to go and get it (or clear out the applications and data that you don't need).
I am with jefro. The reason is that defrag uses this space as a sorting area for file fragments. If your HD has less than fifteen percent free space, defrag will only partially defragments it.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE