CompuServe Thread

You already heard gripes about the real time clock of Timesaver. There are already 2 programs in the DL to try and remedy that, but there is no remedy. Since there is no interaction from the Amiga the Tsaver is playing the cards. The problem is that the Timesaver sends a date command after a certain delay since you re-boot. If you were too ssllooww to put your disk in, the date will go to the bit bucket. Of course you always have the choice to use a 2 keystroke command to input the date in the system but this will at the least, require a CLI already open and you can never get it accurate to the second. But I don't see why you have to spend $80 for something you can do for free by typing the date or even have your startup query you for that. I don't want to go too much into this but the auto-date can also cause a lot of problems with auto-boot commercial programs. Since I am talking about Real time Clocks, let me say something about their accuracy of the 3 (4, I am still waiting on my 68881/clock card for my starboard) that I have. These figures are from data books of the clock chips: TimeSaver: 58321-B 130 sec/month (50ppm part of OKI 58321 clock with crystal) Insider : DS1216 60 sec/month (25ppm Dallas Semiconductor SmartWatch) A-Time : 58321-AA 26 sec/month (10ppm part of OKI 58321 clock with crystal) ** the above values are + or -. These are all pre-manufactured parts from 3rd party companies. That's the only reason why I use my A-Time as my clock, cause is the most accurate. For the 9 months that I had it it has lost no more than 4 seconds. The first clock that I got for the insider had problems but Michigan software exchanged it for another one which was not as accurate as the A-Time. Timesaver on the other hand is never accurate cause you never know when it will execute. <Continued….3 of 4>