Image Map Image Map
Results 1 to 5 of 5

Thread: IBM PS/2 P70 8573 POST 161 163 after replacing battery

  1. #1
    Join Date
    Dec 2010
    Location
    Marietta, GA
    Posts
    303

    Default IBM PS/2 P70 8573 POST 161 163 after replacing battery

    I recently came into a wonderful IBM PS/2 P70, which I have always wanted. I knew it had POST errors 161 and 163 on buying, and hoped this could be fixed quickly.

    When I first got it, it does a RAM check up to 8MB, and then shows POST errors 161 (CMOS configuration lost (battery has died)) and 163 (CMOS error; Clock is not updating).

    I opened it up, and found it was quite clean, and there was no CMOS battery installed, so I purchased a new Duracell DL223A, and put it in. It still gives a 161 and 163 error.

    I checked the battery lines with a DVM, and it says a clean 6.4 VDC all the way to the PCB connections (I even checked it when running).

    I created several P70 reference disks on a spare Win98 laptop with a floppy drive, and ran REFSTAMP on those. After getting 161 163, I try the floppy and it sounds good initially, but then just spins forever, and when I eventually eject it, the P70 goes to cassette BASIC. The keyboard works fine, and I can enter in a program, list it, renumber it, and run it without issue.


    It came with modem and network cards, and I removed them. I tried replacing the nasty sounding ESDI hard drive with a working spare, and no difference. I eventually unplugged the hard drive completely, and there's no difference, still 161 and 163 POST errors.

    I also tried removing all the RAM sticks (it has 4 sticks), and tried putting in only 1 stick (and I tried 2 of the original 4 sticks) as the only stick. No difference, except the RAM check only goes to 2MB in those cases.

    So I've done tons of internet searches, and am looking for help.


    My first thought was that somehow there's a power draw making it look like there's no CMOS battery, but checking the board connections shows it is still 6+ volts when running. Shouldn't replacing the battery cause the 161 error to go away, and just leave the 163 error?

    It's also likely my floppy drive needs capacitor replacement, but that just affects its inability to boot from my created reference disks. I keep coming back to thinking that the continued 161 error is the problem.

    Can someone help?

  2. #2
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    6,494

    Default

    Quote Originally Posted by Holmes View Post
    I opened it up, and found it was quite clean, and there was no CMOS battery installed, so I purchased a new Duracell DL223A, and put it in. It still gives a 161 and 163 error.
    Even the IBM AT exhibits that behaviour. With the IBM AT, after a bad battery is replaced with new, the only way to remove the 161 and 163 errors is to follow up by executing the SETUP procedure. Even with the configuration in the CMOS/RTC chip being in an 'unconfigured' state, the IBM AT can still boot from the AT's diagnostic floppy (in order to perform SETUP).

    I am pretty sure that the P70 is 'in the same boat'; need to run the P70's reference diskette.

  3. #3
    Join Date
    Dec 2010
    Location
    Marietta, GA
    Posts
    303

    Default

    Quote Originally Posted by modem7 View Post
    Even the IBM AT exhibits that behaviour. With the IBM AT, after a bad battery is replaced with new, the only way to remove the 161 and 163 errors is to follow up by executing the SETUP procedure. Even with the configuration in the CMOS/RTC chip being in an 'unconfigured' state, the IBM AT can still boot from the AT's diagnostic floppy (in order to perform SETUP).

    I am pretty sure that the P70 is 'in the same boat'; need to run the P70's reference diskette.
    OK, I see. Looks like I can't procrastinate working on the floppy drive, then! Nuts.

    Thanks!

  4. #4
    Join Date
    May 2006
    Location
    Melbourne, Australia
    Posts
    6,494

    Default

    Quote Originally Posted by Holmes View Post
    It's also likely my floppy drive needs capacitor replacement, but that just affects its inability to boot from my created reference disks.
    The "created reference disks" are also suspect until proven good.

    I have read things like, "It took me four attempts to create a reference diskette that worked."

    Consider trying REFSTAMP against your created reference disks. Detailed at [here].

  5. #5
    Join Date
    Dec 2010
    Location
    Marietta, GA
    Posts
    303

    Default

    Quote Originally Posted by modem7 View Post
    The "created reference disks" are also suspect until proven good.

    I have read things like, "It took me four attempts to create a reference diskette that worked."

    Consider trying REFSTAMP against your created reference disks. Detailed at [here].
    I did run REFSTAMP on my created reference disks. I first ran it in "report" mode, and it said the just-created disks were NOT refstamped. Then I ran it to update the refstamps, and checked with the "report" mode again, and it seemed to work.

    I just attempted to boot using the created reference disks on the win98 machine I used to create them, and it showed an official message "window" on a text screen saying "The Reference Diskette in drive A will not run on this system. Your system is now locked." It seems like the disks work.

    Maybe I can try building them on a different machine, once I unpack them.

    Thanks for the suggestions.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •