Not one to promote my own software , but I wrote yFacts for this issue. Just stick it in WBStartUp and forget about it (it takes the server config out of Time Prefs.. not sure what it does if that is empty, can't remember).
Well as per usual there is something wrong with AmigaOS. I already have a time server specified in Time prefs, clearly its trying to grab the time before the tcp/ip stack is ready and doesn't just auto-retry moments later. Yfacts would be unnecessary if stuff just worked as advertised.
@all hohoho, butt of some jokes tonight it would seem, how very drool.
Even if you have a time server specified it doesn't background check/correct the time. That's why you need the line in network-startup (for a single check on boot, after the TCP/IP stack starts up) or yFacts (which runs more like the time service you get on Windows or Linux, and checks in the background).
As you say, it's something which should be part of the OS.
Might clock has read the year as 2089 and 1989 in the past so yeah the battery definitely needs replacing. However that's a lot (pardon the pun) of time and effort to get it repaired when software will suffice. Thats my only concern. If I ever go to LAG again perhaps someone will gladly fix it for me!
Replacing the battery is something that takes about one minute. Removing the case screws takes most of the time. But replacing a CR2032 battery is really no rocket science.
While we are at it and now that the vanishing button images issue from ticket #133 is fixed, would you please confirm whether ticket #132 is still valid? I asked you several times by now to provide a working (on AmigaOS3) Listtree demo, but all my recent requests went by unanswered/unnoticed and so far you uploaded non-working versions only.
#132 Yes this is still valid, its a separate issue unrelated to #133. All my ListTrees (even Odyssey, see Bookmark amanager) are missing the square -/+ symbol/con next to the Nodes perhaps other users here on Amigans can check for themselves and report back their findings.
Yes, regarding #133, its not that it has gone unnoticed, there wasn't much to say on it- I checked the code last night and couldn't find anything wrong with brush 21. I will recompile in its current state (maybe I missed something) and send you it in time for the weekend.