Clock/Timezone Settings

[gerograph]

Clock is always two hours behind, once I booted into MintPPC before. Seems MintPPC overwrites Clocksettings done by OS4.1. Any Solutions ? Also found new options in "TimeZone Prefs" but couldn't find documentation on that. Maybe correct settings here will lead to correct clock settings ?

regards gerograph

[nbache]

Clock is always two hours behind, once I booted into MintPPC before. Seems MintPPC overwrites Clocksettings done by OS4.1. Any Solutions ? Also found new options in "TimeZone Prefs" but couldn't find documentation on that. Maybe correct settings here will lead to correct clock settings ?

Linux expects the hardware clock to be running UTC and handles the conversion to the local time in software, while AmigaOS expects the hardware clock to be set to local time.

The only real solution is to fetch the time from an NTP server on each boot, like Linux (probably) already does.

In Time prefs on the second tab page, you can set the details. Once you have saved a setting that works (test it with the button), you can add the line "C:Date SERVER PREFS" to your S:Network-Startup after the existing lines. You can add "C:SetClock SAVE" after that if you want to save it to the hardware clock, but since you fetch it again next time you boot, you may want to omit that, which will keep Linux's time running in the hardware clock (if Linux saves it - I'm not sure whether it does).

Best regards,

Niels

[musa]

Linux expects the hardware clock to be running UTC and handles the conversion to the local time in software, while AmigaOS expects the hardware clock to be set to local time.

The only real solution is to fetch the time from an NTP server on each boot, like Linux (probably) already does.

In Time prefs on the second tab page, you can set the details. Once you have saved a setting that works (test it with the button), you can add the line "C:Date SERVER PREFS" to your S:Network-Startup after the existing lines. You can add "C:SetClock SAVE" after that if you want to save it to the hardware clock, but since you fetch it again next time you boot, you may want to omit that, which will keep Linux's time running in the hardware clock (if Linux saves it - I'm not sure whether it does).

Best regards,

Niels

Hello
None of the above work for me. I manually have to put my time each time the workbench starts. If I use the command line in network startup, loading of workbench will sometimes stops with the error of "this service is not available right now". Although the error does not come then I'm still 2 hours behind in time.
I think I've tried everything (maybe another time server?) but it should surely not be the great science to have the correct time.
Anyone have an idea for a solution
Thank you in advance

[gerograph]

It works perfect for me, now ! Thanx nBache.. This is with MintPPC after turnoff an booting into OS4. Doesn't even matter wether I login or turn the machine of right from login screen. This is my timeserver:

0.europe.pool.ntp.org

GMT Offsett is set to automatic on OS4. Keep in mind, that "C:Date SERVER PREFS" does not work, if network is not up (which might take longer, than loading Workbench...

[musa]

It works perfect for me, now ! Thanx nBache.. This is with MintPPC after turnoff an booting into OS4. Doesn't even matter wether I login or turn the machine of right from login screen. This is my timeserver:

0.europe.pool.ntp.org

GMT Offsett is set to automatic on OS4. Keep in mind, that "C:Date SERVER PREFS" does not work, if network is not up (which might take longer, than loading Workbench...

Hi
thanks for reply. I think I'll try your time server and see if it change anything

[nbache]

None of the above work for me. I manually have to put my time each time the workbench starts. If I use the command line in network startup, loading of workbench will sometimes stops with the error of "this service is not available right now".

That does sound like the time server you are trying is not working, or only partly working maybe with long response times. So trying another one would be a good idea.

Although the error does not come then I'm still 2 hours behind in time.
I think I've tried everything (maybe another time server?) but it should surely not be the great science to have the correct time.

No, it shouldn't, and in my experience normally isn't. The easiest way to get it working is to experiment with various servers in the Time prefs' second tab page. Set the various details, and try hitting the "Fetch time" (or whatever; "Hente klokkeslættet" in Danish) button. Then you will know at once whether it works. If not, try another one, or maybe check whether the port number etc. is set correctly. Once you have it working there, save the prefs, and it should also work from the command line as described above.

BTW, I use ntp.inet.tele.dk. It's my ISP's own time server (pool), but I don't think it is limited to TDC customers. You could try it. It is very reliable. Port number is set to standard (checkbox set).

Best regards,

Niels

[musa]

BTW, I use ntp.inet.tele.dk. It's my ISP's own time server (pool), but I don't think it is limited to TDC customers. You could try it. It is very reliable. Port number is set to standard (checkbox set).

Best regards,

Niels

Hello Niels
Tdc did it. Thank you
There was nothing wrong with the other servers, but my contact with them took too long. Therefore, there was no data been retrieved during startup.
Should not it be possible to put the hardware time 2 hours ahead and save it?
Well this seems to work so that everything is ok
Have a nice weekend (Vejrudsigten ser god ud)
Peter