Task Scheduler question........

[J Tinsby]

Hello,



I have been trying, with little or no success, to get TS to run my

Auslogic defrag program once a week. Seems that no matter what I do it

won't start, BUT..... it did once as the log shows. After that at the

appointed time it never runs.



In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

Defrag\cdefrag.exe" C: D: -bk



The START IN box is blank



The exerpt from the log on the day it ran successfully is:

"Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

(cdefrag.exe)

Started 2/22/2010 10:00:12 AM

"Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

(cdefrag.exe)

Finished 2/22/2010 10:01:09 AM

Result: The task completed with an exit code of (0).



Note that I did not create the run line, it was put there when I

installed the Auslogic program.



I only need the program to run once a week, I have also tried having

it wake up the machine from S3 standby, or from totally OFF, but that

doesn't work either.



What can I do to make it work as it should? I am using XP Pro with SP3

and all updates installed.



Thank you very much for any help you might give me.



J Tinsby

 

[John John - MVP]

J Tinsby wrote:

> Hello,

>

> I have been trying, with little or no success, to get TS to run my

> Auslogic defrag program once a week. Seems that no matter what I do it

> won't start, BUT..... it did once as the log shows. After that at the

> appointed time it never runs.

>

> In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

> Defrag\cdefrag.exe" C: D: -bk

>

> The START IN box is blank

>

> The exerpt from the log on the day it ran successfully is:

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

> Started 2/22/2010 10:00:12 AM

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

> Finished 2/22/2010 10:01:09 AM

> Result: The task completed with an exit code of (0).

>

> Note that I did not create the run line, it was put there when I

> installed the Auslogic program.

>

> I only need the program to run once a week, I have also tried having

> it wake up the machine from S3 standby, or from totally OFF, but that

> doesn't work either.

>

> What can I do to make it work as it should? I am using XP Pro with SP3

> and all updates installed.

>

> Thank you very much for any help you might give me.



Is your account password protected? Scheduled Tasks wont run properly

if your account is not password protected.



John

 

[Jose]

On Mar 2, 11:25 am, J Tinsby wrote:

> Hello,

>

> I have been trying, with little or no success, to get TS to run my

> Auslogic defrag program once a week. Seems that no matter what I do it

> won't start, BUT..... it did once as the log shows. After that at the

> appointed time it never runs.

>

> In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

> Defrag\cdefrag.exe" C: D: -bk

>

> The START IN box is blank

>

> The exerpt from the log on the day it ran successfully is:

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

>         Started 2/22/2010 10:00:12 AM

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

>         Finished 2/22/2010 10:01:09 AM

>         Result: The task completed with an exit code of (0).

>

> Note that I did not create the run line, it was put there when I

> installed the Auslogic program.

>

> I only need the program to run once a week, I have also tried having

> it wake up the machine from S3 standby, or from totally OFF, but that

> doesn't work either.

>

> What can I do to make it work as it should? I am using XP Pro with SP3

> and all updates installed.

>

> Thank you very much for any help you might give me.

>

> J Tinsby



Let's make sure your Scheduled Tasks mechanism is sound first using a

simple test, then try to fix your Auslogics.



I have not used Auslogics in a while, and I may install it after you

complete these tests if you still have a problem.



Some applications you may want to schedule at a convenient time

require user intervention (answering questions via the keyboard).

Does your application have options to run unattended and is it

designed to run as an unattended scheduled task?



It is strongly suggested that the task be assigned to a user that has

a password (I would not use the Administrator account), so create a

new user with a password just for scheduled tasks or add a password to

your account if needed. You can temporarily assign yourself a PW to

test and worry about this later.



If your login does not use a password, you should assign a password to

your currently logged in account right now - at least temporarily for

the following tests. You can remove the password later if you want.



If you don't use an account with a password, you will get an error

trying to create the task. It will still be created, but will not run

properly.



There is a way around this, but get this working first to be sure your

mechanism is not afflicted.



Stop the Task Scheduler service.



Delete or rename the probably cluttered ST log file:



c:\windows\schedlgu.txt



Restart the Task Scheduler service to create a new log and take a look

at it with a text editor.



Browse to the folder where the STs are stored:



c:\windows\tasks



Here you will see all your STs and pay attention to the different

column headings that are particular to this folder.



The Next Run Time, Last Run Time, Status and Last Results columns are

of interest. You can also click Advanced and view the log.



Choose to Add Scheduled Task. Create a new task to run Command Prompt

once, now using the same login and password as the account you are

currently logged in. If you don't use a password, you will get an

error trying to create the ST (more on that later). The ST will be

created, but it will never run.



Right click the new Command Prompt task and choose Run and a command

window should open immediately. If not, something is wrong. If yes,

your mechanism is sound. Look in the log file to see your results.



You know how to remove the log now, so that is up to you. Be sure the

Task Scheduler service is running again and try to get your afflicted

task working.



Add or change your desired task Properties using the same credentials

(user and password) that was used when you created the task to run the

command prompt task - since you know that works okay.



Try to Run your new or troublesome task, observe the columns, and the

log. If your task fails to run manually, the errors in the log file

are the clues to what to do next.

 

[Jose]

On Mar 2, 11:25 am, J Tinsby wrote:

> Hello,

>

> I have been trying, with little or no success, to get TS to run my

> Auslogic defrag program once a week. Seems that no matter what I do it

> won't start, BUT..... it did once as the log shows. After that at the

> appointed time it never runs.

>

> In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

> Defrag\cdefrag.exe" C: D: -bk

>

> The START IN box is blank

>

> The exerpt from the log on the day it ran successfully is:

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

>         Started 2/22/2010 10:00:12 AM

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

>         Finished 2/22/2010 10:01:09 AM

>         Result: The task completed with an exit code of (0).

>

> Note that I did not create the run line, it was put there when I

> installed the Auslogic program.

>

> I only need the program to run once a week, I have also tried having

> it wake up the machine from S3 standby, or from totally OFF, but that

> doesn't work either.

>

> What can I do to make it work as it should? I am using XP Pro with SP3

> and all updates installed.

>

> Thank you very much for any help you might give me.

>

> J Tinsby



Okay - I installed Auslogics, set up a ST and ran it manually on

various drives, then let it run itself automatically (I set the time 5

minutes into the future and waited).



My ST log has entries that look similar to yours, but my job ran

longer with a 40GB drive about 50% full:



"Auslogics Boost Speed Disk Defrag Console

Defragmentation.job" (cdefrag.exe)

Started 3/2/2010 1:55:23 PM

"Auslogics Boost Speed Disk Defrag Console

Defragmentation.job" (cdefrag.exe)

Finished 3/2/2010 2:10:46 PM



This makes sense - the Auslogics shouldn't be writing to the Windows

ST log file... that is just for ST information, not too much about

what actually happens with the application behind the task - that is a

different log.



The results of the Auslogics effort are stored in the user profile

folder for the user that installed Auslogics, which for me is here:



C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

\Logs



There is a nice HTML report you can open in your browser to see how it

went. When you set up the job in Auslogics there is a link to click

to take you right to the log files.



You should also read up on the "rules" for Auslogics and how it

decides if your drive needs attention or not and how it might be time

to run according to the ST schedule, but Auslogics may decide it is

not the right moment to run the defrag because of other things.

 

[Lem]

J Tinsby wrote:

> Hello,

>

> I have been trying, with little or no success, to get TS to run my

> Auslogic defrag program once a week. Seems that no matter what I do it

> won't start, BUT..... it did once as the log shows. After that at the

> appointed time it never runs.

>

> In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

> Defrag\cdefrag.exe" C: D: -bk

>

> The START IN box is blank

>

> The exerpt from the log on the day it ran successfully is:

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

> Started 2/22/2010 10:00:12 AM

> "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> (cdefrag.exe)

> Finished 2/22/2010 10:01:09 AM

> Result: The task completed with an exit code of (0).

>

> Note that I did not create the run line, it was put there when I

> installed the Auslogic program.

>

> I only need the program to run once a week, I have also tried having

> it wake up the machine from S3 standby, or from totally OFF, but that

> doesn't work either.

>

> What can I do to make it work as it should? I am using XP Pro with SP3

> and all updates installed.

>

> Thank you very much for any help you might give me.

>

> J Tinsby



TS can be finicky about what it runs. Sometimes, I've been able to

resolve a situation such as you describe (it used to work, but now it

doesn't) by deleting the task and then re-creating it. Or try this:



- Start event viewer (Start > Run > eventvwr.exe)

- Clear the Application and System logs

- Open Task Scheduler, right click your desired task and select "Run"

- Go back to the event viewer and see what the error message is. If you

didn't close event viewer, select one of the logs, then click on

"Refresh" in the "Actions" menu.



If you can't figure out the problem yourself from the error message,

click on the icon just below the up/down arrows in the "Event

Properties" display and then paste into your next post.



--

Lem



Apollo 11 - 40 years ago:

http://www.nasa.gov/mission_pages/apollo/40th/index.html

 

[Jose]

On Mar 2, 2:27 pm, Jose wrote:

> On Mar 2, 11:25 am, J Tinsby wrote:

>

>

>

>

>

> > Hello,

>

> > I have been trying, with little or no success, to get TS to run my

> > Auslogic defrag program once a week. Seems that no matter what I do it

> > won't start, BUT..... it did once as the log shows. After that at the

> > appointed time it never runs.

>

> > In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

> > Defrag\cdefrag.exe" C: D: -bk

>

> > The START IN box is blank

>

> > The exerpt from the log on the day it ran successfully is:

> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> > (cdefrag.exe)

> >         Started 2/22/2010 10:00:12 AM

> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> > (cdefrag.exe)

> >         Finished 2/22/2010 10:01:09 AM

> >         Result: The task completed with an exit code of (0).

>

> > Note that I did not create the run line, it was put there when I

> > installed the Auslogic program.

>

> > I only need the program to run once a week, I have also tried having

> > it wake up the machine from S3 standby, or from totally OFF, but that

> > doesn't work either.

>

> > What can I do to make it work as it should? I am using XP Pro with SP3

> > and all updates installed.

>

> > Thank you very much for any help you might give me.

>

> > J Tinsby

>

> Okay - I installed Auslogics, set up a ST and ran it manually on

> various drives, then let it run itself automatically (I set the time 5

> minutes into the future and waited).

>

> My ST log has entries that look similar to yours, but my job ran

> longer with a 40GB drive about 50% full:

>

> "Auslogics Boost Speed Disk Defrag Console

> Defragmentation.job" (cdefrag.exe)

>         Started 3/2/2010 1:55:23 PM

> "Auslogics Boost Speed Disk Defrag Console

> Defragmentation.job" (cdefrag.exe)

>         Finished 3/2/2010 2:10:46 PM

>

> This makes sense - the Auslogics shouldn't be writing to the Windows

> ST log file...  that is just for ST information, not too much about

> what actually happens with the application behind the task - that is a

> different log.

>

> The results of the Auslogics effort are stored in the user profile

> folder for the user that installed Auslogics, which for me is here:

>

> C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

> \Logs

>

> There is a nice HTML report you can open in your browser to see how it

> went.  When you set up the job in Auslogics there is a link to click

> to take you right to the log files.

>

> You should also read up on the "rules" for Auslogics and how it

> decides if your drive needs attention or not and how it might be time

> to run according to the ST schedule, but Auslogics may decide it is

> not the right moment to run the defrag because of other things.



....and when Auslogics sets up the ST itself, it will use the NT

AUTHORITY\SYSTEM account which is fine and has no password which is

also fine.



If you run then the task manually you will not see much until is is

done and check the Auslogics log. If you change the Properties of the

task to run as your currently logged in account and password, you can

watch it run.

 

[J Tinsby]

Hi Jose and all,



thank you for the very comprehensive help with the dreaded TS

program.



I made a new account to test things as you suggested. I cleaned out

the TS logfile too. Then I set it up to run the C prompt and that

worked when I hit RUN.



I then made a new start time using the new account and password, I

don't understand why this is necesary. the Auslogic did run once with

no password using the NTAUTORITY\SYSTEM but now it won't.



Anyway using the new account and new p/w I set up to run Auslogic it

started on it's own but wouldn't stop! I had to manually do it. In

fact even though it said it was running I saw no HD activity at all

and the program never actually opened on my monitor.



The Schedlgu.log says:



"Auslogics Disk Defrag.job" (DISKDE~1.EXE) 3/2/2010 7:11:45 PM **

WARNING **

The task was terminated. This action was initiated either by

an administrator or by the Task Scheduler service (because, for

example, the computer is now non idle).





So I don't know what to think, yes it starts and 'says' its running

but there is no HD activity at all. The machine was idle when it

started and I just sat and watched it and after a few minutes I had to

stop it even though I wasn't convinced it was really running.



At this point what do you think? And can I go back to the

NTAUTORITY\SYSTEM or let it alone with the new user account?



Thanks for all you posted to help me.



J Tinsby





On Tue, 2 Mar 2010 14:03:16 -0800 (PST), Jose

wrote:



>On Mar 2, 2:27 pm, Jose wrote:

>> On Mar 2, 11:25 am, J Tinsby wrote:

>>

>>

>>

>>

>>

>> > Hello,

>>

>> > I have been trying, with little or no success, to get TS to run my

>> > Auslogic defrag program once a week. Seems that no matter what I do it

>> > won't start, BUT..... it did once as the log shows. After that at the

>> > appointed time it never runs.

>>

>> > In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

>> > Defrag\cdefrag.exe" C: D: -bk

>>

>> > The START IN box is blank

>>

>> > The exerpt from the log on the day it ran successfully is:

>> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

>> > (cdefrag.exe)

>> >         Started 2/22/2010 10:00:12 AM

>> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

>> > (cdefrag.exe)

>> >         Finished 2/22/2010 10:01:09 AM

>> >         Result: The task completed with an exit code of (0).

>>

>> > Note that I did not create the run line, it was put there when I

>> > installed the Auslogic program.

>>

>> > I only need the program to run once a week, I have also tried having

>> > it wake up the machine from S3 standby, or from totally OFF, but that

>> > doesn't work either.

>>

>> > What can I do to make it work as it should? I am using XP Pro with SP3

>> > and all updates installed.

>>

>> > Thank you very much for any help you might give me.

>>

>> > J Tinsby

>>

>> Okay - I installed Auslogics, set up a ST and ran it manually on

>> various drives, then let it run itself automatically (I set the time 5

>> minutes into the future and waited).

>>

>> My ST log has entries that look similar to yours, but my job ran

>> longer with a 40GB drive about 50% full:

>>

>> "Auslogics Boost Speed Disk Defrag Console

>> Defragmentation.job" (cdefrag.exe)

>>         Started 3/2/2010 1:55:23 PM

>> "Auslogics Boost Speed Disk Defrag Console

>> Defragmentation.job" (cdefrag.exe)

>>         Finished 3/2/2010 2:10:46 PM

>>

>> This makes sense - the Auslogics shouldn't be writing to the Windows

>> ST log file...  that is just for ST information, not too much about

>> what actually happens with the application behind the task - that is a

>> different log.

>>

>> The results of the Auslogics effort are stored in the user profile

>> folder for the user that installed Auslogics, which for me is here:

>>

>> C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

>> \Logs

>>

>> There is a nice HTML report you can open in your browser to see how it

>> went.  When you set up the job in Auslogics there is a link to click

>> to take you right to the log files.

>>

>> You should also read up on the "rules" for Auslogics and how it

>> decides if your drive needs attention or not and how it might be time

>> to run according to the ST schedule, but Auslogics may decide it is

>> not the right moment to run the defrag because of other things.

>

>...and when Auslogics sets up the ST itself, it will use the NT

>AUTHORITY\SYSTEM account which is fine and has no password which is

>also fine.

>

>If you run then the task manually you will not see much until is is

>done and check the Auslogics log. If you change the Properties of the

>task to run as your currently logged in account and password, you can

>watch it run.

 

[Jose]

On Mar 2, 7:25 pm, J Tinsby wrote:

> Hi Jose and all,

>

>  thank you for the very comprehensive help with the dreaded TS

> program.

>

> I made a new account to test things as you suggested. I cleaned out

> the TS logfile too. Then I set it up to run the C prompt and that

> worked when I hit RUN.

>

> I then made a new start time using the new account and password, I

> don't understand why this is necesary. the Auslogic did run once with

> no password using the NTAUTORITY\SYSTEM but now it won't.

>

> Anyway using the new account and new p/w I set up to run Auslogic it

> started on it's own but wouldn't stop! I had to manually do it. In

> fact even though it said it was running I saw no HD activity at all

> and the program never actually opened on my monitor.

>

> The Schedlgu.log says:

>

> "Auslogics Disk Defrag.job" (DISKDE~1.EXE) 3/2/2010 7:11:45 PM **

> WARNING **

>         The task was terminated. This action was initiated eitherby

> an administrator or by the Task Scheduler service (because, for

> example, the computer is now non idle).

>

> So I don't know what to think, yes it starts and 'says' its running

> but there is no HD activity at all. The machine was idle when it

> started and I just sat and watched it and after a few minutes I had to

> stop it even though I wasn't convinced it was really running.

>

> At this point what do you think? And can I go back to the

> NTAUTORITY\SYSTEM or let it alone with the new user account?

>

> Thanks for all you posted to help me.

>

> J Tinsby

>

> On Tue, 2 Mar 2010 14:03:16 -0800 (PST), Jose

> wrote:

>

>

>

> >On Mar 2, 2:27 pm, Jose wrote:

> >> On Mar 2, 11:25 am, J Tinsby wrote:

>

> >> > Hello,

>

> >> > I have been trying, with little or no success, to get TS to run my

> >> > Auslogic defrag program once a week. Seems that no matter what I do it

> >> > won't start, BUT..... it did once as the log shows. After that at the

> >> > appointed time it never runs.

>

> >> > In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

> >> > Defrag\cdefrag.exe" C: D: -bk

>

> >> > The START IN box is blank

>

> >> > The exerpt from the log on the day it ran successfully is:

> >> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> >> > (cdefrag.exe)

> >> >         Started 2/22/2010 10:00:12 AM

> >> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

> >> > (cdefrag.exe)

> >> >         Finished 2/22/2010 10:01:09 AM

> >> >         Result: The task completed with an exit code of (0).

>

> >> > Note that I did not create the run line, it was put there when I

> >> > installed the Auslogic program.

>

> >> > I only need the program to run once a week, I have also tried having

> >> > it wake up the machine from S3 standby, or from totally OFF, but that

> >> > doesn't work either.

>

> >> > What can I do to make it work as it should? I am using XP Pro with SP3

> >> > and all updates installed.

>

> >> > Thank you very much for any help you might give me.

>

> >> > J Tinsby

>

> >> Okay - I installed Auslogics, set up a ST and ran it manually on

> >> various drives, then let it run itself automatically (I set the time 5

> >> minutes into the future and waited).

>

> >> My ST log has entries that look similar to yours, but my job ran

> >> longer with a 40GB drive about 50% full:

>

> >> "Auslogics Boost Speed Disk Defrag Console

> >> Defragmentation.job" (cdefrag.exe)

> >>         Started 3/2/2010 1:55:23 PM

> >> "Auslogics Boost Speed Disk Defrag Console

> >> Defragmentation.job" (cdefrag.exe)

> >>         Finished 3/2/2010 2:10:46 PM

>

> >> This makes sense - the Auslogics shouldn't be writing to the Windows

> >> ST log file...  that is just for ST information, not too much about

> >> what actually happens with the application behind the task - that is a

> >> different log.

>

> >> The results of the Auslogics effort are stored in the user profile

> >> folder for the user that installed Auslogics, which for me is here:

>

> >> C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

> >> \Logs

>

> >> There is a nice HTML report you can open in your browser to see how it

> >> went.  When you set up the job in Auslogics there is a link to click

> >> to take you right to the log files.

>

> >> You should also read up on the "rules" for Auslogics and how it

> >> decides if your drive needs attention or not and how it might be time

> >> to run according to the ST schedule, but Auslogics may decide it is

> >> not the right moment to run the defrag because of other things.

>

> >...and when Auslogics sets up the ST itself, it will use the NT

> >AUTHORITY\SYSTEM account which is fine and has no password which is

> >also fine.

>

> >If you run then the task manually you will not see much until is is

> >done and check the Auslogics log.  If you change the Properties of the

> >task to run as your currently logged in account and password, you can

> >watch it run.



I didn't remember much about Auslogics until I reinstalled it again,

so this is what I would do...



Put a password on the account you use to login. You don't have to

login again - just put a password on your account to make the

Scheduled Task happy.



If you set up a new account and PW and use it to run the task and you

login with your regular account, it will run, but you will not be able

to see it (that may not have been the best troubleshooting advice).

Later when it is working, you can just leave the user NT AUTHORITY

\SYSTEM if you want.



Browse to c:\windows\tasks, delete all the Auslogics tasks, clear the

task scheduler log (stop the service, remove the log, restart the

service).



Clean up any mess and delete any old Auslogics logs from your profile

folder. For user Jose, I empty this folder:



C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

\Logs



From the Auslogics program, schedule your task. Just make a simple

task for one drive and change it later when you know everything

works.



Browse to c:\windows\tasks and right click the new Auslogics task,

Properties.



Do not change the task Run line that Auslogics set up for you.



The Run as: box contains NT AUTHORITY\SYSTEM so change it to the

account you are currently logged into the computer with and set the

password - this is the only way you will be able to actually watch it

run. I changed mine to Jose and my password because I am logged into

XP as Jose.



Right click the task and run it, you should see a window open up to

analyze your disk and defrag it if Auslogics thinks it need

defragging. It may take a log time to finish, it may take a few

seconds but you should be able to see at least the windows open and

the analysis.



The window will close and the Auslogics report (for Jose) is in this

folder:



C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

\Logs



My drive that has zero fragmentation (according to Auslogics) looks

like this:



Run as Jose (I saw it run in a window)



Disk Size 297.44 GB

Free Space Size 282.50 GB

Clusters 77970943

Sectors per cluster 8

Bytes per sector 512

Started defragmentation at 3/3/2010 7:00:38 AM

Completed defragmentation at 3/3/2010 7:00:38 AM

Elapsed time 00:00:00

Total Files 14701

Total Directories 512

Fragmented Files 0

Defragmented Files 0

Skipped Files 0

Fragmentation Before 0.00%

Fragmentation After 0.00%



Now you know the task really works because you saw it actually run and

you have a good looking log file.



Change the Properties of the task Run as: back to NT AUTHORITY\SYSTEM

with no password and run it again. You will not see it open a window

and run, but you will have a new report. You can see I just did this

and observe the time on my reports:



Three minutes later after I changed the task Run as to NT AUTHORITY

\SYSTEM (I did not see it run in a window)



Disk Size 297.44 GB

Free Space Size 282.50 GB

Clusters 77970943

Sectors per cluster 8

Bytes per sector 512

Started defragmentation at 3/3/2010 7:03:45 AM

Completed defragmentation at 3/3/2010 7:03:45 AM

Elapsed time 00:00:00

Total Files 14701

Total Directories 512

Fragmented Files 0

Defragmented Files 0

Skipped Files 0

Fragmentation Before 0.00%

Fragmentation After 0.00%

 

[J Tinsby]

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:



>Disk Size 297.44 GB

>Free Space Size 282.50 GB

>Clusters 77970943

>Sectors per cluster 8

>Bytes per sector 512

>Started defragmentation at 3/3/2010 7:00:38 AM

>Completed defragmentation at 3/3/2010 7:00:38 AM

>Elapsed time 00:00:00

>Total Files 14701

>Total Directories 512

>Fragmented Files 0

>Defragmented Files 0

>Skipped Files 0

>Fragmentation Before 0.00%

>Fragmentation After 0.00%



I don't know where that comes from unless its from the Auslogic log

which I can't find. I do have Windows Explorer set to show all folders

and I still can't locate it.



I truly appreciate all your time and trouble and can't really thank

you enough you have gone to great lengths to help me. I think the

Auslogic program is worth using and I'd like to have it run

automatically but that idea seems to be fading fast.



If I use the NT AUTHORITY\SYSTEM line, can I then remove the p/w from

my account or must it stay there as well? Remember the program DID run

once automatically with no password, I just can't see why it won't run

like it did.



Regards,



J T































On Wed, 3 Mar 2010 04:23:47 -0800 (PST), Jose

wrote:



>On Mar 2, 7:25 pm, J Tinsby wrote:

>> Hi Jose and all,

>>

>>  thank you for the very comprehensive help with the dreaded TS

>> program.

>>

>> I made a new account to test things as you suggested. I cleaned out

>> the TS logfile too. Then I set it up to run the C prompt and that

>> worked when I hit RUN.

>>

>> I then made a new start time using the new account and password, I

>> don't understand why this is necesary. the Auslogic did run once with

>> no password using the NTAUTORITY\SYSTEM but now it won't.

>>

>> Anyway using the new account and new p/w I set up to run Auslogic it

>> started on it's own but wouldn't stop! I had to manually do it. In

>> fact even though it said it was running I saw no HD activity at all

>> and the program never actually opened on my monitor.

>>

>> The Schedlgu.log says:

>>

>> "Auslogics Disk Defrag.job" (DISKDE~1.EXE) 3/2/2010 7:11:45 PM **

>> WARNING **

>>         The task was terminated. This action was initiated either by

>> an administrator or by the Task Scheduler service (because, for

>> example, the computer is now non idle).

>>

>> So I don't know what to think, yes it starts and 'says' its running

>> but there is no HD activity at all. The machine was idle when it

>> started and I just sat and watched it and after a few minutes I had to

>> stop it even though I wasn't convinced it was really running.

>>

>> At this point what do you think? And can I go back to the

>> NTAUTORITY\SYSTEM or let it alone with the new user account?

>>

>> Thanks for all you posted to help me.

>>

>> J Tinsby

>>

>> On Tue, 2 Mar 2010 14:03:16 -0800 (PST), Jose

>> wrote:

>>

>>

>>

>> >On Mar 2, 2:27 pm, Jose wrote:

>> >> On Mar 2, 11:25 am, J Tinsby wrote:

>>

>> >> > Hello,

>>

>> >> > I have been trying, with little or no success, to get TS to run my

>> >> > Auslogic defrag program once a week. Seems that no matter what I do it

>> >> > won't start, BUT..... it did once as the log shows. After that at the

>> >> > appointed time it never runs.

>>

>> >> > In the RUN line I have "C:\Program Files\Auslogics\Auslogics Disk

>> >> > Defrag\cdefrag.exe" C: D: -bk

>>

>> >> > The START IN box is blank

>>

>> >> > The exerpt from the log on the day it ran successfully is:

>> >> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

>> >> > (cdefrag.exe)

>> >> >         Started 2/22/2010 10:00:12 AM

>> >> > "Auslogics Boost Speed Disk Defrag Console Defragmentation.job"

>> >> > (cdefrag.exe)

>> >> >         Finished 2/22/2010 10:01:09 AM

>> >> >         Result: The task completed with an exit code of (0).

>>

>> >> > Note that I did not create the run line, it was put there when I

>> >> > installed the Auslogic program.

>>

>> >> > I only need the program to run once a week, I have also tried having

>> >> > it wake up the machine from S3 standby, or from totally OFF, but that

>> >> > doesn't work either.

>>

>> >> > What can I do to make it work as it should? I am using XP Pro with SP3

>> >> > and all updates installed.

>>

>> >> > Thank you very much for any help you might give me.

>>

>> >> > J Tinsby

>>

>> >> Okay - I installed Auslogics, set up a ST and ran it manually on

>> >> various drives, then let it run itself automatically (I set the time 5

>> >> minutes into the future and waited).

>>

>> >> My ST log has entries that look similar to yours, but my job ran

>> >> longer with a 40GB drive about 50% full:

>>

>> >> "Auslogics Boost Speed Disk Defrag Console

>> >> Defragmentation.job" (cdefrag.exe)

>> >>         Started 3/2/2010 1:55:23 PM

>> >> "Auslogics Boost Speed Disk Defrag Console

>> >> Defragmentation.job" (cdefrag.exe)

>> >>         Finished 3/2/2010 2:10:46 PM

>>

>> >> This makes sense - the Auslogics shouldn't be writing to the Windows

>> >> ST log file...  that is just for ST information, not too much about

>> >> what actually happens with the application behind the task - that is a

>> >> different log.

>>

>> >> The results of the Auslogics effort are stored in the user profile

>> >> folder for the user that installed Auslogics, which for me is here:

>>

>> >> C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

>> >> \Logs

>>

>> >> There is a nice HTML report you can open in your browser to see how it

>> >> went.  When you set up the job in Auslogics there is a link to click

>> >> to take you right to the log files.

>>

>> >> You should also read up on the "rules" for Auslogics and how it

>> >> decides if your drive needs attention or not and how it might be time

>> >> to run according to the ST schedule, but Auslogics may decide it is

>> >> not the right moment to run the defrag because of other things.

>>

>> >...and when Auslogics sets up the ST itself, it will use the NT

>> >AUTHORITY\SYSTEM account which is fine and has no password which is

>> >also fine.

>>

>> >If you run then the task manually you will not see much until is is

>> >done and check the Auslogics log.  If you change the Properties of the

>> >task to run as your currently logged in account and password, you can

>> >watch it run.

>

>I didn't remember much about Auslogics until I reinstalled it again,

>so this is what I would do...

>

>Put a password on the account you use to login. You don't have to

>login again - just put a password on your account to make the

>Scheduled Task happy.

>

>If you set up a new account and PW and use it to run the task and you

>login with your regular account, it will run, but you will not be able

>to see it (that may not have been the best troubleshooting advice).

>Later when it is working, you can just leave the user NT AUTHORITY

>\SYSTEM if you want.

>

>Browse to c:\windows\tasks, delete all the Auslogics tasks, clear the

>task scheduler log (stop the service, remove the log, restart the

>service).

>

>Clean up any mess and delete any old Auslogics logs from your profile

>folder. For user Jose, I empty this folder:

>

>C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

>\Logs

>

>From the Auslogics program, schedule your task. Just make a simple

>task for one drive and change it later when you know everything

>works.

>

>Browse to c:\windows\tasks and right click the new Auslogics task,

>Properties.

>

>Do not change the task Run line that Auslogics set up for you.

>

>The Run as: box contains NT AUTHORITY\SYSTEM so change it to the

>account you are currently logged into the computer with and set the

>password - this is the only way you will be able to actually watch it

>run. I changed mine to Jose and my password because I am logged into

>XP as Jose.

>

>Right click the task and run it, you should see a window open up to

>analyze your disk and defrag it if Auslogics thinks it need

>defragging. It may take a log time to finish, it may take a few

>seconds but you should be able to see at least the windows open and

>the analysis.

>

>The window will close and the Auslogics report (for Jose) is in this

>folder:

>

>C:\Documents and Settings\Jose\Application Data\Auslogics\Disk Defrag

>\Logs

>

>My drive that has zero fragmentation (according to Auslogics) looks

>like this:

>

>Run as Jose (I saw it run in a window)

>

>Disk Size 297.44 GB

>Free Space Size 282.50 GB

>Clusters 77970943

>Sectors per cluster 8

>Bytes per sector 512

>Started defragmentation at 3/3/2010 7:00:38 AM

>Completed defragmentation at 3/3/2010 7:00:38 AM

>Elapsed time 00:00:00

>Total Files 14701

>Total Directories 512

>Fragmented Files 0

>Defragmented Files 0

>Skipped Files 0

>Fragmentation Before 0.00%

>Fragmentation After 0.00%

>

>Now you know the task really works because you saw it actually run and

>you have a good looking log file.

>

>Change the Properties of the task Run as: back to NT AUTHORITY\SYSTEM

>with no password and run it again. You will not see it open a window

>and run, but you will have a new report. You can see I just did this

>and observe the time on my reports:

>

>Three minutes later after I changed the task Run as to NT AUTHORITY

>\SYSTEM (I did not see it run in a window)

>

>Disk Size 297.44 GB

>Free Space Size 282.50 GB

>Clusters 77970943

>Sectors per cluster 8

>Bytes per sector 512

>Started defragmentation at 3/3/2010 7:03:45 AM

>Completed defragmentation at 3/3/2010 7:03:45 AM

>Elapsed time 00:00:00

>Total Files 14701

>Total Directories 512

>Fragmented Files 0

>Defragmented Files 0

>Skipped Files 0

>Fragmentation Before 0.00%

>Fragmentation After 0.00%

 

[Jose]

On Mar 3, 11:21 am, J Tinsby 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.

 

[J Tinsby]

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

wrote:



>On Mar 3, 11:21 am, J Tinsby 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.

 

[Jose]

On Mar 3, 9:44 pm, J Tinsby 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

> wrote:

>

>

>

> >On Mar 3, 11:21 am, J Tinsby 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.

 

[J Tinsby]

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

wrote:



>On Mar 3, 9:44 pm, J Tinsby 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

>> wrote:

>>

>>

>>

>> >On Mar 3, 11:21 am, J Tinsby 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.

 

[Jose]

On Mar 4, 10:49 am, J Tinsby 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

> wrote:

>

>

>

> >On Mar 3, 9:44 pm, J Tinsby 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

> >> wrote:

>

> >> >On Mar 3, 11:21 am, J Tinsby 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 thatI

> >> >> 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.

 

[Twayne]

In news:46ef0e1c-0d21-42f2-b590-cbea2192cb30@19g2000yqu.googlegroups.com,

Jose typed:

> On Mar 4, 10:49 am, J Tinsby 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

>> wrote:

>>

>>

>>

>>> On Mar 3, 9:44 pm, J Tinsby 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

>>>> wrote:

>>

>>>>> On Mar 3, 11:21 am, J Tinsby 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.

 

[J Tinsby]

On Tue, 02 Mar 2010 14:35:56 -0500, Lem wrote:

>

>TS can be finicky about what it runs. Sometimes, I've been able to

>resolve a situation such as you describe (it used to work, but now it

>doesn't) by deleting the task and then re-creating it. Or try this:

>

>- Start event viewer (Start > Run > eventvwr.exe)

>- Clear the Application and System logs

>- Open Task Scheduler, right click your desired task and select "Run"

>- Go back to the event viewer and see what the error message is. If you

>didn't close event viewer, select one of the logs, then click on

>"Refresh" in the "Actions" menu.

>

>If you can't figure out the problem yourself from the error message,

>click on the icon just below the up/down arrows in the "Event

>Properties" display and then paste into your next post.



Hi Lem and Jose and all who tried to help me.



I am sorry to report that nothing seems to work, I've done all the

things suggested and can't get TS to make Auslogics run when I want it

to. So in effect I will put all of you out of your misery trying to

help me and call it quits.



I will be the first one to say that on this topic all of you have

spent the most time EVER in your efforts to get the thing to work and

I really appreciate it!



I may fool with it from time to time but I think I am beating a dead

horse. But I may try once more and end up sending a log of why it

didn't run..........Jose suggested I have TS run a command prompt and

that worked fine, so I don't know why the trouble with the defrag.



So thanks very very much to all of you once again, you are the best!



Cheers,



J Tinsby

 

[Jose]

On Mar 14, 2:18 pm, J Tinsby wrote:

> On Tue, 02 Mar 2010 14:35:56 -0500, Lem wrote:

>

> >TS can be finicky about what it runs.  Sometimes, I've been able to

> >resolve a situation such as you describe (it used to work, but now it

> >doesn't) by deleting the task and then re-creating it.  Or try this:

>

> >- Start event viewer (Start > Run > eventvwr.exe)

> >- Clear the Application and System logs

> >- Open Task Scheduler, right click your desired task and select "Run"

> >- Go back to the event viewer and see what the error message is. If you

> >didn't close event viewer, select one of the logs, then click on

> >"Refresh" in the "Actions" menu.

>

> >If you can't figure out the problem yourself from the error message,

> >click on the icon just below the up/down arrows in the "Event

> >Properties" display and then paste into your next post.

>

> Hi Lem and Jose and all who tried to help me.

>

> I am sorry to report that nothing seems to work, I've done all the

> things suggested and can't get TS to make Auslogics run when I want it

> to. So in effect I will put all of you out of your misery trying to

> help me and call it quits.

>

> I will be the first one to say that on this topic all of you have

> spent the most time EVER in your efforts to get the thing to work and

> I really appreciate it!

>

> I may fool with it from time to time but I think I am beating a dead

> horse. But I may try once more and end up sending a log of why it

> didn't run..........Jose suggested I have TS run a command prompt and

> that worked fine, so I don't know why the trouble with the defrag.

>

> So thanks very very much to all of you once again, you are the best!

>

> Cheers,

>

> J Tinsby



Refresh my memory on what it is that you expect to see that you are

not seeing or what it is that you do see that you are not expecting

to see?



If you set up a ST and the task does not run, XP will not be able to

figure out that the task was missed and decide to run it *now*. It

will wait until the next time the system is running and the time for

the task is at hand.



If the system is running and the ST does not start when it is supposed

to, there is an explanation for it.



What did you explain to Auslogic and what did they say back to you?

 

[J Tinsby]

Lem,



I did all you suggested to no avail, cleared out all the logs under

EVENTS.

Ran the program manually ( it started and ran fine ) but it put

nothing in the event's log even after using 'refresh' nothing

appeared. It did add to the TS log however.



I put the machine in S-3 standby to see if it would wake up and run,

it wouldn't. Then I shut it off entirely to see if it would wake up

from that state and run and it wouldn't.



The easiest thing at this point is just to click the Auslogics icon

and run it when I please. There seems to be no resolution to what

should be a simple problem, even with all your expert help we can't

crack it. I should mention I am using the TS under the

NTAUTHORITY/SYSTEM if that matters. Having a p/w on it never seemed to

make a difference.



The TS will run IF the machine is already on, other than that, at

least on this machine it's useless. On older machines I was able to

get it run things with no trouble, now for some reason it's being

impossibly difficult for no apparent reason.



Regards,



J T

 

[Jose]

On Mar 14, 6:11 pm, J Tinsby wrote:

> Lem,

>

> I did all you suggested to no avail, cleared out all the logs under

> EVENTS.

> Ran the program manually ( it started and ran fine ) but it put

> nothing in the event's log even after using 'refresh' nothing

> appeared. It did add to the TS log however.

>

> I put the machine in S-3 standby to see if it would wake up and run,

> it wouldn't. Then I shut it off entirely to see if it would wake up

> from that state and run and it wouldn't.

>

> The easiest thing at this point is just to click the Auslogics icon

> and run it when I please. There seems to be no resolution to what

> should be a simple problem, even with all your expert help we can't

> crack it. I should mention I am using the TS under the

> NTAUTHORITY/SYSTEM if that matters. Having a p/w on it never seemed to

> make a difference.

>

> The TS will run IF the machine is already on, other than that, at

> least on this machine it's useless. On older machines I was able to

> get it run things with no trouble, now for some reason it's being

> impossibly difficult for no apparent reason.

>

> Regards,

>

> J T



Check the Task Properties, Settings tab and check the box to Wake the

computer to run this task.



If the system is in Stand By and the Task is configured properly, it

will wake the computer and run the task. Any task.



There will will be info in the Task log, and in the Auslogics log.

This is what I see when I used set Auslogics to run a task a few

minutes in the future, then I adjusted the Task Properties by hand to

Wake the computer to run the task (you can't set this property for the

task using Auslogics) and put my computer in Stand By - then waited 3

minutes:



"Auslogics Boost Speed Disk Defrag Console

Defragmentation.job" (cdefrag.exe)

Started 3/15/2010 7:32:12 AM

"Auslogics Boost Speed Disk Defrag Console

Defragmentation.job" (cdefrag.exe)

Finished 3/15/2010 7:32:28 AM

Result: The task completed with an exit code of (0).



If you do not set the Wake the computer to run this task box in the

Task Properties by hand, the task will never come out of Stand By to

run. If you check the box, the task will wake the computer and run.



If the computer is turned off the task will of course not run.



If the computer is in Hibernate, the task may or may not run depending

on your hardware. That has nothing to do with Auslogics or Task

Scheduler.



You should leave the Task credentials and NT AUTHORITY\SYSTEM. That

account has no password.

 

[J Tinsby]

On Mon, 15 Mar 2010 04:46:53 -0700 (PDT), Jose

wrote:



>Check the Task Properties, Settings tab and check the box to Wake the

>computer to run this task.

>

>If the system is in Stand By and the Task is configured properly, it

>will wake the computer and run the task. Any task.

>

>There will will be info in the Task log, and in the Auslogics log.

>This is what I see when I used set Auslogics to run a task a few

>minutes in the future, then I adjusted the Task Properties by hand to

>Wake the computer to run the task (you can't set this property for the

>task using Auslogics) and put my computer in Stand By - then waited 3

>minutes:

>

>"Auslogics Boost Speed Disk Defrag Console

>Defragmentation.job" (cdefrag.exe)

> Started 3/15/2010 7:32:12 AM

>"Auslogics Boost Speed Disk Defrag Console

>Defragmentation.job" (cdefrag.exe)

> Finished 3/15/2010 7:32:28 AM

> Result: The task completed with an exit code of (0).

>

>If you do not set the Wake the computer to run this task box in the

>Task Properties by hand, the task will never come out of Stand By to

>run. If you check the box, the task will wake the computer and run.

>

>If the computer is turned off the task will of course not run.

>

>If the computer is in Hibernate, the task may or may not run depending

>on your hardware. That has nothing to do with Auslogics or Task

>Scheduler.

>

>You should leave the Task credentials and NT AUTHORITY\SYSTEM. That

>account has no password.





Hello Jose ,



Well I am hoping to get the TS to run the defrag when the machine is

on standby , yes it is set to wake up the machine to run the process.



As far as Auslogics they promised twice to answer my questions but

never did, they are a bit of a disappoinment as far as I am concerned.

If they don't have tech support for a free program they should just

say so and not lie and say "we'll get back to you in 24 to 48 hours."



Maybe I am expecting the TS to run the program EXACTLY AT THE TIME I

HAVE IT SET FOR................. maybe for whatever reason it won't

start then but many minutes later. But if the machine is on standby

it's not doing anything else I would think it would start relatively

quickly.



J T