Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!peruvian.utah.edu!u-dmfloy
From: u-dmfloy%peruvian.utah.edu@cs.utah.edu (Daniel M Floyd)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Leading Edge Clock Problem
Keywords: Leading Edge Clock
Message-ID: <1990Apr8.222651.21046@hellgate.utah.edu>
Date: 9 Apr 90 04:26:50 GMT
References: <3822.261de7ec@vax5.cit.cornell.edu> <1990Apr9.021431.5531@eng.umd.edu>
Distribution: comp
Organization: University of Utah CS Dept
Lines: 18

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
read the clock - no device driver, no autoexec.  LE DOS does the clock.
This may differ on a model D, as at least two other postings have
pointed out.  (I think I just offered contradictory opinion about
LE modifying DOS too.)

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
Dan Floyd
u-dmfloy@ug