Task Scheduler question........ [Windows XP]

Prev: What is locking the partition
Next: installing xp brings a blue screen

From: J Tinsby on 3 Mar 2010 21:44

Hi Jose,

Well I found that darned log file that Auslogics makes! So that's out
of the way, now I can check it two ways to see if it ran.

I cannot get ST to 'wake up' the machine from an S-3 standby condition
to run the defrag. I doubt it ever will.

I was hoping that using the Auslogics scheduler I could set it to run
at lets' say 7:00am....with the machine shut off.. then I start the
machine at 9:00am and Auslogics sees that it didn't run and runs the
program that should have run at 7 but it doesn't seem to do that
either.

The darned thing is so close to being right it's really frustrating. I
notice that when I change settings in Auslogic it creates a new ST to
match what's been changed in Auslogics.

Do you think that Auslogics settings are dependent on the ST being
there? They make no mention of it in any help file. and I wonder too
if the drive is only fragemented a tiny amount is the program smart
enough to see it and NOT run?

Initially the Auslogics program used the NT AUTHORITY\SYSTEM as the
default and it ran once on it's own that way for me. But only once, I
can't figure that one out. How was anyone to know to use a password or
make a new identity so you can schedule a task? How lame is that?

I normally would just run the darned program manually, but years ago I
used Diskeeper and it ran as needed, you just set it and forgot about
it until you saw the icon in the tooltray showing it was active. I
reallly liked that program but it wasn't nearly as fast as Auslogics.

Again many thanks,

J Tinsby

On Wed, 3 Mar 2010 09:53:33 -0800 (PST), Jose <jose_ease(a)yahoo.com>
wrote:

>On Mar 3, 11:21 am, J Tinsby <n...(a)present.com> wrote:
>> Hello Jose,
>>
>> I am still fighting with this darn thing but I won't give up :)
>>
>> I can get the ST to run the defrag but it runs it a DOS window that I
>> can see. It doesn't run as if you had clicked on the .exe icon to get
>> it started.
>>
>> Furthermore I do not have a folder like the one you describe that has
>> the Auslogic log file in it. I had one of them that dated back to
>> 2/8/2010 but now I can't even find that, using the path you mentioned.
>>
>> If I look at the schedlLgu.txt I can see where the program ran and
>> shut down successfully. That was done by making a password for my own
>> name and deleting the extra account I had created. I am using the
>> command line that was put in the box by Auslogics
>>
>> "C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" C: D:
>> -bk
>>
>> I will try to put the NT AUTHORITY\SYSTEM back in and see if it will
>> run that way.
>>
>> I surely don't have all the nice log information you posted:
>
>
>You almost have it...
>
>I download and installed yesterday version 3.1.2.90 and did not have
>an old version installed.
>
>I clicked on Settings, Program Settings, Schedule to set up my ST. I
>said every Friday for my H drive, but it doesn't matter - I should
>still be able to run the task anytime I want.
>
>There is a check box so create a report (or not) and a link to browse
>the reports folder. I checked the box for the task it needs to
>create.
>
>The ST was created in the Tasks folder. The Task Properties Run lines
>looks like this:
>
>"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk -
>Log:"C:\Documents and Settings\Jose\Application Data\Auslogics\Disk
>Defrag\Logs\"
>
>Then I told Auslogics not to create a report and the Run line looks
>like this:
>
>"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk
>
>You are missing the -Log stuff...
>
>If yours does not have the -Log stuff, check your Auslogics settings
>and check the box to create a report, then check your Task Properties
>again. If it is not right, just delete the task from Auslogics and
>start over until it is right - don't try to figure out what is wrong
>with the ST Properties and fix it - you shouldn't have to do that.
>
>If you run the task with your login credentials and the -Log option,
>you will see the box - that is good for testing to make sure
>everything works. Then check the log through Auslogics, or just
>browse to your user folder. When you are finished testing, put the NT
>AUTHORITY\SYSTEM back and test again.
>
>You should not see a box, but will get a new log.
>
>Then the Task will run behind the scenes (no box) and not pop up some
>box one day when you don't expect it. It will still create the log
>file so you can check on it.

From: Jose on 4 Mar 2010 07:52

On Mar 3, 9:44 pm, J Tinsby <n...(a)present.com> wrote:
> Hi Jose,
>
> Well I found that darned log file that Auslogics makes! So that's out
> of the way, now I can check it two ways to see if it ran.
>
> I cannot get ST to 'wake up' the machine from an S-3 standby condition
> to run the defrag. I doubt it ever will.
>
> I was hoping that using the Auslogics scheduler I could set it to run
> at lets' say 7:00am....with the machine shut off.. then I start the
> machine at 9:00am and Auslogics sees that it didn't run and runs the
> program that should have run at 7 but it doesn't seem to do that
> either.
>
> The darned thing is so close to being right it's really frustrating. I
> notice that when I change settings in Auslogic it creates a new ST to
> match what's been changed in Auslogics.
>
> Do you think that Auslogics settings are dependent on the ST being
> there? They make no mention of it in any help file. and I wonder too
> if the drive is only fragemented a tiny amount is the program smart
> enough to see it and NOT run?
>
> Initially the Auslogics program used the NT AUTHORITY\SYSTEM as the
> default and it ran once on it's own that way for me. But only once, I
> can't figure that one out. How was anyone to know to use a password or
> make a new identity so you can schedule a task? How lame is that?
>
> I normally would just run the darned program manually, but years ago I
> used Diskeeper and it ran as needed, you just set it and forgot about
> it until you saw the icon in the tooltray showing it was active. I
> reallly liked that program but it wasn't nearly as fast as Auslogics.
>
> Again many thanks,
>
> J Tinsby
>
> On Wed, 3 Mar 2010 09:53:33 -0800 (PST), Jose <jose_e...(a)yahoo.com>
> wrote:
>
>
>
> >On Mar 3, 11:21 am, J Tinsby <n...(a)present.com> wrote:
> >> Hello Jose,
>
> >> I am still fighting with this darn thing but I won't give up :)
>
> >> I can get the ST to run the defrag but it runs it a DOS window that I
> >> can see. It doesn't run as if you had clicked on the .exe icon to get
> >> it started.
>
> >> Furthermore I do not have a folder like the one you describe that has
> >> the Auslogic log file in it. I had one of them that dated back to
> >> 2/8/2010 but now I can't even find that, using the path you mentioned.
>
> >> If I look at the schedlLgu.txt I can see where the program ran and
> >> shut down successfully. That was done by making a password for my own
> >> name and deleting the extra account I had created. I am using the
> >> command line that was put in the box by Auslogics
>
> >> "C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" C: D:
> >> -bk
>
> >> I will try to put the NT AUTHORITY\SYSTEM back in and see if it will
> >> run that way.
>
> >> I surely don't have all the nice log information you posted:
>
> >You almost have it...
>
> >I download and installed yesterday version 3.1.2.90 and did not have
> >an old version installed.
>
> >I clicked on Settings, Program Settings, Schedule to set up my ST. I
> >said every Friday for my H drive, but it doesn't matter - I should
> >still be able to run the task anytime I want.
>
> >There is a check box so create a report (or not) and a link to browse
> >the reports folder. I checked the box for the task it needs to
> >create.
>
> >The ST was created in the Tasks folder. The Task Properties Run lines
> >looks like this:
>
> >"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk -
> >Log:"C:\Documents and Settings\Jose\Application Data\Auslogics\Disk
> >Defrag\Logs\"
>
> >Then I told Auslogics not to create a report and the Run line looks
> >like this:
>
> >"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk
>
> >You are missing the -Log stuff...
>
> >If yours does not have the -Log stuff, check your Auslogics settings
> >and check the box to create a report, then check your Task Properties
> >again. If it is not right, just delete the task from Auslogics and
> >start over until it is right - don't try to figure out what is wrong
> >with the ST Properties and fix it - you shouldn't have to do that.
>
> >If you run the task with your login credentials and the -Log option,
> >you will see the box - that is good for testing to make sure
> >everything works. Then check the log through Auslogics, or just
> >browse to your user folder. When you are finished testing, put the NT
> >AUTHORITY\SYSTEM back and test again.
>
> >You should not see a box, but will get a new log.
>
> >Then the Task will run behind the scenes (no box) and not pop up some
> >box one day when you don't expect it. It will still create the log
> >file so you can check on it.

I don't see an option in Auslogics to wake the system to run the task,
but you can adjust the Task Properties to wake the computer to run
this task on the task settings tab. I just tried it. My system will
not wake from Hibernate to run a task but a scheduled task will wake
my computer from Stand By if I check the box to do so. Works every
time!

I am a hibernator, not a stand byer...

The system wakes up, runs the task behind the scenes (as NT
AUTHORITY), creates the log, logs the event in the ST log, etc. If I
change the Properties to my user login, I can see it running after it
wakes up.

Just let Auslogics create the task and tweak it using the ST
Properties so you just have one task that does what you want. Firing
up their GUI is too much trouble for simple adjustments once the ST
command is set up properly.

Even on a drive with zero fragmentation (according to Auslogics), the
Auslogics log is still there showing it tried and the XP task log
shows the task started and stopped. I have not read the reasons
Auslogics might look and decide not to run, but there would still
always be an event in the ST log file for Windows that the task at
least started and ended.

I don't know of a way for any Windows ST to check and see "I should
have run this task at 7 and it is now 9, therefore I am going to run
this task now". If Auslogics is not running, it will not be checking
anything and doesn't know if it needs to run or not. Don't mix up
what Auslogics does and what XP does for a task. It is just a task.
If the task starts another program, then the program decides what to
do or what not to do - not XP. XP just starts it when it is time.

I would get it working from NT AUTHORITY and leave it there and switch
to your user credentials for testing and adjustments. Maybe Auslogics
can put an icon in the Taskbar when it is running behind the scenes -
check their support page or email them with your good ideas.

Sometimes when things are working as designed, they are not working as
desired.

From: J Tinsby on 4 Mar 2010 10:49

Jose,

I sent an email to Auslogics and am awaiting a reponse from them
concerning the things I asked you about. I will post them here within
the next few days so you can see what they said.

Regards and thanks as always,

J T

On Thu, 4 Mar 2010 04:52:12 -0800 (PST), Jose <jose_ease(a)yahoo.com>
wrote:

>On Mar 3, 9:44 pm, J Tinsby <n...(a)present.com> wrote:
>> Hi Jose,
>>
>> Well I found that darned log file that Auslogics makes! So that's out
>> of the way, now I can check it two ways to see if it ran.
>>
>> I cannot get ST to 'wake up' the machine from an S-3 standby condition
>> to run the defrag. I doubt it ever will.
>>
>> I was hoping that using the Auslogics scheduler I could set it to run
>> at lets' say 7:00am....with the machine shut off.. then I start the
>> machine at 9:00am and Auslogics sees that it didn't run and runs the
>> program that should have run at 7 but it doesn't seem to do that
>> either.
>>
>> The darned thing is so close to being right it's really frustrating. I
>> notice that when I change settings in Auslogic it creates a new ST to
>> match what's been changed in Auslogics.
>>
>> Do you think that Auslogics settings are dependent on the ST being
>> there? They make no mention of it in any help file. and I wonder too
>> if the drive is only fragemented a tiny amount is the program smart
>> enough to see it and NOT run?
>>
>> Initially the Auslogics program used the NT AUTHORITY\SYSTEM as the
>> default and it ran once on it's own that way for me. But only once, I
>> can't figure that one out. How was anyone to know to use a password or
>> make a new identity so you can schedule a task? How lame is that?
>>
>> I normally would just run the darned program manually, but years ago I
>> used Diskeeper and it ran as needed, you just set it and forgot about
>> it until you saw the icon in the tooltray showing it was active. I
>> reallly liked that program but it wasn't nearly as fast as Auslogics.
>>
>> Again many thanks,
>>
>> J Tinsby
>>
>> On Wed, 3 Mar 2010 09:53:33 -0800 (PST), Jose <jose_e...(a)yahoo.com>
>> wrote:
>>
>>
>>
>> >On Mar 3, 11:21 am, J Tinsby <n...(a)present.com> wrote:
>> >> Hello Jose,
>>
>> >> I am still fighting with this darn thing but I won't give up :)
>>
>> >> I can get the ST to run the defrag but it runs it a DOS window that I
>> >> can see. It doesn't run as if you had clicked on the .exe icon to get
>> >> it started.
>>
>> >> Furthermore I do not have a folder like the one you describe that has
>> >> the Auslogic log file in it. I had one of them that dated back to
>> >> 2/8/2010 but now I can't even find that, using the path you mentioned.
>>
>> >> If I look at the schedlLgu.txt I can see where the program ran and
>> >> shut down successfully. That was done by making a password for my own
>> >> name and deleting the extra account I had created. I am using the
>> >> command line that was put in the box by Auslogics
>>
>> >> "C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" C: D:
>> >> -bk
>>
>> >> I will try to put the NT AUTHORITY\SYSTEM back in and see if it will
>> >> run that way.
>>
>> >> I surely don't have all the nice log information you posted:
>>
>> >You almost have it...
>>
>> >I download and installed yesterday version 3.1.2.90 and did not have
>> >an old version installed.
>>
>> >I clicked on Settings, Program Settings, Schedule to set up my ST. I
>> >said every Friday for my H drive, but it doesn't matter - I should
>> >still be able to run the task anytime I want.
>>
>> >There is a check box so create a report (or not) and a link to browse
>> >the reports folder. I checked the box for the task it needs to
>> >create.
>>
>> >The ST was created in the Tasks folder. The Task Properties Run lines
>> >looks like this:
>>
>> >"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk -
>> >Log:"C:\Documents and Settings\Jose\Application Data\Auslogics\Disk
>> >Defrag\Logs\"
>>
>> >Then I told Auslogics not to create a report and the Run line looks
>> >like this:
>>
>> >"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk
>>
>> >You are missing the -Log stuff...
>>
>> >If yours does not have the -Log stuff, check your Auslogics settings
>> >and check the box to create a report, then check your Task Properties
>> >again. If it is not right, just delete the task from Auslogics and
>> >start over until it is right - don't try to figure out what is wrong
>> >with the ST Properties and fix it - you shouldn't have to do that.
>>
>> >If you run the task with your login credentials and the -Log option,
>> >you will see the box - that is good for testing to make sure
>> >everything works. Then check the log through Auslogics, or just
>> >browse to your user folder. When you are finished testing, put the NT
>> >AUTHORITY\SYSTEM back and test again.
>>
>> >You should not see a box, but will get a new log.
>>
>> >Then the Task will run behind the scenes (no box) and not pop up some
>> >box one day when you don't expect it. It will still create the log
>> >file so you can check on it.
>
>I don't see an option in Auslogics to wake the system to run the task,
>but you can adjust the Task Properties to wake the computer to run
>this task on the task settings tab. I just tried it. My system will
>not wake from Hibernate to run a task but a scheduled task will wake
>my computer from Stand By if I check the box to do so. Works every
>time!
>
>I am a hibernator, not a stand byer...
>
>The system wakes up, runs the task behind the scenes (as NT
>AUTHORITY), creates the log, logs the event in the ST log, etc. If I
>change the Properties to my user login, I can see it running after it
>wakes up.
>
>Just let Auslogics create the task and tweak it using the ST
>Properties so you just have one task that does what you want. Firing
>up their GUI is too much trouble for simple adjustments once the ST
>command is set up properly.
>
>Even on a drive with zero fragmentation (according to Auslogics), the
>Auslogics log is still there showing it tried and the XP task log
>shows the task started and stopped. I have not read the reasons
>Auslogics might look and decide not to run, but there would still
>always be an event in the ST log file for Windows that the task at
>least started and ended.
>
>I don't know of a way for any Windows ST to check and see "I should
>have run this task at 7 and it is now 9, therefore I am going to run
>this task now". If Auslogics is not running, it will not be checking
>anything and doesn't know if it needs to run or not. Don't mix up
>what Auslogics does and what XP does for a task. It is just a task.
>If the task starts another program, then the program decides what to
>do or what not to do - not XP. XP just starts it when it is time.
>
>I would get it working from NT AUTHORITY and leave it there and switch
>to your user credentials for testing and adjustments. Maybe Auslogics
>can put an icon in the Taskbar when it is running behind the scenes -
>check their support page or email them with your good ideas.
>
>Sometimes when things are working as designed, they are not working as
>desired.

From: Jose on 5 Mar 2010 21:34

On Mar 4, 10:49 am, J Tinsby <n...(a)present.com> wrote:
> Jose,
>
> I sent an email to Auslogics and am awaiting a reponse from them
> concerning the things I asked you about. I will post them here within
> the next few days so you can see what they said.
>
> Regards and thanks as always,
>
> J T
>
> On Thu, 4 Mar 2010 04:52:12 -0800 (PST), Jose <jose_e...(a)yahoo.com>
> wrote:
>
>
>
> >On Mar 3, 9:44 pm, J Tinsby <n...(a)present.com> wrote:
> >> Hi Jose,
>
> >> Well I found that darned log file that Auslogics makes! So that's out
> >> of the way, now I can check it two ways to see if it ran.
>
> >> I cannot get ST to 'wake up' the machine from an S-3 standby condition
> >> to run the defrag. I doubt it ever will.
>
> >> I was hoping that using the Auslogics scheduler I could set it to run
> >> at lets' say 7:00am....with the machine shut off.. then I start the
> >> machine at 9:00am and Auslogics sees that it didn't run and runs the
> >> program that should have run at 7 but it doesn't seem to do that
> >> either.
>
> >> The darned thing is so close to being right it's really frustrating. I
> >> notice that when I change settings in Auslogic it creates a new ST to
> >> match what's been changed in Auslogics.
>
> >> Do you think that Auslogics settings are dependent on the ST being
> >> there? They make no mention of it in any help file. and I wonder too
> >> if the drive is only fragemented a tiny amount is the program smart
> >> enough to see it and NOT run?
>
> >> Initially the Auslogics program used theNTAUTHORITY\SYSTEM as the
> >> default and it ran once on it's own that way for me. But only once, I
> >> can't figure that one out. How was anyone to know to use a password or
> >> make a new identity so you can schedule a task? How lame is that?
>
> >> I normally would just run the darned program manually, but years ago I
> >> used Diskeeper and it ran as needed, you just set it and forgot about
> >> it until you saw the icon in the tooltray showing it was active. I
> >> reallly liked that program but it wasn't nearly as fast as Auslogics.
>
> >> Again many thanks,
>
> >> J Tinsby
>
> >> On Wed, 3 Mar 2010 09:53:33 -0800 (PST), Jose <jose_e...(a)yahoo.com>
> >> wrote:
>
> >> >On Mar 3, 11:21 am, J Tinsby <n...(a)present.com> wrote:
> >> >> Hello Jose,
>
> >> >> I am still fighting with this darn thing but I won't give up :)
>
> >> >> I can get the ST to run the defrag but it runs it a DOS window that I
> >> >> can see. It doesn't run as if you had clicked on the .exe icon to get
> >> >> it started.
>
> >> >> Furthermore I do not have a folder like the one you describe that has
> >> >> the Auslogic log file in it. I had one of them that dated back to
> >> >> 2/8/2010 but now I can't even find that, using the path you mentioned.
>
> >> >> If I look at the schedlLgu.txt I can see where the program ran and
> >> >> shut down successfully. That was done by making a password for my own
> >> >> name and deleting the extra account I had created. I am using the
> >> >> command line that was put in the box by Auslogics
>
> >> >> "C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" C: D:
> >> >> -bk
>
> >> >> I will try to put theNTAUTHORITY\SYSTEM back in and see if it will
> >> >> run that way.
>
> >> >> I surely don't have all the nice log information you posted:
>
> >> >You almost have it...
>
> >> >I download and installed yesterday version 3.1.2.90 and did not have
> >> >an old version installed.
>
> >> >I clicked on Settings, Program Settings, Schedule to set up my ST. I
> >> >said every Friday for my H drive, but it doesn't matter - I should
> >> >still be able to run the task anytime I want.
>
> >> >There is a check box so create a report (or not) and a link to browse
> >> >the reports folder. I checked the box for the task it needs to
> >> >create.
>
> >> >The ST was created in the Tasks folder. The Task Properties Run lines
> >> >looks like this:
>
> >> >"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk -
> >> >Log:"C:\Documents and Settings\Jose\Application Data\Auslogics\Disk
> >> >Defrag\Logs\"
>
> >> >Then I told Auslogics not to create a report and the Run line looks
> >> >like this:
>
> >> >"C:\Program Files\Auslogics\Auslogics Disk Defrag\cdefrag.exe" H: -bk
>
> >> >You are missing the -Log stuff...
>
> >> >If yours does not have the -Log stuff, check your Auslogics settings
> >> >and check the box to create a report, then check your Task Properties
> >> >again. If it is not right, just delete the task from Auslogics and
> >> >start over until it is right - don't try to figure out what is wrong
> >> >with the ST Properties and fix it - you shouldn't have to do that.
>
> >> >If you run the task with your login credentials and the -Log option,
> >> >you will see the box - that is good for testing to make sure
> >> >everything works. Then check the log through Auslogics, or just
> >> >browse to your user folder. When you are finished testing, put theNT
> >> >AUTHORITY\SYSTEM back and test again.
>
> >> >You should not see a box, but will get a new log.
>
> >> >Then the Task will run behind the scenes (no box) and not pop up some
> >> >box one day when you don't expect it. It will still create the log
> >> >file so you can check on it.
>
> >I don't see an option in Auslogics to wake the system to run the task,
> >but you can adjust the Task Properties to wake the computer to run
> >this task on the task settings tab. I just tried it. My system will
> >not wake from Hibernate to run a task but a scheduled task will wake
> >my computer from Stand By if I check the box to do so. Works every
> >time!
>
> >I am a hibernator, not a stand byer...
>
> >The system wakes up, runs the task behind the scenes (asNT
> >AUTHORITY), creates the log, logs the event in the ST log, etc. If I
> >change the Properties to my user login, I can see it running after it
> >wakes up.
>
> >Just let Auslogics create the task and tweak it using the ST
> >Properties so you just have one task that does what you want. Firing
> >up their GUI is too much trouble for simple adjustments once the ST
> >command is set up properly.
>
> >Even on a drive with zero fragmentation (according to Auslogics), the
> >Auslogics log is still there showing it tried and the XP task log
> >shows the task started and stopped. I have not read the reasons
> >Auslogics might look and decide not to run, but there would still
> >always be an event in the ST log file for Windows that the task at
> >least started and ended.
>
> >I don't know of a way for any Windows ST to check and see "I should
> >have run this task at 7 and it is now 9, therefore I am going to run
> >this task now". If Auslogics is not running, it will not be checking
> >anything and doesn't know if it needs to run or not. Don't mix up
> >what Auslogics does and what XP does for a task. It is just a task.
> >If the task starts another program, then the program decides what to
> >do or what not to do - not XP. XP just starts it when it is time.
>
> >I would get it working fromNTAUTHORITYand leave it there and switch
> >to your user credentials for testing and adjustments. Maybe Auslogics
> >can put an icon in the Taskbar when it is running behind the scenes -
> >check their support page or email them with your good ideas.
>
> >Sometimes when things are working as designed, they are not working as
> >desired.

That will be good. I will leave mine installed for a while and see
what they say.

I can see that I need to work on my ST troubleshooting words a bit
from my first offering! I can make it easier for the next person -
not just Auslogics, but just general ST troubleshooting.

From: Twayne on 6 Mar 2010 22:07

In news:46ef0e1c-0d21-42f2-b590-cbea2192cb30(a)19g2000yqu.googlegroups.com,
Jose <jose_ease(a)yahoo.com> typed:
> On Mar 4, 10:49 am, J Tinsby <n...(a)present.com> wrote:
>> Jose,
>>
>> I sent an email to Auslogics and am awaiting a reponse
>> from them concerning the things I asked you about. I will
>> post them here within the next few days so you can see
>> what they said.
>>
>> Regards and thanks as always,
>>
>> J T
>>
>> On Thu, 4 Mar 2010 04:52:12 -0800 (PST), Jose
>> <jose_e...(a)yahoo.com> wrote:
>>
>>
>>
>>> On Mar 3, 9:44 pm, J Tinsby <n...(a)present.com> wrote:
>>>> Hi Jose,
>>
>>>> Well I found that darned log file that Auslogics makes!
>>>> So that's out of the way, now I can check it two ways to
>>>> see if it ran.
>>
>>>> I cannot get ST to 'wake up' the machine from an S-3
>>>> standby condition to run the defrag. I doubt it ever
>>>> will.
>>
>>>> I was hoping that using the Auslogics scheduler I could
>>>> set it to run at lets' say 7:00am....with the machine
>>>> shut off.. then I start the machine at 9:00am and
>>>> Auslogics sees that it didn't run and runs the program
>>>> that should have run at 7 but it doesn't seem to do that
>>>> either.
>>
>>>> The darned thing is so close to being right it's really
>>>> frustrating. I notice that when I change settings in
>>>> Auslogic it creates a new ST to match what's been
>>>> changed in Auslogics.
>>
>>>> Do you think that Auslogics settings are dependent on
>>>> the ST being there? They make no mention of it in any
>>>> help file. and I wonder too if the drive is only
>>>> fragemented a tiny amount is the program smart enough to
>>>> see it and NOT run?
>>
>>>> Initially the Auslogics program used
>>>> theNTAUTHORITY\SYSTEM as the default and it ran once on
>>>> it's own that way for me. But only once, I can't figure
>>>> that one out. How was anyone to know to use a password
>>>> or make a new identity so you can schedule a task? How
>>>> lame is that?
>>
>>>> I normally would just run the darned program manually,
>>>> but years ago I used Diskeeper and it ran as needed, you
>>>> just set it and forgot about it until you saw the icon
>>>> in the tooltray showing it was active. I reallly liked
>>>> that program but it wasn't nearly as fast as Auslogics.
>>
>>>> Again many thanks,
>>
>>>> J Tinsby
>>
>>>> On Wed, 3 Mar 2010 09:53:33 -0800 (PST), Jose
>>>> <jose_e...(a)yahoo.com> wrote:
>>
>>>>> On Mar 3, 11:21 am, J Tinsby <n...(a)present.com> wrote:
>>>>>> Hello Jose,
>>
>>>>>> I am still fighting with this darn thing but I won't
>>>>>> give up :)
>>
>>>>>> I can get the ST to run the defrag but it runs it a
>>>>>> DOS window that I can see. It doesn't run as if you
>>>>>> had clicked on the .exe icon to get it started.
>>
>>>>>> Furthermore I do not have a folder like the one you
>>>>>> describe that has the Auslogic log file in it. I had
>>>>>> one of them that dated back to 2/8/2010 but now I
>>>>>> can't even find that, using the path you mentioned.
>>
>>>>>> If I look at the schedlLgu.txt I can see where the
>>>>>> program ran and shut down successfully. That was done
>>>>>> by making a password for my own name and deleting the
>>>>>> extra account I had created. I am using the command
>>>>>> line that was put in the box by Auslogics
>>
>>>>>> "C:\Program Files\Auslogics\Auslogics Disk
>>>>>> Defrag\cdefrag.exe" C: D: -bk
>>
>>>>>> I will try to put theNTAUTHORITY\SYSTEM back in and
>>>>>> see if it will run that way.
>>
>>>>>> I surely don't have all the nice log information you
>>>>>> posted:
>>
>>>>> You almost have it...
>>
>>>>> I download and installed yesterday version 3.1.2.90 and
>>>>> did not have an old version installed.
>>
>>>>> I clicked on Settings, Program Settings, Schedule to
>>>>> set up my ST. I said every Friday for my H drive, but
>>>>> it doesn't matter - I should still be able to run the
>>>>> task anytime I want.
>>
>>>>> There is a check box so create a report (or not) and a
>>>>> link to browse the reports folder. I checked the box
>>>>> for the task it needs to
>>>>> create.
>>
>>>>> The ST was created in the Tasks folder. The Task
>>>>> Properties Run lines looks like this:
>>
>>>>> "C:\Program Files\Auslogics\Auslogics Disk
>>>>> Defrag\cdefrag.exe" H: -bk - Log:"C:\Documents and
>>>>> Settings\Jose\Application Data\Auslogics\Disk
>>>>> Defrag\Logs\"
>>
>>>>> Then I told Auslogics not to create a report and the
>>>>> Run line looks like this:
>>
>>>>> "C:\Program Files\Auslogics\Auslogics Disk
>>>>> Defrag\cdefrag.exe" H: -bk
>>
>>>>> You are missing the -Log stuff...
>>
>>>>> If yours does not have the -Log stuff, check your
>>>>> Auslogics settings and check the box to create a
>>>>> report, then check your Task Properties again. If it is
>>>>> not right, just delete the task from Auslogics and
>>>>> start over until it is right - don't try to figure out
>>>>> what is wrong with the ST Properties and fix it - you
>>>>> shouldn't have to do that.
>>
>>>>> If you run the task with your login credentials and the
>>>>> -Log option, you will see the box - that is good for
>>>>> testing to make sure everything works. Then check the
>>>>> log through Auslogics, or just
>>>>> browse to your user folder. When you are finished
>>>>> testing, put theNT AUTHORITY\SYSTEM back and test again.
>>
>>>>> You should not see a box, but will get a new log.
>>
>>>>> Then the Task will run behind the scenes (no box) and
>>>>> not pop up some box one day when you don't expect it.
>>>>> It will still create the log file so you can check on
>>>>> it.
>>
>>> I don't see an option in Auslogics to wake the system to
>>> run the task, but you can adjust the Task Properties to
>>> wake the computer to run this task on the task settings
>>> tab. I just tried it. My system will not wake from
>>> Hibernate to run a task but a scheduled task will wake my
>>> computer from Stand By if I check the box to do so. Works
>>> every time!
>>
>>> I am a hibernator, not a stand byer...
>>
>>> The system wakes up, runs the task behind the scenes (asNT
>>> AUTHORITY), creates the log, logs the event in the ST
>>> log, etc. If I change the Properties to my user login, I
>>> can see it running after it wakes up.
>>
>>> Just let Auslogics create the task and tweak it using the
>>> ST Properties so you just have one task that does what
>>> you want. Firing up their GUI is too much trouble for
>>> simple adjustments once the ST command is set up properly.
>>
>>> Even on a drive with zero fragmentation (according to
>>> Auslogics), the Auslogics log is still there showing it
>>> tried and the XP task log shows the task started and
>>> stopped. I have not read the reasons Auslogics might look
>>> and decide not to run, but there would still always be an
>>> event in the ST log file for Windows that the task at
>>> least started and ended.
>>
>>> I don't know of a way for any Windows ST to check and see
>>> "I should have run this task at 7 and it is now 9,
>>> therefore I am going to run this task now". If Auslogics
>>> is not running, it will not be checking anything and
>>> doesn't know if it needs to run or not. Don't mix up what
>>> Auslogics does and what XP does for a task. It is just a
>>> task. If the task starts another program, then the
>>> program decides what to do or what not to do - not XP. XP
>>> just starts it when it is time.
>>
>>> I would get it working fromNTAUTHORITYand leave it there
>>> and switch to your user credentials for testing and
>>> adjustments. Maybe Auslogics can put an icon in the
>>> Taskbar when it is running behind the scenes - check
>>> their support page or email them with your good ideas.
>>
>>> Sometimes when things are working as designed, they are
>>> not working as desired.
>
> That will be good. I will leave mine installed for a while
> and see what they say.
>
> I can see that I need to work on my ST troubleshooting
> words a bit from my first offering! I can make it easier
> for the next person - not just Auslogics, but just general
> ST troubleshooting.

LOL! I think only one person in this thread knows how to post! Jeeeezz!

--
--
Life is the only real counselor; wisdom unfiltered
through personal experience does not become a
part of the moral tissue.

First | Prev | Next | Last
Pages: 1 2 3 4 5
Prev: What is locking the partition
Next: installing xp brings a blue screen