David Guntner wrote: > > Jonathan Dlouhy grabbed a keyboard and wrote: > > > > Dave, it definetly sounds like a hardware problem. It sounds like > > something gets heated up after 24 hours then fails. It could be a one > > of several things. Don't flame me for this, but, have you tried a > > different OS to see if it does the same thing? > > That would require an awful *lot* of work to install something else, which > is not exactly something I'm too keen on right now... :-) However, as it > *has* been runing Mandrake reliably for many months (close to a year) now, > I don't think it's an OS thing. Not a flame, just some info. :-) > > > If so, then it's got to be a hardware problem. I would investigate the > > RAM, then the motherboard. I don't know how much ram you have, but if > > you could beg, borrow or steal some other ram, swap yours out then > > run it for a couple of days. If it doesn't lock up, then I guess we > > know the problem. If it still does it it's time to look at the mb. > > After that I'm out of ideas. > > I've got 256M of RAM in the machine, to answer your (implied) question. I > don't know anyone with memory that I could borrow. :-) As I mentioned in > my earlier message, I've run Memtest-86 (you boot it up from a diskette) on > this machine, and it doesn't find any problems with memory (when I was > experiencing a problem where the machine started spontaneously rebooting > from time to time for no apparent reason, Memtest-86 identified bad memory > and when I replaced that SIMM module, the reboots stopped - so I trust this > utility). > > Thanks for the reply! > > --Dave Another utility you might try in order to test the system is the burnin program. There is a pc system exercisr and diagnostic tool, burnin43.zip. It's old but works.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
