Jeroen:

Thanks.

==================
WhenFinished(exit) - Understand
==================
Will this then look at the C drive only (not E and F) and not look at network drives?

VolumeSelect
  CommandlineVolumes()   ---   Is this needed?
  and Name("C:")
  and Removable(no)
VolumeActions

Can I just use this?

VolumeSelect
  Name("C:")
  and Removable(no)
VolumeActions
==================
OtherInstances - Understand
==================
Since the log is cleared each time MyDefrag is run, is the latest data always shown for both the "SlowOptimize.MyD" and the "FastUpdate.MyD", or when a script runs the log reflects only the latest data for that script?

If only the latest, I'm guessing that is when I would use the different log file names.
==================

I'm using the scheduler to run the supplied scripts "SlowOptimize.MyD" monthly and "FastUpdate.MyD" daily based on the recommendations I found in the forum and in help. I know the "FastUpdate.MyD" will close when done while the "SlowOptimize.MyD" will not. I also want the "SlowOptimize.MyD" to close when it is done running.

In looking at the script, is it as simple as adding "WhenFinished(exit)" below the "RunScript('Settings')" in the "SlowOptimize.MyD" file similar to the "FastUpdate.MyD" file?

====================================

On my computer I have my C: drive, a second hard drive (E:) and an external drive (Z: - connected via USB). The second and external drives are simply for backup and do not need to have MyDefrag run on them.  The only time they will be used is when I have data loss and need to recover data. For both the "SlowOptimize.MyD" monthly and "FastUpdate.MyD" scripts, they have the following volume commands. How would I turn off running MyDefrag against the E:(internal) and Z:(external) drives so it only runs on the C: drive?

VolumeSelect
  CommandlineVolumes()
  and Removable(no)
  and Writable(yes)
  and Mounted(yes)
VolumeActions

====================================

I'm assuming MyDefrag does not run against network drives unless it is turned on. If I'm incorrect, how would I turn those off as I do not want it to run against network drives?

====================================

I had one last question.  In looking at the MyDefrag.log file for "SlowOptimize.MyD", I see information for my E: and Z: drive, but not for my C drive. However, I had scheduled the "FastUpdate.MyD" to run at 3:00 AM this morning thinking the "SlowOptimize.MyD" would be done that I had started at 6:30 PM yesterday. I missed that it would run against the E: and Z : drives.

The "FastUpdate.MyD" ran while the "SlowOptimize.MyD" was still running and the log file names are the same for "FastUpdate.MyD" and "SlowOptimize.MyD". Would that be the reason for not seeing the C: data in the log file (see attached)?

I'm guessing I can change these in the script files to be different names and also to replace each log file. Each time the scripts run, the old log file data will be replaced. For example, would these be correct so each time the scripts run, the log files are replaced?

Change "FastUpdate.MyD" from  --  AppendLogfile("MyDefrag.log","  --  to WriteLogfile("FastUpdate.log","

Change "SlowOptimize.MyD" from  --  AppendLogfile("MyDefrag.log","  --  to WriteLogfile("SlowOptimze.log","

====================================

Thanks

Shawn

Jeroen:

Thank you very much.  I had always planned to run JKDefrag with the defaults until I came across this topic. I really don't know how much benefit I will gain following your suggested steps. For example, will my time decrease dramatically (e.g., 2 minutes to 30 seconds) to do a certain task, then it may be worth it.  That is what I was trying to find out - the benefit of running JKDefrag with options (and what options to use). I just don't know what the results will be.

My PST file has grown from 8GB to 9GB in the last year and will probably be close to 10GB by year end. If I followed the three steps and ran it today and then the defaults daily, I'm assuming I would have to do the three step approach again as new data will be added to the PST file (I'm assuming different parts of the disk). Its a matter of knowing how often and when to complete these steps for it to have any benefit (if any benefit)

I just don't have the knowledge to know the benefit (now and in the future) of moving the PST file to the front.

It sounds like for my use just go with the defaults and not worry about it. Correct?

Thank you.

Thank you very much for all your help.

I have removed the "-a 3" from both commands and "-u" from the second command as these are the defaults and are not needed. The SpaceHogs will be moved to the back and the drive will be defragged and optimized by default.

What I'm not sure about is the PST file and if it moves to the front.  The size of my hard drive is 300 GB, I have about 200 GB free and my PST file is 9 GB. The PST file is accessed (read and written to) all day. I can try the -a 6 option but I'm just trying to understand the benefit of running both commands. I thought by using the "-f 0" option this moves the PST file to Zone 1 to help in accessing the file. If I just run Step #1 below without the "-f 0" is that any better? Or do I just run the command line version as is without any options ("-f 0" "-e").

Step #1: -f 0 "C:\SRMDATAPST\Work.pst" c: e: z:
Step #2: -e "C:\SRMDATAPST\Work.pst" c: e: z:

Shawn

Thanks for your time and help.  I will remove the "-a 7" option. I read through the home page, help and FAQ's and had a few questions.

I created these two tasks:

Task #1: -f 0 -u DisableDefaults "C:\SRMDATAPST\Work.pst" -a 3 c: e: z:
Task #2: -e "C:\SRMDATAPST\Work.pst" -u -a 3 c: e: z:

Do I need the "-a 3" on Task #1 as this is also in Task #2?

For Task #1, I understand the "-f" controls the spaces between zones. Is there any benefit by adding this on Task #1 with moving my PST file to Zone 1 (based on other entries that I read on how to do this)? I could be misunderstanding the use of the "-f" option.

Sorry for the confusion on the "-u" question. My question was by default if the "-u" option is not included in the command line, will the internal list of SpaceHog files still be move to the end? I think they are. By using the "-u" option, this allows me to add extensions, files, folders, etc. or disable the option.

Shawn

Forgot to note that I entered the full path and file name of the PST file

-f 0 -u DisableDefaults "C:\SRMDATAPST\Work.pst" a -7 c: e: z:
-e "C:\SRMDATAPST\Work.pst" - u a -7 c: e: z:

Thanks

Shawn

I'm new to JKDefrag and was hoping for some guidance on the same issue.  I work with very large files on a daily basis and in fact my PST file is over 8 GB. I will use the suggested options across two scheduled tasks.

-f 0 -u DisableDefaults *.pst
-e *.pst

By default, is the "- u" option on? So for example if I don't use the - u option what happens to the large files over 50 MB? The only big file I want to move to the beginning is the PST file.  Other large files can be move to the end of the hard disk. If I add the "- u" option does it include all files greater than 50 MB even if they are not on the pre-defined list?  I'm just trying to understand the use of the "- u" option in that does it exclude or include the big files?

I have run JKDefrag using the "a -7" option. Should I run this on a daily basis or just use the "a -3" option (per the notes)? I will run JKDefrag at night, so for example below is what I think want to use across two scheduled tasks.

-f 0 -u DisableDefaults "C:\SRMDATAPST" a -7 c: e: z:
This will move my PST file to the front, sort by name / optimize on my c:, e:, and z: drives.  Not sure what the -f option does.

-e "C:\SRMDATAPST" - u a -7 c: e: z:
This will leave my PST file as is, sort by name / optimize, and move all other files large than 50 MB to the back on my c:, e:, and z: drives.

Any guidance would be greatly appreciated if what I'm noting is correct.

Thanks

Shawn