Article View: comp.periphs
Article #3110Re: CMOS mismatch 486 system oddity
From: David Longley
Date: Sun, 28 Jun 1998 00:00
Date: Sun, 28 Jun 1998 00:00
51 lines
2756 bytes
2756 bytes
PROBLEM 1 --------- I have a strange problem with a 486 PCI board. 1.2GB hard disk 1.44MB floppy 16MB RAM PCI board with 256K cache and intel DX100 BOARD uses um 8663, 85c496, 85c497 and has on board IO. On power up, it behaves as if it has lost CMOS settings. In fact it *has* lost its CMOS settings. But I have replaced the onboard battery - and THAT made no difference. So I purchased an external lithium battery and plugged that into the ext battery backup pins. Makes no difference, as soon as thr PC is turned off, I get a scan for the hard disk type (which it finds) even though I'd entered the correct parameters into SETUP. I get a message of a CMOS corrupt, loading defaults. But, the time and date are NOT lost. So, it seems it's NOT the battery per se. So what can it be? The board worked fine for a year, then ws kept aside for a couple of months, then installed in a new machine with same CPU and RAM. What was new was soundcard, video card and 1.2GB hard disk and CD ROM. I haven't disconnected the hard disk and floppy yet, but will do just to make sure they are not providing wrong info. 2. Problem Two -------------- System reboots intermittently from about 20 mins after power on. Thought it was the power supply originally. Discounted that after swapping the case today. So it looks like its the 2 x 8MB EDO RAM, cache (COAST) or the Motherboard or CPU. ANy suggestions? -- David Longley (check end reply line #) Longley Consulting London, UK Behaviour Assessment & Profiling Technology, Research, Data Analysis and Training Services, Small IT Systems http://www.longley.demon.co.uk
Technical Details
Message-ID:
<899041024snz@longley.demon.co.uk>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<898983333snz@longley.demon.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10a731,bc55438b0bc3edbe,start X-Google-Attributes: gid10a731,public X-Google-Thread: 10c6a1,bc55438b0bc3edbe,start X-Google-Attributes: gid10c6a1,public X-Google-Thread: 11656c,bc55438b0bc3edbe,start X-Google-Attributes: gid11656c,public X-Google-Thread: fde4f,bc55438b0bc3edbe,start X-Google-Attributes: gidfde4f,public From: David@longley.demon.co.uk (David Longley) Subject: Re: CMOS mismatch 486 system oddity Date: 1998/06/28 Message-ID: <899041024snz@longley.demon.co.uk> X-Deja-AN: 366818435 References: <898983333snz@longley.demon.co.uk> X-Complaints-To: abuse@demon.net X-Mail2News-Path: news.demon.net!longley.demon.co.uk X-Trace: mail2news.demon.co.uk 899042632 mail2news:19521 mail2news mail2news.demon.co.uk Organization: Relational Technology Reply-To: David@longley.demon.co.uk# Newsgroups: comp.periphs,Intel.motherboards,Intel.other_components.pci_chipsets,intel.motherboards.other