Intro Download and install Frequently Asked Questions Tips and tricks

Homepage







© J.C. Kessels 2009
MyDefrag Forum
May 24, 2013, 06:56:48 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: 1 [2]
  Print  
Author Topic: best option for "messy" systems  (Read 1738 times)
technotika
JkDefrag Supporter
***
Posts: 11


View Profile
« Reply #15 on: April 21, 2011, 09:54:01 pm »

 Wink Hey thanks!!  - This is a great piece of kit - I really like it (figures since JKD was my top used cmdline fragger!!!) - after a lot of mistakes I finally got "everything working" including PSEXEC utilization as well. Until I saw the debug log saying no "setting.myd", then the penny dropped, I think it was making the transition between jkdefrag cmdlne and mydefrag (with scripts & some commandline).
Just a couple more things and then I'm really done I swear!  Kiss
So my logs are "C:\Temp\!COMPUTERNAME!.txt", I feel even more identity could be applied since a second visit machine would overwrite the previous log...
I thought "C:\Temp\!COMPUTERNAME!-!DATE!-!TIME!.txt" might work but it broke the log system...is it possible to add extra variables to the log naming convention or just the one?

gonna donate right now, thanks for all this help.......
Logged
Darlis
JkDefrag Hero
*****
Posts: 1707


View Profile WWW
« Reply #16 on: April 22, 2011, 06:01:44 am »

Unfortunately there is currently no way to create a unique name for a logfile except for "DATE" and maybe "ProcessID": Variables.
But MyDefrag also has Macro support which you can use to name the logfile with a name generated outside MyDefrag: Macros
« Last Edit: April 22, 2011, 06:08:04 am by Darlis » Logged

Need help creating a script? Try MyDefrag Script Creator.
Pages: 1 [2]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.5 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!