VOGONS


First post, by multiplebaboons

User metadata
Rank Member
Rank
Member

Hi all,

I have here a circa 1996-97 beige AOpen-branded box (likely P1 @ 233MHz, 64MB RAM) that was given to me by a friend 20+ years ago. It collected dust for most of this time and when it did work, I recall that I had win95 running with the following problem: it would freeze (static image to monitor) until hard reboot. Back then, I was pretty sure it was a memory problem.

Long story short, I would like to resurrect this bastard. On the first start, it would not post, so I reconnected a few IDE cables that I found disconnected and then it did output a low CMOS battery to an old LCD monitor. After that, back to no output, but it tries to speak to me (recording attached). Two things: 1) CMOS battery not easy to rectify right away, because this is the infamous Dallas DS12887 chip; 2) I have no keyboard connected (still waiting for the PS/2 to DIN5 adapter).

Any idea what those beeps are?

Thanks!

Reply 1 of 8, by jakethompson1

User metadata
Rank l33t
Rank
l33t

Loose or failing video card

Reply 2 of 8, by multiplebaboons

User metadata
Rank Member
Rank
Member

You're right: i put the card in another slot and it did output the CMOS battery message again. But only once -- after switching power off back to no signal and no beeps either. I will wait for that keyboard adapter, I guess.
Thanks!

Reply 3 of 8, by quigonhu

User metadata
Rank Newbie
Rank
Newbie

Back to the colledge, I was taught that different BIOS beep code could have different meaning. During the following decades, I learned sometime different BIOS supplier defines different meaning even the beep sounds the same.

Then I post this address, hope that will help you. Good luck.
https://www.computerhope.com/beep.htm

Reply 4 of 8, by multiplebaboons

User metadata
Rank Member
Rank
Member

Well, the first reply was correct off the bat, but thanks for what may be handy later.

After reseating one of the ram sticks, BIOS is posting consistently, so I guess things are starting to clear up and it actually looks like I had more memory than I thought. While I wait for that keyboard adapter, what does it want in terms of display settings (Acer AL1716)?

Reply 5 of 8, by jakethompson1

User metadata
Rank l33t
Rank
l33t

Not sure what you are getting at. With traditional VGA modes like 720x400 text mode, 320x200 graphics mode, and 640x480 graphics mode, it's the monitor's job to just deal with it, there is generally no ability to custom-tune things in software. Maybe with a card-specific program in DOS, but definitely not in the BIOS screen.

You should have an autoadjust feature on the monitor that will help align the text in-bounds. Sometimes if you go into a screen with a background color first (like bios setup or MSD) and then do it, it seems to be more accurate.

Reply 6 of 8, by multiplebaboons

User metadata
Rank Member
Rank
Member
jakethompson1 wrote on 2025-05-06, 14:08:

Not sure what you are getting at. With traditional VGA modes like 720x400 text mode, 320x200 graphics mode, and 640x480 graphics mode, it's the monitor's job to just deal with it, there is generally no ability to custom-tune things in software. Maybe with a card-specific program in DOS, but definitely not in the BIOS screen.

You should have an autoadjust feature on the monitor that will help align the text in-bounds. Sometimes if you go into a screen with a background color first (like bios setup or MSD) and then do it, it seems to be more accurate.

I think I overthought this. Indeed, one of the indistinct buttons on the monitor is the autoadjust, which fixes the shift. On the BIOS side, the monitor related options are simply VGA/CGA, etc.

Speaking of the BIOS, even after adjusting time, it does not feel like booting. The only option is F1 to enter BIOS again.

Reply 7 of 8, by jakethompson1

User metadata
Rank l33t
Rank
l33t
multiplebaboons wrote on 2025-05-06, 18:32:

Speaking of the BIOS, even after adjusting time, it does not feel like booting. The only option is F1 to enter BIOS again.

That is because of the dead battery. You may be able to "exit without saving" and at least boot from a floppy and possibly CD-ROM, though if the hard drive doesn't autodetect or its settings get wiped from CMOS because of the dead battery, you won't be able to access C: unless you boot Linux (or anything else that doesn't care if the HDD is missing from CMOS).

Reply 8 of 8, by multiplebaboons

User metadata
Rank Member
Rank
Member
jakethompson1 wrote on 2025-05-06, 19:50:

That is because of the dead battery. You may be able to "exit without saving" and at least boot from a floppy and possibly CD-ROM, though if the hard drive doesn't autodetect or its settings get wiped from CMOS because of the dead battery, you won't be able to access C: unless you boot Linux (or anything else that doesn't care if the HDD is missing from CMOS).

I am guessing the only proper solution here is to remove the mb and replace that clock chip. I wish that thing was socketed, damnit.