Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!sunybcs!uhura.cc.rochester.edu!rochester!cornell!vax8530!pv9y
From: pv9y@vax5.cit.cornell.edu (O)
Newsgroups: comp.sys.ibm.pc
Subject: Leading Edge Clock Problem
Message-ID: <3822.261de7ec@vax5.cit.cornell.edu>
Date: 7 Apr 90 17:15:24 GMT
Distribution: comp
Lines: 30


    Hi All,
       Here's an odd question.  An office I do some stuff for has two
    Leading Edge PCs (Model D).  BOth have real-time clocks.  Recently
    the hard drive on one died completely and I replaced it.  However,
    this machine was old enough that I used a DOS 3.3 that came with
    an Epson Equity II+ instead of the DOS 3.1 that was on the Leading
    Edge's dead hard disk.  Since that time the clock in the Leading
    Edge whose hard drive died won't keep the time through a cold
    boot.  I checked the CONFIG.SYS file on the other Leading Edge and
    that only has the usual files and buffers lines - so there's no
    clock driver in the config file.  It seems odd that the clock
    should stop at exactly the same time as the hard disk, so I'm
    prone to believe that there is a software answer.

       Assuming the version of DOS I installed is the reason for the
    clock to stop working, is there an easy way to install an older
    version of DOS over a newer one without re-formatting?  Can I just
    delete the COMMAND.COM and the two invisible files and replace
    them with the equivalent ones from the older DOS?

       Many thanks .... Adam



-- 
Adam C. Engst                                pv9y@vax5.cit.cornell.edu   
----------------------------------------------------------------------          
"I ain't worried and I ain't scurried and I'm having a good time"               
                                                           -Paul Simon