CLib568 / FreeTime conflict

Using CLib568 and !FreeTime !RunImage dated 14Dec 02.
When run !FreeTime sets the clock back one hour.
When run again – says it so many secs out – but doesn’t correct it.
Going back to CLib566 and it works as it should.

That’s with a RPC SA RO4.02.

!FreeTime sets the clock back one hour

Looking at the source code it does

timehere = time(NULL);

timehere = mktime(gmtime(&timehere));

I’ve compiled a version which you may wish to try to see if I analysed it right. If I have, I’ll try and remember my sourceforge password to make it official (in theory, a run time check could be made for a fixed CLib and the old code used for anyone who hasn’t updated).

Using a SA RPC RO4.02
SCLib version Open and v 5.68 seem to behave the same.
Using them – and !FreeTime – either RunImages – back goes the hour.
It says it 3600 sec out – updating the clock – but doesn’t.
Re-loading the v 5.68 – and using the original Runimage – the clock is reset correctly.
Hope I have got this correct.

Hope I have got this correct

Referring to your original question, I think the combinations worth trying (and my anticipated outcomes) are:

• CLib 5.66 and !FreeTime 14-Dec-2002 => works
• CLib 5.68 and updated run image for !FreeTime (renamed to !RunImage) => works
• Any other combination => out by 1 hour

You’ll need to reboot between the above tests, since the CLib is a rather important component and should be loaded early in the boot sequence.

CLib 5.68 and your !RunImage file inserted into !FreeTime.
Same Runimage version as you pointed to before.
Run !FreeTime
Says – Time one second slow – and proceeds to reset the clock by minus one hour.
Re-run (3600 sec slow – clock adjusted)
But the clock stays one hour behind.
Using *RMRemove CLib
Load CLib566
Run your version- clock still stays one hour out.
Run old version – clock now resets ok.

Says – Time one second slow – and proceeds to reset the clock by minus one hour.

OK, I probably missed something (I just did a search & replace, no brain juice was used in the process). I’ll try to remember to look at it again…

Repeated attempts to run/update the clock – just says -
(clock is 3600 seconds slow – clock adjusted)
But clock still stays remains one hour slow GMT?

Running the 17Jun12 !RunImage FreeTime with RO 5.19 19Jun12 produces the same effect as RO4.02.
First run – says clock is a few seconds slow – adjusting.
Puts clock one hour back.
Run again says 3600sec out – adjusting.
Run again says 3600sec out – adjusting etc
Clock still stays one hour out.
SharedCLib 5.69 11Jun12

Ok tried this and get the same issue.

Sprows updated RunImage in !Freetime,SharedCLib 5.69, latest ROM and HardDisc images dated 25th June.

Manually set clock back 2 minutes , run Freetime and it says Clock running xxx , accept changes and it puts time back one hour.
Run !FreeTime again and it says 3600sec out – adjusting and click on it but clock says the same 1 hr out.
Run again but FreeTime box flicks on screen and seems to disappear though I notice a slight impression in the far lefthand bottom part of the screen so Alt/Break and FreeTime appears in the list of tasks running. So is the subsequent corrections doing something silly with the positioning of the event notification box?
Tried it with the origonal !Runimage and that stays in the centre of the screen but accepting the change , 3600 secs,out, still leaves the system time 1hr out.

Hope this helps.

Doug

5.19 19Jun12 produces the same effect as RO4.02

I’ve not looked at this yet, other than remembering to check out the configuration half of !FreeTime. I’ll post here when there’s another run image to try.