/
SoftwareRequest.html
80 lines (59 loc) · 6.42 KB
/
SoftwareRequest.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
<!DOCTYPE html>
<head>
<title>retro-B5500 Mark XIII System Software</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Author" content="Nigel Williams & Paul Kimpel">
<meta http-equiv="Content-Script-Type" content="text/javascript">
<meta http-equiv="Content-Style-Type" content="text/css">
<meta http-equiv="cache-control" content="no-cache">
<meta http-equiv="pragma" content="no-cache">
<link id=defaultStyleSheet rel=stylesheet type="text/css" href="./website.css">
</head>
<body>
<a href="../index.html" title="Click to return to the Home Page">
<img id=retroButton src="../webUI/resources/A-CONTROL.png" alt="retro A-CONTROL logo">
</a>
<h1><img src="../webUI/resources/retro-B5500-Logo.png" alt="retro logo">
<hr>
Burroughs B5500 Mark XIII System Software
</h1>
<h2>Background</h2>
<p>The Burroughs B5000 and B5500 were perhaps the first computer systems designed with the idea that they would require a significant operating system in order to run. Operating systems in the early 1960s were known as <i>control programs</i>. The designers at Burroughs envisioned a program that would automatically administer the entire system's operation, and thus created what became known as the Master Control Program, or <b>MCP</b>.
You can read the story of how this came about in the
<a href="http://purl.umn.edu/107105">1985 B5000 oral history</a> transcription.
<p>As a result of that design approach more than 50 years ago, having a B5500 emulator today is not all that interesting unless you also have the associated system software to make it do something. Alas, software was maintained in those days on punched cards and 7-track, open-reel magnetic tape, neither of which have seen much use in the last 30 years. Open-reel magnetic tape, in particular, is not known for having long-term archival qualities.
<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 on those tapes and making the resulting data 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, then 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>.
<h2>Downloading the Tape Images and Source Files</h2>
<p>Our license with Unisys allows us to make the Mark XIII software available to others under the terms of that license. There are three tape images and a ZIP archive of decoded ASCII source, as enumerated below. To download one of the files, please click its corresponding link. The resulting page will display the applicable terms of the Unisys license, and for the tape image files, a directory of the files on that image. Confirm your acceptance of the license terms to begin the download. You will need to download at least the <b>SYSTEM</b> image in order to run the emulator.
<dl>
<dt><a href="./TapeImage-SYSTEM.html"><b>SYSTEM</b></a> image (2.6MiB <code>.zip</code>)
<dd><code>B5500-XIII-SYSTEM-adc00257.zip</code> contains object code for the release, including the Datacom MCP, Timesharing MCP, System Intrinsics, CANDE timesharing system, compilers, and utility programs. It also contains source files for a few utilities, and a set of source-level patch files for the release.
<dt><a href="./TapeImage-SYMBOL1.html"><b>SYMBOL1</b></a> image (2.2MiB <code>.zip</code>)
<dd><code>B5500-XIII-SYMBOL1-adc00255.zip</code> contains the source code for the Datacom MCP, System Intrinsics, and compilers.
<dt><a href="./TapeImage-SYMBOL2.html"><b>SYMBOL2</b></a> image (2.1MiB <code>.zip</code>)
<dd><code>B5500-XIII-SYMBOL2-adc00253.zip</code> contains the remaining source code for the release, including the Timesharing MCP, CANDE, and utility programs.
<dt><a href="./B5500-XIII-Release.html"><b>Release</b></a> ZIP archive file (5.2MiB <code>.zip</code>)
<dd><code>B5500-XIII-Release.zip</code> contains the source and object code for the entire XIII release, translated from 6-bit B5500 internal code to ASCII text files, using the standard retro-b5500 substitutions for the B5500 characters that do not have ASCII equivalents.
</dl>
<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., 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.
The format of disk file headers is described in the
<a href="http://bitsavers.org/pdf/burroughs/B5000_5500_5700/1024916_B5500_B5700_OperMan_Sep68.pdf">B5500 Operation Manual</a>, 1024916 (September 1968, revised June 1971, PCN 015), page 5-41. B5500 character codes are described in Appendix A of that reference.
<p>We have developed a few HTML/Javascript utilities to read these tape images and decode their data. See
<a href="../tools/B5500LibMaintDir.html">B5500LibMaintDir.html</a>,
<a href="../tools/B5500LibMaintDecoder.html">B5500LibMaintDecoder.html</a>, and
<a href="../tools/B5500LibMaintExtract.html">B5500LibMaintExtract.html</a>
in the /tools directory.
<p>
<div id=footerDiv>
Copyright (c) 2013, Nigel Williams and Paul Kimpel • Licensed under the MIT License
</div>
<div id=lastModDiv>Revised
2017-05-28
</div>
</body>
</html>