Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!seismo!mcnc!philabs!pwa-b!mmintl!jeffm
From: jeffm@mmintl.UUCP
Newsgroups: comp.sys.att
Subject: Re: 6300 Clock & PC-DOS 3.1
Message-ID: <1969@mmintl.UUCP>
Date: Tue, 3-Feb-87 14:32:18 EST
Article-I.D.: mmintl.1969
Posted: Tue Feb  3 14:32:18 1987
Date-Received: Mon, 9-Feb-87 03:26:46 EST
References: <254@rocksanne.UUCP> <967@ur-tut.UUCP>
Reply-To: jeffm@mmintl.UUCP (Jeffrey Miller)
Organization: Multimate International, E. Hartford, CT
Lines: 30



*
I too have noticed the 6300 clock problems with PCDOS 3.1 but only recently,
although I have been running it for almost 2 years.  I am on an ethernet
system here at work.  When I brought my machine home the other week I took
3Com's driver, enet.sys, out of config.sys.  Lo and behold, my clock stopped
working automatically.  When I brought the machine back to work and added
enet.sys back in, the clock started working again.  As long as enet.sys is
in there it works.  I'll be leaving it in there even after I retire this
machine! :-)   BTW, I have ROM version 1.21, but the same thing must have
been true with version 1.1 since the clock always worked fine then with PCDOS
3.1.  I also use an Adaptec 2070A controller w/ a Seagate ST238, but this
occurred when I had a WD1002S controlling a CMI 1/2 ht 20 Meg.  I don't
think the controller has any effect but I thought I'd mention it.  BTW BTW,
the Adaptec/Seagate combo is dynamite.

   Strange but true........

     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 *
        *************************************************
*