diskeeper lite or xp defragmenter?

  • Thread starter Thread starter Ed Chait
  • Start date Start date
E

Ed Chait

Are there any advantages to using one or the other?

They look identical, but is one superior in any way?

thanks,

ed
 
Are there any advantages to using one or the other?

They look identical, but is one superior in any way?

thanks,

ed

Use DIRMS, then run Buzzsaw in your start-up folder. Lower memory
usage, less bloat, and more accurate defragging. DK Lite is misery-ware
:-).

--
+++++++++++++++++++++++++++++++
El Gee <><
Know Christ, Know Peace
No Christ, No Peace

Remove yourhat to reply
Home Page - www.mistergeek.com
Blog - mcwtlg.blogspot.com
+++++++++++++++++++++++++++++++
 

I use the command line. Once you have run it on all your partitions and
have started Buzzsaw, you rarely need to run DIRMS again.

Enlighten me. Page defrag is to only defrag you swap file, no?
Besides, if you have Eraser set, it will get rid of you swap file for
you when you shutdown (or boot up...not sure which). Hive issues?
NTRegOpt works great!

--
++++++++++++++++++++++++++++++++
El Gee <><
Know Christ, Know Peace
No Christ, No Peace

Remove yourhat to reply
Home Page - www.mistergeek.com
Blog - mcwtlg.blogspot.com
++++++++++++++++++++++++++++++++
 
El said:
I use the command line. Once you have run it on all your partitions and
have started Buzzsaw, you rarely need to run DIRMS again.

Enlighten me. Page defrag is to only defrag you swap file, no?
Besides, if you have Eraser set, it will get rid of you swap file for
you when you shutdown (or boot up...not sure which). Hive issues?
NTRegOpt works great!
* Eraser versus PageDefrag *
Eraser overwrites the contents of the paging (swap) file(s) with
garbage. The size and location of the paging file(s) are still
determined by the OS. PageDefrag attempts to ensure that the paging
file(s) is physically optimized on the disk.

* NTRegOpt versus PageDefrag *
PageDefrag defragments the paging file(s), the hives (only those in
use?), event log files, and hibernation files. PageDefrag affects the
placement ("shape") of the files, not their contents.
From NTRegOpt.txt
"The program works by recreating each registry hive "from scratch",
thus removing any slack space that may be left from previously
modified or deleted keys.

"Note that the program does NOT change the contents of the registry in
any way, nor does it physically defrag the registry files on the drive
(as the PageDefrag program from SysInternals does). The optimization
done by NTREGOPT is simply compacting the registry hives to the
minimum size possible."

My limited understanding -- NTRegOpt compresses slack space within the
file and creates a new copy (placement determined by the OS) while
PageDefrag copies the file to a new location (while overriding/tweaking
the OS). In other words, NTRegOpt rearranges the contents WITHIN the
file while PageDefrag reshapes the file (i.e., the container) but does
not affect the contents. As such, they appear to be complementary.

* Analogy *
My rather inexact analogy is to a recipe box full of individual
notecards. Over time the recipe box becomes rather messy. You may
annotate a recipe or even "x" it out (but not actually discard it).
Many of us also just rip a recipe out of a magazine and stick it in the
box without pasting/copying it to a card. As the number of recipes
grows, you may need a second or even a third box to hold them.

PageDefrag is somewhat analogous to substituting a single, larger box
for a few smaller ones. The stack of recipes is still messy but at
least they are in one box.

In contrast, NTRegOpt copies all the recipes, cleaning up the
annotations and magazine fragments and also discarding the "x-ed"
recipes. This results in a smaller, neater stack of cards. The stack
is placed in a _new_ box that may -- or may not -- be large enough to
hold all of them without overflowing to more boxes (file fragments).

* Speculation *
On a system that has plenty of contiguous (defragmented) free space,
NTRegOpt may both compress and also effectively defragment the hives
since a new copy is created. I would not count on the latter on a
nearly full, highly fragmented drive.

Perhaps someone with more detailed knowledge will chime in. This is
not an area where I have delved deeply. I don't have detailed
knowledge of the Win2k/XP algorithyms, much less those of NTRegOpt and
PageDefrag.

BillR
 
Power Defragmenter is based on Sysinternals defragmentation "engine".
Basically its just a very advanced GUI for the Sysinternals core
application which takes defragmentation process to a whole new level.
Very high defragmentation speed, efficiency and ease of use. Such high
speed is only available with Sysinternals defragmentation "engine".
Thanks again to Sysinternals Mark Russinovich and Bryce Cogswell.

Version 1.8 and later features new PowerMode which provides even higher
defragmentation rate. Power Defragmenter is a stand-alone application
(extract & use) which works only in Windows 2000/XP.

http://www.excessive-software.tk/

http://www.softpedia.com/get/System/Hard-Disk-Utils/Power-Defragmenter.shtml
 
Mel said:
Power Defragmenter is based on Sysinternals defragmentation "engine".
Basically its just a very advanced GUI for the Sysinternals core
application which takes defragmentation process to a whole new level.
Very high defragmentation speed, efficiency and ease of use. Such high
speed is only available with Sysinternals defragmentation "engine".
Thanks again to Sysinternals Mark Russinovich and Bryce Cogswell.

Version 1.8 and later features new PowerMode which provides even higher
defragmentation rate. Power Defragmenter is a stand-alone application
(extract & use) which works only in Windows 2000/XP.

http://www.excessive-software.tk/

This site has a couple of other interesting items.http://www.softpedia.com/get/System/Hard-Disk-Utils/Power-Defragmenter.shtml
 
Back
Top