Hello,

Here is an excerpt from AutoRun.tg I was using with WinCron v3.6:
--------------------------------
#
{
-start -time 10:00:00 AM
-command o:\1.bat
-action -inc 1 0 0 0
}

#
{
-start -time 11:05:00 AM
-command O:\2.bat
-action -inc 1 0 0 0
}

{
-start -time 11:34:00 AM
-command O:\3.bat
-action -inc 1 0 0 0
}

{
-start -time 2:34:00 PM
-command O:\4.bat
-action -inc 1 0 0 0
}
--------------------------------

I've installed WinCron v4.2 and changed the lines in AutoRun.tg as follows:
--------------------------------
#
{
-start -cron 0 10 * * *
-command o:\1.bat
}

#
{
-start -cron 5 11 * * *
-command O:\2.bat
}

{
-start -cron 34 11 * * *
-command O:\3.bat
}

{
-start -cron 34 14 * * *
-command O:\4.bat
}
--------------------------------

The jobs do not fire on WinCron 4.2 with the new syntax. Is there something wrong with my script?

Thanks for your help!

-Rob

For good measure, I have removed the code from AutoRun.tg and put it in User.tg. I've also added a "-name" to each function.

After restarting the wincron service, the jobs still do not fire.

Would it be possible for you to copy/paste the results from the wincron status window here?

That's really odd that nothing is running. I would like to analyze the output.

How do I open the status window when WinCron is run as a service?

I see no icon in the system tray.

If you are running it in LocalSystem, you should see the little WinCron clock in the systray; double click that.

If you are running WinCron in a USER account (as a service) we'll need to add a logfile directive to start logging to a file.

You would add this as the first job in User.tg.

{
-start -once
-action -logfile "c:\wincron.log"
}

here's a test to run...

In user.tg, put the following:

{
-start -once
-action -logfile "c:\wincron.log"
}

{
-start -cron * * * * *
-action -print "Fire job at %c%"
}


Then use the Control Panel to Stop the WinCron service, then restart it.
You can then list the wincron.log file to see what's going on.

I just did it and this is what it looks like:

Z:\>type c:\wincron.log
Trigger:JOB:227: Thursday, February 05, 2004 13:56:12.
Trigger:JOB:228: Thursday, February 05, 2004 13:56:12.
Fire job at 02/05/04 13:56:12

Z:\>

It is running under a USER account.

I've added (to User.tg) the exact code you provided in your last post.

I've stopped and started the WinCron service out of Control Panel.

No log file was generated!

Hmm. this is really odd.

Would it be possible to rerun these tests from the LocalSystem account? I'm interested in what the WinCron display has to say.

I think we're on to something...:

Text flys by in the status window and then:

WinCron.exe Exception: access violation (0xc0000005), Address: 0x77f64d8a

I try again and this time it did not give me an access violation, however this is what showed up in the status window:

--------------------
Ready.
Completing WinCron installation...
WinCron installation complete.
Running as user 'Administrator' in account 'SYSTEM'
Using email profile 'Seagate'
-+-+-+-+-+-+-+-+
Config.tg: Environment setup complete.
Loading c:\progra~1\tomase~1\wincron\autorun.tab.
1 jobs loaded.
Running as SYSTEM
AutoRun.tg: Complete.
Checking for WinCron update at 02/05/04 17:25:01...
Error in file c:\progra~1\tomase~1\wincron\System.tg
Error: Object doesn't support this property or method: 'objNodeList.nextNode', ; in line 99
Abort called.
Stopping...
Engine Stopped.
--------------------

Is it a good guess that something didn't go well with the upgrade from 3.6 to 4.2?

Also, do a Start/Run:
"C:\Program Files\Tomasello Software\WinCron\WinCron.exe" -application

And let it run for 5 min.. then copy/paste the results here.