VOGONS


First post, by behshad

User metadata
Rank Newbie
Rank
Newbie

Hi all,

I have this ABC Computers motherboard with a 386sx 16 processor. it seems to fire up fine but then it stops after the memory count 4IsAvB7.jpg cursor still blinks but there is nor any message on screen neither I can interact with keyboard. cEB5yix.jpg

I used a diagnostic card but error message is not very helpful GYBsQpC.jpg

it doesn't have a CMOS battery as it was removed due to leakage. leakage damage was very minor and didn't need a repair but i still went ahead and removed the 5 pin din socket and cleaned up all around it.

any help would be appreciated

thanks

Behshad

Reply 1 of 8, by Deunan

User metadata
Rank Oldbie
Rank
Oldbie

Some mobos require battery to be present, otherwise RTC/CMOS doesn't work properly. Try connecting something to the external battery header, 3x AA pack for example is cheap and easy to use (and the wires can be long, just make sure nothing gets pinched between cards or cut on some sharp edge).

Reply 2 of 8, by behshad

User metadata
Rank Newbie
Rank
Newbie

thanks, today i tested the mobo with both x1 3.7 volts battery as well as serial-ing x3 AA batteries (4.5 volts) and neither made any difference. i noticed the memory only counts up to 512k. if i add more ram, the mobo sometimes hangs BEFORE the memory count and once or twice when it finished counting, it still showed just 512 kb (even though 1 Mb) was installed

Reply 3 of 8, by majestyk

User metadata
Rank Oldbie
Rank
Oldbie

Is the jumpering correctly set for 1MB?
As for the "very minor battery leakage" - both 8-bit slots have blueish contacts, this indicates it wasn´t so minor after all. I would look for the cause of the keyboard issue right there.

Reply 5 of 8, by Predator99

User metadata
Rank l33t
Rank
l33t

Does this happen with all cards (escpecially IDE controller) removed?

Is there a twist in the IDE cable on the controller side? For3me it seems the HD is not connected correctly. Try to remove it...

Reply 6 of 8, by Deunan

User metadata
Rank Oldbie
Rank
Oldbie
Predator99 wrote on 2024-04-14, 12:06:

Is there a twist in the IDE cable on the controller side? For3me it seems the HD is not connected correctly. Try to remove it...

Good catch. I didn't even notice it at first.

OP, please disconnect any HDD or floppy drives, _along_ with all the cables. Whatever you have connected there to the Super IO card should not be connected with the twisted part of the cable at the card.
Always run these tests with the bare minimum hardware required, and only when that works you can add more cards and drives.

Reply 7 of 8, by BitWrangler

User metadata
Rank l33t++
Rank
l33t++

Does it get far enough to complain about no keyboard if you leave that unplugged? Some boards are picky about keyboards, or some keyboards are picky about boards.

Unicorn herding operations are proceeding, but all the totes of hens teeth and barrels of rocking horse poop give them plenty of hiding spots.

Reply 8 of 8, by behshad

User metadata
Rank Newbie
Rank
Newbie

thanks for all the help guys. love this forum. just as reference here is a similar 286 mobo which i found closest physically to mine https://theretroweb.com/motherboards/s/abc-co … ct-286-ver.-1.2

Yes you are right about testing with no cards attached. I removed everything but still same failed result. mobo recognizes i.e. missing bank zero rams or the graphic card (if not present) and makes appropriate beeps but every time I still get the dreaded blinking cursor right after successfully counting the first memory bank.

with or without keyboard connected mobo still stops at the same point, I tried different keyboards (even couple XT keyboards!!!) but mobo seems not to care at all. I reckon if problem is keyboard circuitry related then mobo should at least complain about something?!

I cannot see any jumpers to set for more memory ram. I don't think there is any.

last night I found some corrosions which I had missed earlier: Ufty0F5.jpg around the area between keyboard to the keyboard controller IC. this weekend I will re-clean the mobo with vinegar and wash with Isopropyl this weekend and attend to any oxidisation on BIOS chips or other chips too.

it's annoying when there is no on-screen error messages or beeps or even then diagnostic card numbers are not helpful

BTW, I am so glad the SIPP rams were so short-lived !!! no wonder. the damn things are so badly designed and are pain to pull out and put back. my finger tips are sore hehe