Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!olivea!mintaka!mit-eddie!uw-beaver!sumax!polari!dlh
From: dlh@polari.UUCP (d h)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Problem w/386 - is slow
Message-ID: <2724@polari.UUCP>
Date: 13 Nov 90 08:29:56 GMT
References: <90315.214214MHS108@psuvm.psu.edu>
Organization: Seattle Online Public Unix (206) 328-4944
Lines: 18

In article <90315.214214MHS108@psuvm.psu.edu> MHS108@psuvm.psu.edu (Mark Solsman) writes:
>Intresting Problem:
>
> One day I turned on my 386/25, the usual memory check clicks 3 times a second
>while it displays the memory count, but today it clicked at the rate of 1/sec.






I had a similar problem with my 25Mhz 386AT one day. The problem turned out to
be that something had corrupted my CMOS settings.  What I did was go into the
CMOS monitor program and play with the clock settings. At least on my machine, 
you are allowed to select sys clock, sysclock/2, or bus clock to run the bus and
memory.

You might try it.