Thinkpads Forum

After a period of working on the AC power, I decided to replace the dead battery on my 701C. I got one NiCd from Amazon. When I insert the battery the 701C beeped twice(or once? can't recall clearly now), without any screen activity, then continued to behave like powered-off. I plugged in the AC adapter, checked the BIOS, and found that the 701C thought the battery was "Not Installed".And the battery-charging LED was dark. Tried several times but the symptom ("Not Installed" & dark LED) remained unchanged.

Then I got my hands on a flashlight to see the situation in the battery slot. And I found part of the contacts were damaged by the leaked liquid which is from the old battery, when last time it leaked. But since with the battery only the 701 DID BEEP, as mentioned above, I think the contacts are only damaged but not destoryed. However, the beep symptom only showed once, and after that the battery can't let the 701 do anything.

Will a completely discharged but not dead battery cause 701 to ignore its presence? With the dark charging LED I don't know if the 701 will charge the battery. Will appreciate any and all help.

Try to clean contact and re-solder all damaged elements on board.
Today I fixed 390E after water damage - power jack literary felt of board. Acid from battery can get things even worse.
As they are more than two contact points, part of them may work, other not - and this is one of possible causes of your problem.

I'd like to ask another question without posting another topic. Sometimes when I start my 701 it gives me "Divide Overflow" during the starting process of MS-DOS, and I can do nothing but restart. But unlike what some others do,this only happens "sometimes", not "always". In most cases a Ctrl+Alt+Del will get everything done and the 701 starts properly. So why does it appear? Kind of strange really.

What I have on my 701 is MS-DOS 5.0, Windows 3.1, and some other DOS-or-Windows applications. FYI, I have a TSR application but I do not load it at start in the autoexec.bat. As I see sometimes this is a memory error so I provide this to you.