Path: utzoo!mnetor!uunet!oddjob!hao!ames!ucbcad!ucbvax!cartan!brahms.Berkeley.EDU!cooper
From: cooper@brahms.Berkeley.EDU (Duane A. Cooper)
Newsgroups: comp.sys.att
Subject: Re: AT&T 6300+ clock... slow
Message-ID: <1482@cartan.Berkeley.EDU>
Date: 2 Jan 88 19:32:49 GMT
References: <6393@ncoast.UUCP>
Sender: nobody@cartan.Berkeley.EDU
Reply-To: cooper@brahms.Berkeley.EDU (Duane A. Cooper)
Distribution: comp
Organization: Math Dept. UCB
Lines: 35
Keywords: AT&T6300+ slow clock
Summary: mine, too!

In article <6393@ncoast.UUCP> simpsong@ncoast.UUCP writes:
>
>Hello, a friend of mine bought an AT&T 6300+ from a local
>Sears Business Center recently. The clock is slow... I don't
>know how much, but significantly. He has taken it back to Sears,
>and each time, they replace the entire motherboard, and give it
>back to him... It still doesn't work... (they've supposedly replaced
>it 3 times now...)
>
>Has anybody every heard of this problem? He's using AT&T Dos 3.2...
>perhaps the problem is software related?
>

I have no solution, but the problem sounds like mine, which I can state
in more detail:

My clock keeps EXcellent time when the system (6300+) is off.  E.g., I set
the time before I left for Xmas (9 days), and when I returned, the time
was still correct.  So the battery does not seem to be a problem.

When the system is ON, though, the MS-DOS timekeeper loses time.
For instance, I set the time just two hours ago, and now the DOS clock is
32 minutes slow while the UNIX time is correct.  However, were I to reboot
the system right now, BOTH clocks would come back 32 minutes slow.

I, too, suspect a software poblem.  The DOS clock is always wrong in
increments of minutes.  That is, when run simultaneously, the MS-DOS "time"
command and the UNIX "date" command give the same number of seconds,
differing in the minutes (and perhaps hours) columns.

Help!

				--d.c.
				[cooper@brahms.berkeley.edu]
				[ucbvax!brahms!cooper]