Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!rutgers!bellcore!att!cbnewsl!clyde!feg
From: feg@clyde.ATT.COM (Forrest Gehrke,2C-119,7239,ATTBL)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Leading Edge Clock Problem
Keywords: Leading Edge Clock
Message-ID: <5069@cbnewsl.ATT.COM>
Date: 11 Apr 90 15:29:17 GMT
References: <3822.261de7ec@vax5.cit.cornell.edu> <1990Apr8.222651.21046@hellgate.utah.edu>
Sender: nntp@cbnewsl.ATT.COM
Reply-To: feg@clyde.ATT.COM
Distribution: comp
Organization: AT&T Bell Laboratories
Lines: 27

In article <1990Apr8.222651.21046@hellgate.utah.edu>, u-dmfloy%peruvian.utah.edu@cs.utah.edu (Daniel M Floyd) writes:
> On the question of Leading Edge Clocks:
> 
> I had the same problem with my Leading Edge PC when I upgraded
> the DOS for the LE DOS to a generic.  In my machine (which is not
> a model D like the others) LE did something to the DOS to make it
> 
> In order to combat the problem, I wrote my own program that I placed in
> the autoexec.bat file.  If the LE model D has the same (read compatible)
> clock as the older LE PC (an even money bet) you just need that type
> of program.
> 
> Dan





The prospects for the Leading Edge Model M (the earlier model) and
the Model D being the same are dim.  M stood for Mitsubishi and
the D for a Korean manufacturer Daiewo.

BTW if you wrote a program which fixed the problem with the Model
M, watch out on May 31.  That real time clock thinks that May
has only 30 days (the fix was in the L.E. dos).

Forrest Gehrke feg@clyde.ATT.COM