Just purchased my first IBM 5160

[John's first 5160]

In the following, DEBUG is used to copy the contents of U18 into a file named MYF800.BIN
Please perform that, then supply the MYF800.BIN file to me.
The bits in red are what you enter.

C:\DOS>DEBUG
-N MYF800.BIN
-R BX
BX 0000
:0000
-R CX
CX 0000
:8000
-M F800:0 L8000 0100
-W 0100
Writing 8000 bytes
-Q

Ok, will do. Im off this friday , will do it them.

Thank you.

 

[John's first 5160]

Assumption: The purpose is to make a backup of the MFM drive.

In the DOS directory is a program named XCOPY.
So, one way would be to:

1. Boot from the MFM drive. ( The MFM drive is C: and the CF is D: )
2. Enter the command XCOPY C:\ D:\5160 /S /E
3. When XCOPY asks about file or directory, press the 'D' key.
4. {copying starts}

That will result in a directory named '5160' being created on the CF, and the directory and file contents (except for hidden files) of the MFM drive being copied into the '5160' directory.

So I copied the MFM drive. Total was 8.48 megs, took almost 40 minutes, lol , crazy!

Thanks!

 

[John's first 5160]

In the following, DEBUG is used to copy the contents of U18 into a file named MYF800.BIN
Please perform that, then supply the MYF800.BIN file to me.
The bits in red are what you enter.

C:\DOS>DEBUG
-N MYF800.BIN
-R BX
BX 0000
:0000
-R CX
CX 0000
:8000
-M F800:0 L8000 0100
-W 0100
Writing 8000 bytes
-Q

I did the ROM capture, but when I try to attach it here a message says I am not allowed to upload .BIN files.

Let me know.

 

[John's first 5160]

Also, the DeOxit seems to have worked. I can start the PC without fail so far with the quadboard in place.

 

[modem7]

I did the ROM capture, but when I try to attach it here a message says I am not allowed to upload .BIN files.

Does Zipping it work ?

 

[John's first 5160]

Does Zipping it work ?

Will try that. Thank you.

 

[John's first 5160]

Does Zipping it work ?

Here it is.

let me know what you find.

 

[modem7]

Here it is.
let me know what you find.

Thanks for that - it's informative. It turns out that there are two versions of the 1501512 ROM.

In mine, the copyright string is, "1501512 COPR. IBM 1981". In yours, the copyright string is, "1501512 COPR. IBM 1982".

Accordingly, the checksum byte (the final byte in the 1501512 ROM) is also different in order to cater for the '81' versus '82' change.

(IBM did the same thing for the final BIOS revision in the IBM 5150 - two versions of the 1501476 ROM - one 1981, one 1982.)

I will modify RAYXTMFM so that it recognises the 1982 dated 1501512 ROM.

 

[John's first 5160]

Wow, Thats cool. Nice find!

 

[modem7]

Wow, Thats cool. Nice find!

RAYXTMFM is now at version 1.6, and will now identify the 1982 dated 1501512 ROM.

 

[John's first 5160]

This is unusual, right? Maybe the unit was sent for repair and the BIOS flashed?

 

[maxtherabbit]

Thanks for that - it's informative. It turns out that there are two versions of the 1501512 ROM.

In mine, the copyright string is, "1501512 COPR. IBM 1981". In yours, the copyright string is, "1501512 COPR. IBM 1982".

Accordingly, the checksum byte (the final byte in the 1501512 ROM) is also different in order to cater for the '81' versus '82' change.

(IBM did the same thing for the final BIOS revision in the IBM 5150 - two versions of the 1501476 ROM - one 1981, one 1982.)

I will modify RAYXTMFM so that it recognises the 1982 dated 1501512 ROM.

I take it you did a full binary compare and the copyright date (and checksum) were the only divergent bytes?

 

[DrAlis]

Hi Modem, I have recently brought two 5155 back to life and I also used your list So I can gladly contribute my tantal explosion list:

5155 - only C58
5155 - C58 and C56 (MB) and C8 (on CGA) (all blown) and a 10uF tantal on a short IBM memory expansion (has square silver ic like things on it). Three were blown on the start. And after I removed them the fourth one blew. The machine works well without the first three. Without the last one I get very strange behaviour. It boots up but when I type sometimes keypresses turn into "-" on the screen and the machine feels unresponsive and slow. So I took the mem extension back out until I get caps to fix...

I have added the failure to the list at [here].


Presumably, you are writing of leakage from the card's battery.

 

[modem7]

I take it you did a full binary compare and the copyright date (and checksum) were the only divergent bytes?

Yes, performed by the comparison functionality in my hex editor.

This is unusual, right? Maybe the unit was sent for repair and the BIOS flashed?

The 1501512 ROM chip in your IBM 5160 is a masked ROM. For masked ROM's: a company supplies code to the maker of the masked ROM. The maker creates the ROM with the code built in. From the factory, the code in a masked ROM cannot be altered by software/hardware - the contents are fixed.

The IBM 5160 was released in early 1983. So, production of IBM 5160 unique parts would have started before then. MAYBE the "1981" in the code was simply a carry over of reused code from the IBM 5150 - someone forgot to update the date to 1982. Later, for possibly legal reasons, a decision was made to change the date to 1982. IBM then produced new code for the masked ROM makers to put into the 1501512 masked ROM's.

 

[modem7]

Hi Modem, I have recently brought two 5155 back to life and I also used your list So I can gladly contribute my tantal explosion list:

Done - both added to the list. Thanks.

 

[DrAlis]

Thanks. both repairs were done in Oct 2021 btw. Big thanks to all creators of minuszerodegrees btw!!! The stuff you provide is awesome and to the point helpful. Wish there would be more like this! Chapeau!