1
0
mirror of https://github.com/pkimpel/retro-b5500.git synced 2026-05-05 23:54:53 +00:00

Reconstruct Google Code wiki history from r335 on 2013-07-13.

This commit is contained in:
Paul Kimpel
2015-04-04 09:21:33 -07:00
parent bb9794c000
commit 7a7da5b052

View File

@@ -63,7 +63,7 @@ As of this writing, the emulator has been tested with and works with Mozilla Fir
== The Web Server ==
The emulator must be hosted on a web server. You will not be able to run the emulator simply by opening files in your browser from your local file system. The web server can run on your local system and serve files from your local file system, but the emulator files must be served to the browser over HTTP and not simply opened as files within the browser.
See [WebUISettingStarted#Establish_the_Web_Server Establish the Web Server]
See [WebUIGettingStarted#Establish_the_Web_Server Establish the Web Server]
below for more details.
As an alternative to setting up and operating your own web server, you are welcome to use a web site we have set up on a hosting service. Just point your browser to the following URL:
@@ -78,7 +78,7 @@ The web-based emulator is hosted in two directories (folders) of files:
* *`emulator/`* contains the core mainframe modules. These are Javascript objects for the Processor, Central Control, and I/O Unit, plus a simple object that defines the configuration of the system to be emulated.
* *`webUI/`* contains everything else you need to run the system. In particular, it contains the Console UI, the peripheral device drivers, a Cold utility used to initialize the disk subsystem, and a SyllableDebugger utility that can be used to examine the state of the processor while running programs, including the MCP.
* *`webUI/`* contains everything else you need to run the system. In particular, it contains the Console UI, the peripheral device drivers, a Cold Loader utility used to initialize the disk subsystem, and a Syllable Debugger utility that can be used to examine the state of the processor while running programs, including the MCP.
An optional third directory, *`tools/`* contains some standalone utilities that can be used to examine and maintain the emulator environment.
@@ -94,7 +94,7 @@ The emulator files implement only the hardware portion of a B5500 system. To mak
Burroughs became part of Unisys Corporation in 1986. Unisys still owns and maintains copyrights the B5500 system software. We have acquired an educational/hobbyist license to use the Mark XIII release of that software and make it available to others. It is _not_ open source software, however, and not part of this project, so we cannot include it on the project site with the emulator files.
The Burroughs Mark XIII software consists of a set of three binary tape image files from a release in 1971. We are making these files available through a
[http://www.phkimpel.us/B5500/website/SoftwareRequest.html page on our hosting service]. Go to that page, review and accept the licensing terms (they are not onerous), and download one or more of the tape images.
[http://www.phkimpel.us/B5500/webSite/SoftwareRequest.html page on our hosting service]. Go to that page, review and accept the licensing terms (they are not onerous), and download one or more of the tape images.
You will need to download at least the `SYSTEM` tape image, which contains the MCP operating system, compilers, and utilities. The other two images, `SYMBOL1` and `SYMBOL2`, contain source code for the Mark XIII release and are not necessary to run the emulator. See
[WebUIGettingStarted#Download_the_B5500_System_Software Download the B5500 System Software] below for instructions.
@@ -117,7 +117,7 @@ If you want to use your own web server, however, the general steps to set up the
# Create a new virtual directory, say, `/B5500/` to hold the emulator files.
# Download one of the emulator releases (the latest one is usually best) from http://www.phkimpel.us/B5500/downloads/.
# Download one of the emulator releases (the one with the highest release-number suffix is usually best) from [https://drive.google.com/folderview?id=0BxqKm7v4xBswM29qUkxPTkVfYzg&usp=sharing our download site].
# Unzip the release into the directory on your server's file system where the virtual directory is mapped. You will need at least the `emulator/` and `webUI/` directories, and they must be at the root of the virtual directory.
@@ -157,7 +157,7 @@ The Cold Loader will attempt to open the IndexedDB database used by the emulated
After you dismiss the dialog box, the page will dump the contents of the first 2100 disk segments in the database to your screen. If the database has just been initialized, the display will simply indicate that 2100 segments are available.
</wiki:comment>
*Note:* _You *must* run the Cold Loader from the same web site as the one from which you will run the emulator._
Note: _You *must* run the Cold Loader from the same web site as the one from which you will run the emulator._
The IndexedDB API is subject to the "same origin" policy used by many web browser features. That means that the database used for the disk subsystem is restricted for use only by web pages and scripts from the same Internet host name as the one that created the database. Even though the database is physically stored on your workstation, if you run the Cold Loader from one web site and the emulator from another, they will access two separate databases on that workstation.