JohnPolka Posted May 1, 2019 Share Posted May 1, 2019 (edited) I recently contacted Jookie and Lotharek about a problem I'm having wiht my UltraSatan's battery backed real time clock (purchased from Lotharek). Jookie suggested I contact Lotharek. Lotharek said he never heard of this problem before. So, I thought I'd post it here: As I mentioned in another post, I have an UltraSatan running on an Atari 1040 STE (4 Megs, TOS 1.62). I purchased it used and the seller purchased it from Lotharek (it's the metal cased version). The US has version 1.20 firmware installed. It also has the PeraPutnik drivers. The seller never bothered to to try to set the battery backed real time clock chip (RTC). So, it's unknown if it ever worked correctly. I downloaded Jookie's clock utilities, but they do not set the date and time on the US. I also tried replacing the battery and tried it with the base firmware. I also tried the US on a stock Atari 520STFM. No luck. The date and time do appear to be working but can't be set. When I first ran the clock set program it said the date was was 2002-03-18. When I replaced the battery, it reset to 2001-01-01. I did not find anything on the Internet that said there is a known problem with my system configuration and the US. I do wonder if upgrading to TOS 2.06 could fix the problem. Does anyone have any ideas? I checked all over the Internet and did not find anyone else reporting the same issue. -JP Edited May 1, 2019 by JohnPolka Quote Link to comment Share on other sites More sharing options...
Wally1 Posted May 1, 2019 Share Posted May 1, 2019 there are two small files within I believe the ICD folder that comes with the Ultrasatan called something like GETCLK and SETCLK that work very nicely to set and install the time if you put the GETCLK file in an AUTO folder on the C: drive then the correct time will be loaded with every bootup provided you set it initially I did all this today myself Quote Link to comment Share on other sites More sharing options...
JohnPolka Posted May 2, 2019 Author Share Posted May 2, 2019 (edited) there are two small files within I believe the ICD folder that comes with the Ultrasatan called something like GETCLK and SETCLK that work very nicely to set and install the time if you put the GETCLK file in an AUTO folder on the C: drive then the correct time will be loaded with every bootup provided you set it initially I did all this today myself Yes, those are Jookie's clock utilities that I mentioned in my original post. They do not work for me. That is, SETCLK will not set the clock on my UltraSatan. What kind of ST and version of TOS are you running? -JP Edited May 2, 2019 by JohnPolka Quote Link to comment Share on other sites More sharing options...
Tillek Posted May 2, 2019 Share Posted May 2, 2019 Just out of curiosity, what did the utility do? Was there an error message? Did it just not work? Because.... I had a thought. What if the date format is causing an error since it is probably written for European date formats and you probably entered in a US one? You know, how they put the day before the month, because somehow that makes logical sense to nations that didn't fake footage of putting a man on the moon like we did)!!!!!! (Really though... nothing but love for our overseas brothers... just wondering if that might have been an issue... I know I've run into it on the A8 with versions of the SpartaDos time and date setting where sometimes, depending on the version and where it came from, wants the European date format). Quote Link to comment Share on other sites More sharing options...
JohnPolka Posted May 2, 2019 Author Share Posted May 2, 2019 Just out of curiosity, what did the utility do? Was there an error message? Did it just not work? Because.... I had a thought. What if the date format is causing an error since it is probably written for European date formats and you probably entered in a US one? You know, how they put the day before the month, because somehow that makes logical sense to nations that didn't fake footage of putting a man on the moon like we did)!!!!!! (Really though... nothing but love for our overseas brothers... just wondering if that might have been an issue... I know I've run into it on the A8 with versions of the SpartaDos time and date setting where sometimes, depending on the version and where it came from, wants the European date format). No error message. The date and time does not change. The utility has you enter the date/time in a specified format. I tried that format and a few others. No difference. -JP Quote Link to comment Share on other sites More sharing options...
Tillek Posted May 2, 2019 Share Posted May 2, 2019 No error message. The date and time does not change. The utility has you enter the date/time in a specified format. I tried that format and a few others. No difference. -JP Alas... just thought I'd make sure to eliminate the low hanging fruit. Quote Link to comment Share on other sites More sharing options...
ParanoidLittleMan Posted May 2, 2019 Share Posted May 2, 2019 I checked it today - did not use it, last time maybe some 6 years ago, because programming goes mostly with Steem Debugger, so I don't need real time on Atari really Jookie SW works, but I noticed 1 error with German 1.04 original: Time in TOS is 1 hour more than what is set - checked twice. With US 1.62i it is OK. Really strange. What could be problem by you, JohnPolka ? May be that there is some HW problem on your US only with RTC part. Really have no other idea. 1 Quote Link to comment Share on other sites More sharing options...
JohnPolka Posted May 2, 2019 Author Share Posted May 2, 2019 (edited) I checked it today - did not use it, last time maybe some 6 years ago, because programming goes mostly with Steem Debugger, so I don't need real time on Atari really Jookie SW works, but I noticed 1 error with German 1.04 original: Time in TOS is 1 hour more than what is set - checked twice. With US 1.62i it is OK. Really strange. What could be problem by you, JohnPolka ? May be that there is some HW problem on your US only with RTC part. Really have no other idea. I suspect this may be a hardware problem. What puzzled Lotharek was the fact that I could still read the time. If there was a problem with the chip, he suspected I wouldn't read any time (or I'd read a random/garbage time). The RTC is keeping time. I just can't set it (other than reset it to 2001-01-01 if I unplug the battery). I did find a message on atari-forum from someone who had a similar, but not exactly the same, problem. On the last two messages of the following link someone with a similar set up (1040 STE, 4MB, 1.62 TOS), mentioned a problem setting the date, but not the time. My problem is with both time and date. Regardless, it doesn't look like their problem was ever resolved either. However, they wondered if upgrading to TOS 2.06 may help. I suppose I could try posting a message there too. http://www.atari-forum.com/viewtopic.php?t=17742&start=50 -JP Edited May 2, 2019 by JohnPolka Quote Link to comment Share on other sites More sharing options...
Wally1 Posted May 2, 2019 Share Posted May 2, 2019 I'm using Atari 1040 ST with TOS 1.04. 1 Quote Link to comment Share on other sites More sharing options...
JohnPolka Posted June 13, 2019 Author Share Posted June 13, 2019 I did find a message on atari-forum from someone who had a similar, but not exactly the same, problem. On the last two messages of the following link someone with a similar set up (1040 STE, 4MB, 1.62 TOS), mentioned a problem setting the date, but not the time. My problem is with both time and date. Regardless, it doesn't look like their problem was ever resolved either. However, they wondered if upgrading to TOS 2.06 may help. I suppose I could try posting a message there too. http://www.atari-forum.com/viewtopic.php?t=17742&start=50 -JP Just an FYI - upgrading to TOS 2.06 didn't help. It's probably a defective US. -JP Quote Link to comment Share on other sites More sharing options...
Wrathchild Posted June 13, 2019 Share Posted June 13, 2019 (edited) can't find what RTC chip is used, but don't some have a write-protect pin. Perhaps that wasn't soldered properly? Edited June 13, 2019 by Wrathchild Quote Link to comment Share on other sites More sharing options...
JohnPolka Posted June 13, 2019 Author Share Posted June 13, 2019 can't find what RTC chip is used, but don't some have a write-protect pin. Perhaps that wasn't soldered properly? I'll double check tonight. However, according to a partial schematic that Lotharek sent me, it's a DS1307Z. -JP Quote Link to comment Share on other sites More sharing options...
JohnPolka Posted June 14, 2019 Author Share Posted June 14, 2019 I'll double check tonight. However, according to a partial schematic that Lotharek sent me, it's a DS1307Z. -JP I confirmed on the board that the RTC is a DS1307. I didn't see a 'Z' in the number. -JP Quote Link to comment Share on other sites More sharing options...
snarkdluG Posted June 14, 2019 Share Posted June 14, 2019 I confirmed on the board that the RTC is a DS1307. I didn't see a 'Z' in the number. -JP It' still a DS1307Z just marked on top as a DS1307: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.