github.com/pkimpel.retro-b5500
1
0
Fork 0
mirror of https://github.com/pkimpel/retro-b5500.git synced 2026-05-05 07:34:36 +00:00
Code Releases Activity

Minor web site corrections as of 2013-07-18 (from WIP r348).

Browse Source
This commit is contained in:
paul.kimpel@digm.com
2014-08-09 19:20:53 +00:00
parent 75e0c4aca7
commit 32c2dd8351
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
webSite/SoftwareRequest.html
View File

@@ -30,7 +30,7 @@ You can read the story of how this came about in the
<p>Fortunately for us, Sid McHarg of Seattle, Washington (US) had preserved a set Burroughs 7-track release tapes for the B5500 Mark XIII (October 1971) version of the system software. Even more fortunately, Sid was able to work with Paul Pierce of Portland, Oregon (US) to recover the data from those tapes. We are indebted to Sid and Paul for their work in recovering those tapes and making the results available.
<p>Burroughs became part of Unisys Corporation in 1986. Unisys still owns and holds copyrights on the B5500 system software, so Sid worked with Bob Supnik, VP on Engineering and Supply Chain at Unisys, to arrange an educational/hobbyist license for this software. We have acquired such a license, and are thus indebted to Bob and Unisys for generously allowing us to use the B5500 Mark XIII software under the
<p>Burroughs became part of Unisys Corporation in 1986. Unisys still owns and holds copyrights on the B5500 system software, so Sid worked with Bob Supnik, VP of Engineering and Supply Chain at Unisys, to arrange an educational/hobbyist license for this software. We have acquired such a license, and are thus indebted to Bob and Unisys for generously allowing us to use the B5500 Mark XIII software under the
<a href="./Unisys-B5500-Software-License.pdf">terms of that license</a>.
@@ -52,7 +52,7 @@ You can read the story of how this came about in the
<h2>Format of the Tape Image Files</h2>
<p>Each of the tape images above is a standard ZIP archive file containing a single "<code>.bcd</code>" file. That file is a binary octet stream, i.e., it is a blob of 8-bit bytes. Each octet represents one data frame (6-bit character) from the 7-track tape. The low-order six bits of each octet contain the binary data from the tape frame. The next-higher bit is the odd-parity bit. The high-order bit in the octet will be a <code>1</code> if that frame is the first one in a physical tape block, and <code>0</code> otherwise. A tape mark (EOF) is represented by a block containing a single octet with the hexadecimal code 8F.
<p>Each of the tape images above is a standard ZIP archive file containing a single "<code>.bcd</code>" file. That file is a binary octet stream, i.e., a blob of 8-bit bytes. Each octet represents one data frame (6-bit character) from the 7-track tape. The low-order six bits of each octet contain the binary data from the tape frame. The next-higher bit is the odd-parity bit. The high-order bit in the octet will be a <code>1</code> if that frame is the first one in a physical tape block, and <code>0</code> otherwise. A tape mark (EOF) is represented by a block containing a single octet with the hexadecimal code 8F.
<p>The files on the tape image are formatted in B5500 "Library/Maintenance" format, which is described in the
<a href="http://bitsavers.org/pdf/burroughs/B5000_5500_5700/1042462_B5500_MCP_Reference_Jun69.pdf">B5500 MCP Reference Manual</a>, 1042462 (June 1969), page 8-1. Tape label records are described in Appendix B of that reference.
@@ -70,7 +70,7 @@ in the /tools directory.
Copyright (c) 2013, Nigel Williams and Paul Kimpel &bull; Licensed under the MIT License
</div>
<div id=lastModDiv>Revised
2013-07-10
2013-07-17
</div>
</body>