Archived from groups: microsoft.public.windowsxp.perform_maintain (
More info?)
Hi,
the prefetcher doesn't look on size or if a file is volatile. The best
is
to disable the build in defraggers capabilities of boot optimization
by turning
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction\Enable
to N.
Than you should try mst Defrag (http://www.mstsoftware.com). It's very
fast and it consumes only small memory.
After installing set the key MoveModifiedFilesToEnd (see FAQ) to 2.
Now you'll have always a quick boot and fast data access.
If you like you can read a test on Kickstart News:
http://www.kickstartnews.com/reviews/utilities/mst_defrag_workstation.html
Bye
Rob
davexnet02 <davexnetzerotwo@hooya!.com> wrote in message news:<96koo05vbicgg5stjbko5evasjmm5b5e4t@4ax.com>...
> On Fri, 5 Nov 2004 22:13:57 -0700, "Wesley Vogel"
> <123WVogel955@comcast.net> wrote:
>
> >Why wait three boots, find out now...
> >
> >Start | Run | Paste:
> >
> >Rundll32.exe advapi32.dll,ProcessIdleTasks
> >
> >Click OK
> >
> >DFRGNTFS.EXE & DEFRAG.EXE will run. Assuming your disk is formatted NTFS.
> Hi Wes,
> well the fat32 defrag ran for about 15 minutes, I've got to believe
> that those big multimedia files are a part of it.
> How to know for sure?
>
> Why would these big files be included here?
> They're volatile, temporary, could be changed or deleted
> at anytime. Including 300MB files in the prefetch mechanism
> makes no sense.
> Any way to exclude certain directories? Any other options?\
>
> Or am I misunderstanding something here?
>
> Thanks,
> Dave