Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!oliveb!pyramid!prls!philabs!pwa-b!mmintl!jeffm
From: jeffm@mmintl.UUCP
Newsgroups: comp.sys.att
Subject: PC-DOS 3.1 on 6300 and clock problems
Message-ID: <2181@mmintl.UUCP>
Date: Thu, 11-Jun-87 11:51:40 EDT
Article-I.D.: mmintl.2181
Posted: Thu Jun 11 11:51:40 1987
Date-Received: Tue, 16-Jun-87 00:50:00 EDT
Reply-To: jeffm@mmintl.UUCP (Jeffrey Miller)
Organization: Multimate International, E. Hartford, CT.
Lines: 24
Keywords: 6300 clock, PC-DOS 3.1

*
Please excuse me.  I stated in an earlier posting that using PC-DOS 3.1 on
my 6300, as long as I had the 3Com ethernet driver enet.sys loaded, my
clock worked.  That was wrong.  It turns out that I've been setting the
time from the network ALL THIS TIME!!!!!  I can't believe it.  I'm so
disappointed.  But I have modified for Lattice the WRATTCL.C and RDATTCL.C
programs posted earlier written by Bernie Roehl.  They work.  So now
when I boot RDATTCL.EXE runs and reads the hardware clock and sets the
DOS time.  The hardware clock was set previously with WRATTCL.EXE.  I
recommend these programs.

Sorry about that.

Jeff

* Jeff Miller                                                              *
* Multimate International, an Ashton-Tate Co.                              *
* 52 Oakland Avenue,  East Hartford, CT  06108-9911                        *
* (203) 522-2116 x257  UUCP: ...!seismo!utah-cs!utah-gr!pwa-b!mmintl!jeffm *
-- 
* Jeff Miller                                                              *
* Multimate International, an Ashton-Tate Co.                              *
* 52 Oakland Avenue,  East Hartford, CT  06108-9911                        *
* (203) 522-2116 x257  UUCP: ...!seismo!utah-cs!utah-gr!pwa-b!mmintl!jeffm *