the more i think about this idea, the more i like it.  here is one more thought:

currently, the default statusbar content ("text to show on statusbar on launch") will be replaced by:
1) typing (eg. "found x results in y seconds")
2) selecting a new item from the list (eg. "C:\WINDOWS\explorer.exe")
3) stopping a search (eg. "search stopped after finding x results in y seconds")
4) etc.

it would be great to have an option to disable these updates so that the default statusbar content would persist even if one of these events is triggered.

Especially now that FARR forces the presence of the statusbar, I would really like to be able to modify the option:
  "text to show on statusbar on launch"
with something more useful (specifically the time and the date).  are there currently any variable strings i can insert to accomplish this?  if not, would you consider adding these variables:

%a - Abbreviated weekday name
%A - Full weekday name
%b - Abbreviated month name
%B - Full month name
%d - Day of month as decimal number (01 - 31)
%H - Hour in 24-hour format (00 - 23)
%I - Hour in 12-hour format (01 - 12)
%m - Month as decimal number (01 - 12)
%M - Minute as decimal number (00 - 59)
%p - Current locale's A.M./P.M. indicator for 12-hour clock
%S - Second as decimal number (00 - 59)
%y - Year without century, as decimal number (00 - 99)
%Y - Year with century, as decimal number
%C - center text in the statusbar
%% - Percent sign

for example, if i wanted the statusbar to read:
Wednesday, August 21 - 3:11 pm
and have it centered in the statusbar, i would insert:
%A, %B %d - %I:%M %p%C

other useful variables could eventually be added later by users request (like uptime, cpu load, memory usage, etc.)

thanks for the continued work on FARR! it's working great!

-cracksloth

How about commandline options to allow running moveOut using the windows task scheduler and quit cleanly after that, or send email/log if errors occur?

i think this is a brilliant idea!  i also prefer to keep running processes down to a minimum especially since i already have the overhead of windows scheduler running at all times which should do the job nicely.

also, i am experiencing a bug.  when i click "browse" to specify a source/target, i am only presented with a dialog box saying "press ok to continue".  i'm running the compiled script because i do not have ahk installed atm.  any ideas on this?  has anyone else experienced this problem?  i am running a spanky fresh copy of xp sp2 so it seems unlikely that i am experiencing a conflict with another program.