Path: utzoo!attcan!uunet!cbmvax!heimat!sneakers
From: sneakers@heimat.UUCP (Dan "Sneakers" Schein)
Newsgroups: comp.sys.amiga
Subject: Re: Clock problem
Message-ID: <5972.AA5972@heimat>
Date: 22 Jan 89 04:18:29 GMT
Followup-To: comp.sys.amiga
Organization: Sneakers Computing
Lines: 30

In Message <463@csd4.milw.wisc.edu>, duc@csd4.milw.wisc.edu (Duc Minh Tran) writes:

>[ What are these line eaters I keep reading about? ]
>
  Something that has not existed for years, yet people keep feeding them.

>Anyone out there with a Michigan Software Insider?  The clock on mine
>cannot seem to store the correct date; it always runs one day or 24hrs
>late.  Here is how I set the Insiders clock:
>	1) Use the Date command to set the Amiga's current date & time.
>	2) Use RTClock -W to write the previous info to the Insider clock. 
>When I use RTClock -R (read the date & time) off of the Insider, the
>info would be correct.  Now if I re-boot and then type RTClock -R again
>the date and time displayed would be 24hrs late.  I (going for a long shot)
>even used a clock virus dectector but Amiga does not recognize the Insiders
>clock.  I would appreciate any suggestions on a cure.
>
  I remember seeing messages about this on a commercial network. Turns out
  there is a bug (?) in the INSIDER clock program. A fixed version has been
  released (I know its on PLINK & BERKS AMIGA anyway).

  Sneakers

--
Dan "Sneakers" Schein          {pyramid|rutgers|uunet}!cbmvax!heimat!sneakers
Sneakers Computing
2455 McKinley Ave.                     Of course heimat is an Amiga.
West Lawn, PA 19609           Doesn't everyone run UUCP & UseNet on an Amiga?

   Call: BERKS AMIGA BBS - 60+ Megs - 24 Hrs - 12/2400 Baud - 215/678-7691