Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!cbmvax!schein From: schein@cbmvax.UUCP (Dan Schein MAGAZINES) Newsgroups: comp.sys.amiga Subject: Re: Problem with JTIME Message-ID: <2292@cbmvax.UUCP> Date: Thu, 3-Sep-87 08:54:13 EDT Article-I.D.: cbmvax.2292 Posted: Thu Sep 3 08:54:13 1987 Date-Received: Sat, 5-Sep-87 11:04:19 EDT References: <30@rpicsb8> <2290@cbmvax.UUCP> Reply-To: schein@cbmvax.UUCP (Dan Schein MAGAZINES) Distribution: na Organization: Commodore Technology, West Chester, PA Lines: 27 Keywords: JTIME, clock/calendars, hardware In article <2290@cbmvax.UUCP> mikec@cbmvax.UUCP (Mike Colligon QA) writes: > >I'm sorry I have no real solution for the problem. How about some input from >other TIC owners and JTIME builders? ^^^ ^^^^^ I have had a TIC since Winter CES (Jan of 87) and it has performed just fine on both of my A1000's, it has also worked fine on 2 A1000's w/Sidecar that I tried it with. I have since updated one of my A1000's with an "INSIDER" 1 Meg memory / battery clock - calander and that also keeps correct time. The TIC is still ticking (ha ha ha) away on my other A1000 just like new. > >-- >| Michael Colligon uucp: {ihnp4|seismo|caip}!cbmvax!mikec | -- +----------------------------------------------------------------------------+ | Commodore Business Machines | | 1200 Wilson Drive uucp: {ihnp4|seismo|caip}!cbmvax!schein | | West Chester, PA 19380 arpa: cbmvax!schein@seismo.css.GOV | | (215) 431-9100 x9542 or schein@cbmvax.UUCP@{seismo|harvard} | +----------------------------------------------------------------------------+ | All spelling mistakes are a result of my efforts to avoid education :-) | +----------------------------------------------------------------------------+ | Quote: Those who worked the hardest Gary Ward - Oklahoma State | | are the last to surrender baseball coach | +----------------------------------------------------------------------------+