LC.YRS@forsythe.stanford.edu (Richard Stanton) (01/06/90)
The date on my system (Epson Equity II+, MS-DOS 3.3) seems to be doing some funny things. Yesterday, I had to change it because it had lost a day. This morning, I noticed it claimed the date was November 29, 1989. The time is correct, however. Does anyone know a) what the problem is b) what a solution might be? Thanks Richard Stanton pstanton@gsb-what.stanford.edu
poffen@molehill (Russ Poffenberger) (01/07/90)
In article <6902@lindy.Stanford.EDU> LC.YRS@forsythe.stanford.edu (Richard Stanton) writes: >The date on my system (Epson Equity II+, MS-DOS 3.3) seems to be >doing some funny things. Yesterday, I had to change it because it >had lost a day. This morning, I noticed it claimed the date was >November 29, 1989. The time is correct, however. > >Does anyone know > > a) what the problem is > > b) what a solution might be? > >Thanks > I would say that your battery for your real-time clock needs replacing. Check with an Epson Dealer for a replacement. Russ Poffenberger DOMAIN: poffen@sj.ate.slb.com Schlumberger Technologies UUCP: {uunet,decwrl,amdahl}!sjsca4!poffen 1601 Technology Drive CIS: 72401,276 San Jose, Ca. 95110 (408)437-5254
pipkins@qmsseq.imagen.com (Jeff Pipkins) (01/09/90)
In article <6902@lindy.Stanford.EDU> LC.YRS@forsythe.stanford.edu (Richard Stanton) writes: >The date on my system (Epson Equity II+, MS-DOS 3.3) seems to be >doing some funny things. Yesterday, I had to change it because it >had lost a day. This morning, I noticed it claimed the date was >November 29, 1989. The time is correct, however. Two caveats to consider: 1. If you use the DATE command to set the date (or TIME to set time), it will NOT set the date and time in your CMOS clock chip. The next time you power-on, the date and time will be set from the chip. To set it permenantly you will probably have to run the SETUP utility. 2. Although the time is updated constantly, the date is only updated when it is _read_. So if you leave your machine on overnight or more, the date will not have been updated. Some versions of some BIOSes do not have this bug. Good luck.