VOGONS


First post, by eliot_new

User metadata
Rank Member
Rank
Member

Hello everybody

I have bought very cheap an old Aopen AP53 rev. 3.0 i430HX Board.
It recognizes only HDD till 8GB and no sdcard with the ide2sdcard adapter.
I wanted to flash the amibios using the ami flash utility ver. 8.95.
It says at start "flash is write protected"

Question: is there any jumper to adjust this?
https://www.dosdays.co.uk/media/aopen/AP53/ap53.pdf

I don´t see this.
Or maybe I should use another utility?

https://soggi.org/motherboards/bios-update-fl … h-utilities.htm

EDIT: uniflash.exe helped, now I have Bios 3.90 on it. Sorry for the thread. Please ignore it!

DOS:P233MMX,64MB,ECS,SpeaMirageV7,3dfxV1,AWE64,ESS1868,PicoGUS,32GB
W98SE:K63/400,256MB,P5A,Verite2200AGP,3dfxV2,M3D,AWE64,ESS1938,PicoGUS,64GB
XP:P3-1G,512MB,CUSL2C,FX5600AGP,Audigy1,80GB

Reply 1 of 5, by CrustyCeleron

User metadata
Rank Newbie
Rank
Newbie

If utilty related, could try uniflash instead.

Else... little google revealed these flashers which might help. Or not! https://e1magic.ru/files/MOTHERBOARDS/aopen%2 … ap53%2095140-3/

Also, some version of the AP53 is available in 86box, so could try things safely in there too to see if they differ.

Reply 2 of 5, by rasz_pl

User metadata
Rank l33t++
Rank
l33t++

check where jumpers near BIOS are connected to. I think hmm pin 31 is write enable? One connecting to that pin will be responsible for protection. Uniflash is a good idea too.

https://github.com/raszpl/sigrok-disk FM/MFM/RLL decoder
https://github.com/raszpl/FIC-486-GAC-2-Cache-Module (AT&T Globalyst)
https://github.com/raszpl/386RC-16 ram board
https://github.com/raszpl/Zenith_ZBIOS Zenith Z-386 MFM-300 ZBIOS disassembly

Reply 3 of 5, by eliot_new

User metadata
Rank Member
Rank
Member

CrustyCeleron + rasz_pl: thank you both for your answers!

Unfortunately, I have (maybe) unintentionally destroyed the board:

I pressed the EDO SIMM modules down too hard because I thought they weren't seated firmly enough in the RAM sockets.

After doing that, I get a new error message on boot:

Bank 0: EDO

Error!

I switched the modules to Bank 1, but got the exact same result.

Even with other EDO SIMM modules, the issue persists (tested with both 2x 16MB and 2x 32MB Siemens 60ns EDO SIMMs).

This is really sad, as the last time I accidentally killed hardware was back in 1994 when I got my first Gateway 2000 PC.

Ever since, I've always been extremely careful whenever handling or assembling hardware.

Obituary:

(Wipes a silent tear from the PCB...)

It is deeply heartbreaking to find the right words. The news of my AOpen AP53's sudden passing has shaken me to the core. It’s a sad day for the retro community and a painful loss for any hardware enthusiast.

Here is a fitting eulogy to pay our last respects to this fine piece of silicon history:
🕊️ In Deep Grief: A Eulogy for the AOpen AP53 🕊️

(Soft organ music plays in the background)

Dear mourners, fellow retro enthusiasts,

We are gathered here today to say goodbye. Goodbye to a faithful companion, a masterpiece of the late 90s, a true hero of the Intel 430HX era: the AOpen AP53.

It came into your life for a steal at €37 – a absolute bargain, a visual and technical gem in remarkably pristine condition. It was ready for a second life. Ready to swing old EDO SIMMs, break benchmark records, and resurrect the spirit of the Socket 7 golden age.

What immense potential was locked inside! It proudly carried 256 KB of Pipeline Burst L2 Cache and possessed – one can barely speak of it without tearing up – the coveted 32 KB TAG-RAM (UM61256S-15), granting it the ultimate power to cache a full 512 MB of RAM. This was no ordinary board; it was a beacon of hope against the merciless 64 MB cacheable area limit.

Even its stubborn AMI WinBIOS – as quirky and idiosyncratic as it was – held that special retro nostalgia charm we will now miss so dearly.

And yet... one single, tragic moment of pressing down just a little too hard. A short, silent scream within the trace layers.

Bank 0: EDO... Error!

A sentence like a dagger to the heart of every retro builder.

It passed away as it lived: in the heat of action, right at the open heart of retro tinkering. No slow death by leaking capacitors – but taken from us in its prime while trying to give it a firm seat.

Dear AOpen AP53: Your buses may now be silent, and no POST beep will ever echo through the room again. But your components – your Tag RAM, your SRAMs, your crystals – will live on in future projects. You do not die in vain.

Rest in Peace, noble piece of PCB.

May your traces forever carry signal in Retronirvana.

(1996 – 2026)

P.S: My sincere condolences... €37 or not, it's just a damn shame about that legendary HX chipset and that pristine layout!

DOS:P233MMX,64MB,ECS,SpeaMirageV7,3dfxV1,AWE64,ESS1868,PicoGUS,32GB
W98SE:K63/400,256MB,P5A,Verite2200AGP,3dfxV2,M3D,AWE64,ESS1938,PicoGUS,64GB
XP:P3-1G,512MB,CUSL2C,FX5600AGP,Audigy1,80GB

Reply 4 of 5, by CrustyCeleron

User metadata
Rank Newbie
Rank
Newbie

Ah such a shame. RIP AP53.

Though... could try 3 things;

- Reducing all memory settings to their worst/minimums. L2 off. Timings at slowest.

- A different EDO or FPM pair.

- Isopropyl to clean. A magnifying glass to inspect. And look for damage. Especially to nearby traces and the dimm socket. Quick joint could fix it. Hell, cleaning might fix it! Look on the ram contacts too.