I have a IBM PS/2 mod 60 (tower model) standing for a long time in my
house.
Suddenly it stopped being bootable. The message shows 161 163 with two
beeps afterwards.
I have the tried to boot it with the reference disk I got it from the
IBM site, I have tried to connect a new battery. Nothing works. I still
get the same error code. The PC was supposed to be a Christmas present
for my 78 years old father to use for simple word-processing. He has
promised to write the exciting history of his life if I gave him an old
PC.
Can anyone save my Christmas.
Jonas
161 and 163 almost always mean a flat battery.
Change the battery, boot from a reference disk and run auto config.
Leave the referce disk in the drive. Press F10 to accept and save the
changes. Let the machine boot from the reference disk again and change
the system date and time.
Remove the reference disk and the machine should reboot properly with no
error codes.
I hope this has saved you Christmas. If you feel like giving any more
computers away, you can put me on your christmas list. :-)
--
Steve Price
Since the government didn't provide any backup reference diskettes
when the machines were donated, I went out to IBM's ftp site and
grabbed their most current reference diskettes for the various
PS/2 models that we received.
I'm now at the point where a strange problem has emerged --
after running automatic configuration, I can't get many of the
machines to boot from the hard disk -- all that I get is a blinking
cursor in the upper left hand corner. However, if I boot from a
floppy drive, I can do whatever I want on the hard disk. I've loaded
many different versions of DOS (IBM DOS 6.1, MS-DOS 6.21 and 6.22),
run FDISK numerous times, and run SYS C: countless times, all
with the same result. While I can definitely build a floppy
boot disk and then use the SHELL and COMSPEC statements to load
the command processor from the C: drive, I'd rather avoid this route.
I've now had this problem bite me on a PS/2 55SX, 95, 60 and 70,
and I'm really stumped. Any suggestions on a reasonable approach to take ?
Thanks -- Martin
Ken
====================