Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!mips!zaphod.mps.ohio-state.edu!rpi!hydrox From: hydrox@itsgw.rpi.edu (Michael A. Hendrix) Newsgroups: comp.sys.ibm.pc Subject: Re: Leading Edge Clock Problem Keywords: Leading Edge Clock Message-ID: Date: 9 Apr 90 11:50:20 GMT References: <3822.261de7ec@vax5.cit.cornell.edu> <1990Apr9.021431.5531@eng.umd.edu> <1990Apr8.222651.21046@hellgate.utah.edu> Distribution: comp Organization: Rensselaer Polytechnic Institute, Troy NY Lines: 20 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 >read the clock - no device driver, no autoexec. LE DOS does the clock. I also had owned an older Leading Edge. I discovered that they located the clock in a different place than where IBM had put theirs, so the only way to read and set the clock with the correct time was to use Leading Edge's version of DOS, which was modified to read/set the clock. When you upgrade to a different DOS you will need a device driver to be able to access the clock. -- --------------------------------------------------------------------------- The Dragon's Lair BBS | hydrox@pawl.rpi.edu 300/1200/2400 N81 8PM - 10AM Daily | Michael_Hendrix@mts.rpi.edu (413) 743-1828 Adams, MA 01220 | BITNET: F7TZ@RPITSMTS