Path: utzoo!attcan!uunet!lll-winken!ames!xanth!nic.MR.NET!umn-cs!mmm!schultz
From: schultz@mmm.UUCP (John C Schultz)
Newsgroups: comp.sys.nsc.32k
Subject: Re: Clock on ICM-3216
Summary: no problem here but using National V.2.2 port
Keywords: ICM3216 clock chip BSD
Message-ID: <1209@mmm.UUCP>
Date: 12 Jan 89 02:37:52 GMT
References: <493@hocpa.UUCP>
Reply-To: schultz@mmm.UUCP (John C Schultz)
Organization: 3M Company - ES&T; St. Paul, MN
Lines: 21

In article <493@hocpa.UUCP> rusty@hocpa.ATT.COM (91341-M.W.HADDOCK) writes:
>Happy New Year folks!
>
>Unfortunately, since the beginning of the new year, fe2o3 (my ICM3216) keeps
>reporting each minute (or there abouts) that the rtclock is off by 86400
>seconds +/- 1. This comes to be 1-day worth of seconds.  Naturally, I'm

Nope, I have not had this problem.  However I am (still) using the
V.2.2 National port.  

I don't think the battery is the problem since my board is a couple
years old (Rev A PROMS) too.

Of course bad batteries and/or a bug in the software is not unheard of
:-).


-- 
 john c. schultz   schultz@3M.Com   ..!uiucuxc!mmm!schultz  (612) 733-4047
           3M Center, Bldg 518-1-1, St. Paul, MN 55144-1000
  The opinions expressed herein are, as always, my own and not 3M's.