VOGONS


First post, by Syntho

User metadata
Rank Member
Rank
Member

I've got a late '96 to '97 BIOS from American Megatrends. The motherboard is an Aopen AP5VM. This BIOS has a GUI, which is a first for me (at least on an old PC). I'm having some issues with getting a new battery working in it. I put in a DS12887A mod and it tells me to enter BIOS setup. I go in and change things, but it won't let me change the date. And I mean, when I go to the numerical day, month and year, I keep hitting + and - as well as use my mouse to point and click and it won't change at all. It lets me change the time though.

So I save the settings and restart and it gives me "BIOS Checksum Bad" every time now. I thought my new battery holder wasn't soldered correctly so I resoldered it, but it's still the same. Then I upgraded the BIOS chip thinking my BIOS was bad, but that doesn't help either.

I'm not sure why it won't let me change the date. I've got a new battery mod on the way to me. Is there anything else I should check? I'm thinking I can't change the date because the battery mod isn't working correctly.

Reply 1 of 8, by rasz_pl

User metadata
Rank l33t
Rank
l33t
Syntho wrote on 2024-06-18, 01:16:

I put in a DS12887A mod

does the clock tick in the bios? what RTC chip was there before? most compatible repair is to file the original chip and solder battery holder with a diode directly to it

Reproductions
https://github.com/raszpl/FIC-486-GAC-2-Cache-Module for AT&T Globalyst
https://github.com/raszpl/386RC-16 memory board
RE
Zenith Data Systems (ZDS) ZBIOS 'MFM-300 Monitor'

Reply 3 of 8, by brian105

User metadata
Rank Member
Rank
Member

Easiest way to see if something is wrong is using the date command in DOS.

Presario 5284: K6-2+ 550 ACZ @ 600 2v, 256MB PC133, GeForce4 MX 440SE 64MB, MVP3, Maxtor SATA/150 PCI card, 16GB Sandisk U100 SATA SSD
2007 Desktop: Athlon 64 X2 6000+, Asus M2v-MX SE, Foxconn 7950GT 512mb, 4GB DDR2 800, Audigy 2 ZS, WinME/XP

Reply 4 of 8, by Syntho

User metadata
Rank Member
Rank
Member
brian105 wrote on 2024-06-18, 07:13:

Easiest way to see if something is wrong is using the date command in DOS.

Yeah but I can't get that far since it says I need to go into the BIOS to set it up first every time.

Reply 5 of 8, by jakethompson1

User metadata
Rank Oldbie
Rank
Oldbie
Syntho wrote on 2024-06-18, 18:34:
brian105 wrote on 2024-06-18, 07:13:

Easiest way to see if something is wrong is using the date command in DOS.

Yeah but I can't get that far since it says I need to go into the BIOS to set it up first every time.

Sometimes, if it does that to you, but then you exit BIOS setup without saving, it will go ahead and boot, albeit with the default settings (hopefully 1.44MB floppy at least)

Reply 6 of 8, by Syntho

User metadata
Rank Member
Rank
Member
jakethompson1 wrote on 2024-06-18, 18:44:
Syntho wrote on 2024-06-18, 18:34:
brian105 wrote on 2024-06-18, 07:13:

Easiest way to see if something is wrong is using the date command in DOS.

Yeah but I can't get that far since it says I need to go into the BIOS to set it up first every time.

Sometimes, if it does that to you, but then you exit BIOS setup without saving, it will go ahead and boot, albeit with the default settings (hopefully 1.44MB floppy at least)

Actually, yeah, this seems to work. It's asking for a floppy or HD or just something to boot from. I'm thinking the battery holder is what's causing this so I've got a new one on the way. Will update once I get it.

Reply 8 of 8, by analog_programmer

User metadata
Rank Oldbie
Rank
Oldbie

Yes, usually this happens when battery in RTC module is depleted.

from СМ630 to Ryzen gen. 3
engineer's five pennies: this world goes south since everything's run by financiers and economists
this isn't voice chat, yet some people, overusing online communications, "talk" and "hear voices"