Backup battery leakage 386/486

Backup battery leakage 386/486 - problems

Topic actions

Post a reply

First post, by Half-Saint

Posted on 2013-08-23, 09:50

Half-Saint Offline

Rank Oldbie

Rank: Oldbie
Posts: 935
Joined: 2013-07-26, 04:27
Location: Slovenia

I have two motherboards which had leaky batteries. In both cases I desoldered the battery and cleaned the residue with white vinegar and isopropyl alcohol.

Now my 486 board won't even let me enter BIOS. I can see it do a RAM count, report floppy drive error then it switches to a blank screen displaying :47:56Z000 in the top left corner. I thought the battery residue just damaged the coating not the traces themselves...

The weird thing is that this board worked just fine before I cleaned it. Any ideas?

As I was writing this, I went back and tried to power it on a few more times. Now it won't output anything to the screen and it doesn't give me any beeps. WTF...

That 386 board, on the other hand works fine.

Reply 1 of 8, by carlostex

Posted on 2013-08-23, 10:04

carlostex Offline

Rank l33t

Rank: l33t
Posts: 2405
Joined: 2010-04-03, 21:39
Location: Portugal

Check the traces carefully and see if anything is cut.

Reply 2 of 8, by Half-Saint

Posted on 2013-08-23, 11:14

Half-Saint Offline

Rank Oldbie

Rank: Oldbie
Posts: 935
Joined: 2013-07-26, 04:27
Location: Slovenia

I checked most, if not all traces that looked suspicious and they all gave a beep on the voltmeter. So unless it's one of the traces that I couldn't get to, I don't know what it could be.

Reply 3 of 8, by Stojke

Posted on 2013-08-23, 12:55

Stojke Offline

Rank l33t

Rank: l33t
Posts: 2080
Joined: 2012-03-23, 14:51
Location: Serbia

One of the boards i cleaned had problems with the keyboard, so i soldered an like some people at vogons suggested to, but than it wouldnt start at all 😀

I have not made any errors during soldering, it might be possible that the internal lines were also damaged.

Note | LLSID | "Big boobs are important!"

Reply 4 of 8, by Half-Saint

Posted on 2013-08-24, 19:40

Half-Saint Offline

Rank Oldbie

Rank: Oldbie
Posts: 935
Joined: 2013-07-26, 04:27
Location: Slovenia

Still not any closer to a solution...

Reply 5 of 8, by Half-Saint

Posted on 2013-08-26, 08:56

Half-Saint Offline

Rank Oldbie

Rank: Oldbie
Posts: 935
Joined: 2013-07-26, 04:27
Location: Slovenia

Looks like the problem fixed itself... I have no idea what happened but the board appears to be functional now.

Reply 6 of 8, by badmojo

Posted on 2013-08-26, 10:15

badmojo Offline

Rank l33t

Rank: l33t
Posts: 4048
Joined: 2011-10-11, 04:14
Location: Australia

Maybe it just hadn't dried out properly.

Life? Don't talk to me about life.

Reply 7 of 8, by rgart

Posted on 2013-08-26, 11:44

rgart Offline

Rank Oldbie

Rank: Oldbie
Posts: 738
Joined: 2013-04-16, 05:32
Location: Australia

badmojo wrote:
Maybe it just hadn't dried out properly.

=My Cyrix 5x86 systems : 120MHz vs 133MHz=. =My 486DX2-66MHz=

Reply 8 of 8, by nforce4max

Posted on 2013-08-26, 13:04

nforce4max Offline

Rank l33t

Rank: l33t
Posts: 2451
Joined: 2012-05-05, 22:55

This is why I do full board washes when something like this comes up as sometimes the acid from the battery as well the vinegar finds its way into spaces not easily seen. Good luck with your build.

On a far away planet reading your posts in the year 10,191.

Go to top of page Go to top of page

Back to General Old Hardware

Main menu

Common searches