From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci) Subject: Re: CMOS getting mangled ? Date: 12 Jan 1993 12:41:29 GMT
In article <1993Jan12.032455.27285@nwnexus.WA.COM> danubius@halcyon.com (Joseph R. Pannon) writes:
>In article <1993Jan11.151851.23665@athena.mit.edu> acook@athena.mit.edu (Andrew R Cook) writes:
>>I've been running SLS v.98pl5 for a while, and (almost) everything is
>>peachy-keen, except for the fact that Linux has the annoying habbit of
>>thrashing my CMOS for time to time. It seems like every other time the
>>time and date get fried, and occasionally the disk info is lost. Very
>>strange. I've never had this problem running any dos stuff. It looks
>>like the clock is just reset, it comes up jan 1, 1980.
>
>Hmmm ... That's interesting, because something similar is happening to
>my Gateway 486/33C, too, but up to now I never linked it to linux.
>(... and it still may have nothing to do with it until I hear about more
>similar coincidences).
>
>Lately I have noticed some erratic behavior with my A: drive while in
>DOS 5. I would try to format a 1.2Mb floppy in it with the usual
>command lines options (/u /f:1.2) and it would be refused with a message
>saying something about those parameters not matching the drive. This is
>new, because those params always used to work before (meaning
>unconditional formatting of a 1.2 Mb floppy). What I discovered,
>however, that all I needed to fix this problem was to make a cold boot
>with the reset button.
>
>Reading your post makes me think of the circumstances when these things
>were happening and it looks like it might have been when I used the floppy
>drive in linux and later rebooted (via warm boot) into DOS-5 to format
>some floppy. I thought that recent erratic behavior may have been due
>to my drive slowly going south, but perhaps there is something else to
>this. (I hope I'm not going to be eaten alive for this comment again!
>;-) Maybe somebody more knowledgeable can look into it.
>I am going to watch this better from now on, because it may have been
>happening when I tried to format after a RAWRITE.
>
>Joe Pannon
I have seen postings regarding this for some time, always linked to
486 motherboards. Seems to be related to rebooting system. I always
do "shutdown now", then hit reset button to reboot. Have NEVER had a
problem. There have been virtually no postings on this for a few weeks,
but I guess there is still a problem.
-- =========================================================================== phil perucci | "Any opinions expressed are solely my own views and ssb1pzp@digex.com | do not reflect the position of any organization" ===========================================================================