From: JD on
Many thanks to you and Paul. I will have to learn how to access the BIOS and
make the required changes. I'm a little apprehensive about it, but if it has
to be done...
Jim
"Richard Urban" <richardurbanREMOVETHIS(a)hotmail.com> wrote in message
news:uc%23a%23nDYKHA.4068(a)TK2MSFTNGP06.phx.gbl...
> Your bios was reset due to a failed mother board battery. Now you have to
> replace the battery and set the bios to what YOU feel it should be.
> Apparently the default setting allows for a floppy drive, which you don't
> use. There may be other settings that have to be changed to your liking.
>
> --
>
> Richard Urban
> Microsoft MVP
> Windows Desktop Experience & Security
>
>
> "JD" <erehwon(a)example.com> wrote in message
> news:eyVk9hCYKHA.4452(a)TK2MSFTNGP04.phx.gbl...
>>I appreciate your extensive and thoughtful reply. However, to quote Casca,
>>it was "Greek to me." I've never fooled with the BIOS, so I have no idea
>>how to "load setup defaults in the BIOS."
>> My instincts tell me that if I check "Do not use this device" in Device
>> Manager, then the "resources" assigned to it will be regained, and no
>> harm done.
>> As for the system battery, it--and the computer--is six years old. I've
>> never thought about the prospect of having to replace it, but I know that
>> batteries don't last forever.
>> "Paul" <nospam(a)needed.com> wrote in message news:hd5cru$68p$1(a)aioe.org...
>>> JD wrote:
>>>> When I noticed that my system clock had been reset to Jan. 1, 2002, I
>>>> corrected it manually, and that allowed my A-V "license" to be
>>>> validated.
>>>> However, to my surprise, I had to reinstall the audio drivers from the
>>>> CD.
>>>> But My Computer now shows the presence of a floppy drive (A). This
>>>> machine has never had a floppy drive. Hardware Manager shows both a
>>>> floppy drive and floppy disk controller installed and "working
>>>> properly."
>>>> Should I use the Hardware Manager to "remove" the floppy drive--and
>>>> floppy disk controllers?
>>>> Or just leave well enough alone. Everything else seems to be working OK
>>>> now.
>>>
>>> 1) Verify the CMOS battery is still working. Usually that
>>> is a CR2032 in a socket. Check with a multimeter, that it
>>> measures 3.0V or a bit more. You can pick up a ground, on
>>> any shiny metal or an I/O screw on the back I/O plate.
>>> You don't have to pull the battery to measure it.
>>> If the battery reads below 2.4V, that is not sufficient
>>> to power the CMOS RAM when the ATX power supply is switched
>>> off at the back or unplugged (or power failure).
>>>
>>> Your power fail symptoms tell me the battery is flat,
>>> but you can verify with the multimeter before tearing
>>> anything apart.
>>>
>>> 2) For the floppy, try a load setup defaults in the BIOS,
>>> save and exit.
>>>
>>> My guess would be, the SuperI/O chip has a floppy interface,
>>> and normally the BIOS would be setting a bit in the chip
>>> after power up, to make it look like no floppy is present.
>>> On modern systems, they may continue to use legacy rich
>>> chips. Then, to make it look like most of that is
>>> missing, they disable the devices in the SuperI/O during
>>> POST. A SuperI/O might have eight legacy devices, and
>>> it is likely each one has an enable/disable, to suit
>>> situations where connectors have not been connected
>>> to the interfaces in question. So the fact that yours
>>> has become visible, might be corrected by a power cycle and
>>> POST sequence. Or by a load setup defaults.
>>>
>>> I think I would fix the CMOS battery first, before
>>> working on the floppy issue.
>>>
>>> Paul
>>
>>
>