CronTab bug fix

[cshandley]

If anyone has had problems where the next CronTab alarm goes off when they use PsiWin or AtomicTime (or otherwise change the Psion's clock), there is a temporary fix available:

http://psion.cshandley.co.uk/CronTabFix.zip


This should please a few FastBackup users who want automated backups using the CronTab macro.
---
Chris Handley

[E}|{]

khm... as for me the problem with CronTab was the fact that planned (crontabbed) events started to function only when Psion was switched on (i.e. it was for egzample impossible to use CronTab for the automated FastBackup backups since the operation started only when i've switched on (opened) my Psion).

in other words -- do you plan to release another fix? :).

[cshandley]

Originally posted by E}|{
khm... as for me the problem with CronTab was the fact that planned
(crontabbed) events started to function only when Psion was switched on (i.e.
it was for example impossible to use CronTab for the automated FastBackup
backups since the operation started only when i've switched on (opened) my
Psion).

I simply do not know WHY the bug is occuring, or even if it is really a problem
with some other software you have installed. This makes it essentially
impossible to fix, since I cannot replicate the problem myself.

My only thought is that you are using CronTab wrong. You could also try using
it after a SOFT reset (make sure you backup first - just in case), before
running ANY other software.


in other words -- do you plan to release another fix? :).

No, for the reasons explained above :(

[ohsix]

I must be doing something wrong, too. I tried using it for an app (BikLog5); a document (Sheet); and a macro (changing wallpaper). I tested each separately. In each case , after setting CronTab, I turned off the machine and watched what happened.

With the app and the document, the machine turned on at the set time, stayed on about 3 seconds then turned off. Neither the app nor the document started before the machine turned itself off. They each started up *after* I turned the machine on.

The macro started during the time CronTab had the machine turned on and had completed its job by the time I turned the machine on.

What sort of things are those of you who use it successfully running? And any ideas as to what might be wrong in setting up CronTab? I don't see where one can have a lot of options in setting something to run in CronTab. As far as I can tell, you set the start date/time, frequency, type, and "what". I have not tried Alarm (don't use that function) or Backup. While I *do* know what a backup is, as I frequently do that :), I don't know just what "Backup" in CronTab actually does. Is it tied in with Chris Handley's FastBackup?

[cshandley]

I have not tried the Backup feature either, but the CronTab code contains a procedure called "backup" which says 'this is not implemented yet'...

I suggest you try Alarm, to see if it works better than using macros.

Are you using CronTab v0.91? If not, download and install it.

Other than that, I really think it is some other software you have installed that is interfering with CronTab - so trying that soft-reset might be an idea. Alternatively, ensure you Psion's auto switch-off time is greater than a minute, but LESS than 30 minutes.

[E}|{]

Originally posted by ohsix
With the app and the document, the machine turned on at the set time, stayed on about 3 seconds then turned off. Neither the app nor the document started before the machine turned itself off. They each started up *after* I turned the machine on.

The macro started during the time CronTab had the machine turned on and had completed its job by the time I turned the machine on.


100% confirm. and it's seems to me that before cshandley's fix it was even worse -- macro mode did not function too (so, thanks for the fix).

well, anyway, i'm able now to use scheduled backup operations with FastBackup.

[vliegfietser]

well, anyway, i'm able now to use scheduled backup operations with FastBackup.

Can you explain, how you solved your problem?? I tried to follow Chris's instructions, but was not successfull.

Thanks in advance.

Jaap

[cshandley]

Can you explain, how you solved your problem?? I tried to follow Chris's instructions, but was not successfull.
Are you able to successfully schedule OTHER alarms in Crontab?

If yes, then you could try describing your problem in more detail. e.g. Do you get any error messages?

[vliegfietser]

Chris wrote:
>Are you able to successfully schedule OTHER alarms in Crontab?


Alarms are working fine.

>If yes, then you could try describing your problem in more detail. e.g. Do you get any error messages?

Documents: not working, they only show up after opening the Mbook after switch on time.

Programs, like biklog5, fastbackup,agenda: not, they only show up/work after opening the Mbook after switch on time.

I don´t see any error messages, but maybe I am looking at the wrong place or don´t have enough time to see it , since at switch-on time the Mbook is only a few seconds on.

Macro´s: same as with programs.

Maybe E}|{ can explain how he solved his problem??

Jaap

[E}|{]

i use CronTab only for FastBackup, so i assume it won't help you to solve your problems with BikLog or other. well, anyway: i use the short program which looks something like the one i mentioned here (http://www.pdastreet.com/forums/showthread.php?s=&threadid=32574) to perfom backup operation with FastBackup; i call this short program via CronTab (with applied cshandley's fix) where i use Macro setting for it. everything works fine :). please confirm if you need more detailed information (yet i don't know what else can i mention).

[cshandley]

Maybe the Mbook OS is itself at fault? I have had another Mbook user who couldn't even RUN FastBackup! Perhaps some other Mbook users could say if they have had success or problems with FastBackup, CronTab, etc?

[E}|{]

vliegfietser, so how are the things going?

[vliegfietser]

vliegfietser, so how are the things going?

I am sorry, was this weekend out-of-town.

I wrote a macro similar to your one in another post, and got the same result as in earlier cases; in other words: the macro or programme is only finished after I have powered on the Mbook after the switch-on time. I did some other experiments and it looks like that the macro or program has been started by Crontab, but that Crontab switchs the Mbook off after 5-10 seconds. It will finish the job after I have powered on the Mbook. I played with the switch off settings without success.

I will repeat my experiments tonight with my old series 5 and Mako to find out if it is related to my Mbook or to Crontab itself as Chris suggested. Maybe other Crontab users with Mbook or other machines can tell their experiences??

I will keep you informed.

Jaap

[E}|{]

and just in order to be sure -- have you applied above-mentioned cshandley's patch to the CronTab?

[vliegfietser]

and just in order to be sure -- have you applied above-mentioned cshandley's patch to the CronTab?

Yes and also tried without the patch.
I have also installed the latest version of Fastbackup. but I don't think that Fastbackup is the culprit.

Jaap

PS Chris, when you investigated the original source code of Crontab, did you find anything related to a timing algorithme for powering off after Crontab has switched on on the defined time??

[cshandley]

Originally posted by vliegfietser
PS Chris, when you investigated the original source code of Crontab, did you find anything related to a timing algorithme for powering off after Crontab has switched on on the defined time?? [/B]

While I thought this issue seems very related to the OS, a quick look does show that it has some code to SwitchOff the machine. I am not (yet) clear quite why it makes a particular decision to switch-off or not, nor how an executing macro is supposed to prevent it from switching it off in the first place.

Really the new official owner(s) of CronTab' source code need to look into this issue, and all I will say is that any feedback on this issue will certainly help them. (Non-specific answer was intentional - you will have to wait for any official announcement!)

[vliegfietser]

Chris and E}|{,

After some playing around with CronTab on my Mbook and on my Mako I found:

(1) Running Crontab with a simple program at a defined time with Crontab on the background but the machine on, CronTab did its work without any problem on both machines. :)

(2) as (1) but now with the machine switched off after setting CronTab on the background, both machines switched on for a few seconds (± 5-8 seconds) and powered off. After switching the psion on, the program executed normally. :mad:

I also changed the switch-off settings, but without any positive result. Again, when alarms are used instead of programs, CronTab is functioning correctly.

In my humble opinion, this bug is not related to a faulty Mbook (are there other Mbook users with this problem??) but most likely to a timing mishap of the switch-off algorithme in CronTab.

Chris, are the new owners of CronTab aware of this problem and more importantly are they willing to find a solution for this bug??? If not, can I write to them?


Jaap

[E}|{]

and what does happen when 'macro' mode is used instead of programs?

i also confirm that the 'app/doc' mode does not work (i was saying that from the very beginning :)), but macroses works fine for me (and i do use macro mode to use FastBackup via the little program that i have mentioned earlier).

[cshandley]

Originally posted by vliegfietser
I also changed the switch-off settings, but without any positive result. Again,
when alarms are used instead of programs, CronTab is functioning
correctly.

E}|{ makes a good point - are you running the FastBackup macro using the "Macro"
mode of CronTab, or the "App/Doc" mode?

Having looked (again) at CronTab's code, I can see that "Macro" mode SHOULD
work. But I can also see that "App/Doc" mode will not work without another
patch; thanks E}|{ :-)

BTW, yes, the relevant people are aware of the issue.
---
Chris Handley

[vliegfietser]

and what does happen when 'macro' mode is used instead of programs?

macro's are working fine!
Chris and E}|{, thanks for helping me with this. I am looking forward to the patch by the new owners of the source code. Meanwhile I will be able to use Fastbackup et al with CronTab in the macro mode.

Jaap

PS. Chris, thanks for the new update of fastbackup!:D

[cshandley]

The fix for the App/Doc bug turned out to be REALLY easy (tut tut Pascal;-) so I've added it to my existing CronTabFix.

You can download it using the link at the start of this thread.

BTW, please report if it works or not. A real quick test on a Netbook seemed to show it does, but...
---
Chris Handley

[vliegfietser]

BTW, please report if it works or not. A real quick test on a Netbook seemed to show it does, but...

Chris, I ran the new patched version of CronTab on my Mbook and on my Mako. Both times it worked without any glitches. :D
Thanks again for your help.

Jaap

[ohsix]

My experience has been different with the fixed CronTabFix. It ran a macro fine. But with an app and a doc, it would now open the app or doc, but then just sit there hung up and never turning off. After killing the app/doc I could then use the machine.

[cshandley]

Originally posted by ohsix
But with an app and a doc, it would now open the app or doc, but then just sit
there hung up and never turning off. After killing the app/doc I could then use
the machine.

Hmmm, fair point, but thats the only way I can stop the Psion turning off before
the app has finished doing it's scheduled task. But this exactly what happens
when you run a macro - CronTab is frozen until the macro finishes!

I suppose I could make the "wait until app has finished" stuff only happen if
CronTab would otherwise switch the Psion off again. Would that help?

Anyway, thanks for pointing this out; I don't use CronTab, and therefore
wouldn't realise there was this kind of conflict of interests.