January 12th 10, 11:21 AM
posted to microsoft.public.win98.gen_discussion
|
|
|
Defrag problems
"MEB" wrote in message
...
On 01/08/2010 06:42 AM, Aster wrote:
"Bill Blanton" wrote in message
...
On 1/6/2010 05:47, Aster wrote:
Also, according to microsoft, the volume must have at least 15 percent
free space for Defrag to completely and adequately defragment it.
Defrag
uses this space as a sorting area for file fragments. If a volume has
less than 15 percent free space, Defrag only partially defragments it.
So, if my 20Gb hard drive has only 1.53Gb free space and I have
performed defrag, my volume has been just partially defragmented?
If you only have 1.5GB free it's either time to move some data off, or
buy another drive. If you're thinking that defrag is going to speed up
your system considerably, it won't. Far better to look at what
processes are running in the background.
It was mentioned that Scandisk reported bad clusters. In that case
stay away from any defrag utility. Defrag is for healthy disks.
---------------
still not clear, has been my volume fully defragged, or just some
partially? Canno check this, since there is no 'Analyze' disk option,
like win XP has.
Uhm, here's what I found in Win9X in similar situations:
1. *IF* I had *disabled virtual memory* and thereby deleted the swap
file upon re-boot before the scandisk/defrag, then yes, during the first
run, though it took even longer. This frees up MORE space, though it can
only be done on computers in which there is sufficient memory and
limited background apps.
The reason is to place the swap in contiguous blocks rather than
scattered around the disk, and the extra time comes from moving all
those files to fill in the now blanked/freed areas. The swap is then
placed at the end of the used file area when re-enabled.
The warning you refer to [15%] comes from the necessity to ensure there
IS available swap space/area sufficient to run "not only"
scandisk/defrag, but also for large and/or numerous applications being
run and being swapped, *particularly* if you have not disabled what you
can for the scandisk/defrag operations [hence why it is recommended to
limit these background applications during the activities].
A. *IF* you have lots of memory, then you can limit the swap to a small
area (or disable it) and *force* Windows to use physical memory instead.
2. *IF* leaving memory control in the hands of Windows during
scandisk/defrag, then expect it will constantly warn about disk changes,
at least until you tell it not to warn you again. Also note:
A. you haven't really defragmented the disk completely/thoroughly [due
to the non-contiguous swap areas];
1. this is fine for normal usage, however, it is good idea to do a
*thorough* scandisk and defrag on your disk(s) "every once in awhile"
[depending upon your usage and/or needs].
3. Remember, many application's files may expand during usage so the
defrag actually only lasts for a relatively short time period as these
are moved around the disk to free areas, leaving small previously
claimed "file" areas as freed, which may be filled in with smaller files
from other applications or otherwise (as in parts of files or similar)
starting the fragmentation process again.
4. *IF* installing and un-installing are part of your normal usage,
EXPECT the disk to be severely fragmented. The systems being used in
this fashion REQUIRE scandisk and defrag or other disk maintenance tools
be used more frequently.
--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Info, Diagnostics, Security, Networking
http://peoplescounsel.org
The "real world" of Law, Justice, and Government
---------------
How to disable virtual memory?
Aster
|