Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Start using HTTPS to access all archived files

Browse source
This commit is contained in:
Jeff Parsons 2017-08-23 20:20:17 -07:00 • committed by Jeff Parsons
commit 73bcb543fd
185 changed files with 17533 additions and 17518 deletions
Download patch file Download diff file Expand all files Collapse all files

10
devices/pcx86/rom/5170/README.md
View file

@ -45,18 +45,18 @@ From [http://minuszerodegrees.net/bios/BIOS_5170_10JAN84_6MHZ.zip](http://minusz
The JSON-encoded ROM image that PCjs uses was created using the *FileDump* command-line *merge* option:
filedump --file=http://archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JAN84_U27_6181028_27256_6MHZ.BIN --merge=http://archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JAN84_U47_6181029_27256_6MHZ.BIN --output=ATBIOS-REV1.json --overwrite
filedump --file=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JAN84_U27_6181028_27256_6MHZ.BIN --merge=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JAN84_U47_6181029_27256_6MHZ.BIN --output=ATBIOS-REV1.json --overwrite
Since a MAP file ([ATBIOS-REV1.map](1984-01-10/ATBIOS-REV1.map)) exists as well, it is automatically appended to the JSON file
([ATBIOS-REV1.json](1984-01-10/ATBIOS-REV1.json)) when using a ROM input file (or JSON output file) with a matching filename.
It is also possible to create a merged binary ROM image ([ATBIOS-REV1.rom](http://archive.pcjs.org/devices/pcx86/rom/5170/ATBIOS-REV1.rom))
It is also possible to create a merged binary ROM image ([ATBIOS-REV1.rom](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/ATBIOS-REV1.rom))
by adding *--format=rom* to the command-line (the default is *--format=json*).
These operations can only be performed using the *FileDump* command-line interface; the *FileDump* API does not support
either the *merge* option or the appending of MAP data. For the moment, the API can only dump unadorned ROM images; eg:
http://localhost:8088/api/v1/dump/?file=http://archive.pcjs.org/devices/pcx86/rom/5170/ATBIOS-REV1.rom
http://localhost:8088/api/v1/dump/?file=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/ATBIOS-REV1.rom
---
@ -89,7 +89,7 @@ From [http://minuszerodegrees.net/bios/BIOS_5170_10JUN85_6MHZ.zip](http://minusz
The JSON-encoded ROM image that PCjs uses was created using the *FileDump* command-line *merge* option:
filedump --file=http://archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JUN85_U27_6480090_27256.BIN --merge=http://archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JUN85_U47_6480091_27256.BIN --output=ATBIOS-REV2.json --overwrite
filedump --file=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JUN85_U27_6480090_27256.BIN --merge=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_10JUN85_U47_6480091_27256.BIN --output=ATBIOS-REV2.json --overwrite
---
@ -125,4 +125,4 @@ From [http://minuszerodegrees.net/bios/BIOS_5170_15NOV85_8MHZ_VARIATION_2.zip](h
The JSON-encoded ROM image that PCjs uses was created using the *FileDump* command-line *merge* option:
filedump --file=http://archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_15NOV85_U27_61X9266_27256.BIN --merge=http://archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_15NOV85_U47_61X9265_27256.BIN --output=ATBIOS-REV3.json --overwrite
filedump --file=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_15NOV85_U27_61X9266_27256.BIN --merge=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/rom/5170/BIOS_5170_15NOV85_U47_61X9265_27256.BIN --output=ATBIOS-REV3.json --overwrite

6
devices/pcx86/rom/compaq/deskpro386/README.md
View file

@ -10,7 +10,7 @@ COMPAQ DeskPro 386 ROMs
The oldest COMPAQ DeskPro 386 ROM I have is a Rev J.4 ROM from a "Version 2" motherboard designed
in 1987 and released in 1988.
[<img src="http://archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_Board_V2-640.jpg" alt="Compaq DeskPro 386 System Board Version 2"/>](http://archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_Board_V2.jpg)
[<img src="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_Board_V2-640.jpg" alt="Compaq DeskPro 386 System Board Version 2"/>](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_Board_V2.jpg)
Thanks to folks on the [Vintage Computer](http://www.vintage-computer.com/) forums, I also have a Rev N.1 ROM from 1989.
@ -65,9 +65,9 @@ Arduino-compatible prototyping board, and capturing the serial port output on my
by [NYC Resistor](http://www.nycresistor.com/) contributor [phooky](http://www.nycresistor.com/author/phooky/).
The DeskPro 386 ROMs were P27128A-2 chips, so I wired my Uno32 based on this
[27128A](http://archive.pcjs.org/pubs/pc/datasheets/27128A.pdf) datasheet -- the closest match I could find online.
[27128A](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/datasheets/27128A.pdf) datasheet -- the closest match I could find online.
![<img src="http://archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_ROM_V2_Breadboard-640.jpg" alt="Compaq DeskPro 386 System ROM Version 2"/>](http://archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_ROM_V2_Breadboard.jpg)
![<img src="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_ROM_V2_Breadboard-640.jpg" alt="Compaq DeskPro 386 System ROM Version 2"/>](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/reference/compaq/images/Compaq_DeskPro_386-16_System_ROM_V2_Breadboard.jpg)
On my first dump attempt, every ROM address returned 0xFF. After looking at the 27128A datasheet more closely,
I noticed the DEVICE OPERATION table indicated that, for a READ operation, /CE and /OE pins should be connected to

4
devices/pcx86/rom/compaq/portable/README.md
View file

@ -9,7 +9,7 @@ Compaq Portable Computer ROMs
The oldest COMPAQ Portable Computer ROM I have is an 8Kb [Rev C ROM](100666-001-REVC.json) from a REV D system board.
[<img src="http://archive.pcjs.org/pubs/pc/reference/compaq/images/COMPAQ_Portable_System_Board.jpg" alt="Compaq Portable System Board REV D"/>](http://archive.pcjs.org/pubs/pc/reference/compaq/images/COMPAQ_Portable_System_Board-FULL.jpg)
[<img src="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/reference/compaq/images/COMPAQ_Portable_System_Board.jpg" alt="Compaq Portable System Board REV D"/>](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/reference/compaq/images/COMPAQ_Portable_System_Board-FULL.jpg)
Printed on the back of the system board:
@ -25,7 +25,7 @@ my board contains two. Do the contents of the second ROM show up in a different
I'm someday able to power and test this board, I may never know.
Some clues can be found in this
[COMPAQ Portable/Plus Maintenance Guide (Excerpt)](http://archive.pcjs.org/pubs/pc/reference/compaq/portable/Compaq_Portable_Plus_Support_Discontinued.pdf).
[COMPAQ Portable/Plus Maintenance Guide (Excerpt)](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/pc/reference/compaq/portable/Compaq_Portable_Plus_Support_Discontinued.pdf).
Older (REV B) system boards apparently *did* require 2 ROMs, at locations U40 and U47. REV C and later system boards
required only 1 (REV C or later) ROM at location U40.

2
devices/pcx86/video/compaq/vga/README.md
View file

@ -9,7 +9,7 @@ COMPAQ Video Graphics Controller (VGA)
This is the COMPAQ Video Graphics Controller Board, one of the earliest VGA boards COMPAQ released
for its DeskPro 386 line.
[<img src="http://archive.pcjs.org/devices/pcx86/video/compaq/vga/109360-001/Compaq_VGA_109360-001-640.jpg" alt="COMPAQ VGA Board"/>](http://archive.pcjs.org/devices/pcx86/video/compaq/vga/109360-001/Compaq_VGA_109360-001.jpg)
[<img src="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/video/compaq/vga/109360-001/Compaq_VGA_109360-001-640.jpg" alt="COMPAQ VGA Board"/>](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/video/compaq/vga/109360-001/Compaq_VGA_109360-001.jpg)
It was featured in the February 16, 1988 of PC Magazine (p.188). At that time, it retailed for $599, and it was described
as "the sharpest, fastest IBM-standard video board you can slide into your PC." The article goes on to say:

2
devices/pcx86/video/ibm/ega/README.md
View file

@ -58,7 +58,7 @@ The symbol information in the MAP file will be automatically converted and appen
The PCjs server's Dump API can be used as well:
http://www.pcjs.org/api/v1/dump?file=http://archive.pcjs.org/devices/pcx86/video/ibm/ega/1984-09-13/ibm-ega.rom&format=bytes&decimal=true
http://www.pcjs.org/api/v1/dump?file=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/video/ibm/ega/1984-09-13/ibm-ega.rom&format=bytes&decimal=true
### IBM EGA Font Information

2
devices/pcx86/video/ibm/vga/README.md
View file

@ -56,6 +56,6 @@ The symbol information in the MAP file will be automatically converted and appen
The PCjs server's Dump API can be used as well:
http://www.pcjs.org/api/v1/dump?file=http://archive.pcjs.org/devices/pcx86/video/ibm/vga/1986-10-27/ibm-vga.rom&format=bytes&decimal=true
http://www.pcjs.org/api/v1/dump?file=https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/video/ibm/vga/1986-10-27/ibm-vga.rom&format=bytes&decimal=true
The disassembled contents of the 1986-10-27 ROM from the IBM PS/2 Display Adapter is available [here](1986-10-27/ibm-vga.asm).

2
devices/pcx86/video/paradise/vga/README.md
View file

@ -9,7 +9,7 @@ Paradise VGA Board: WDVGA PLUS 16
This Paradise VGA board was manufactured in 1988 and sold by Western Digital Corporation as a **WDVGA PLUS 16**, Model No. 61-603023-02.
[<img src="http://archive.pcjs.org/devices/pcx86/video/paradise/vga/Paradise_VGA_1988-640.jpg" alt="Paradise VGA Board"/>](http://archive.pcjs.org/devices/pcx86/video/paradise/vga/Paradise_VGA_1988.jpg)
[<img src="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/video/paradise/vga/Paradise_VGA_1988-640.jpg" alt="Paradise VGA Board"/>](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/devices/pcx86/video/paradise/vga/Paradise_VGA_1988.jpg)
A copy of the board's [ROM BIOS](1988-05-23.json) was created by [dumping](/devices/pcx86/rom/compaq/deskpro386/#dumping-the-roms)
the contents of each of the board's two M27128AZB PROMs to a *.hex* file, and then merging the *.hex* files with the following

2
devices/pdp11/machine/1170/4mb/README.md
View file

@ -7,7 +7,7 @@ machines:
type: pdp11
autoMount:
RL0:
path: http://archive.pcjs.org/disks/dec/rl01k/RL01K-RSTS-V70.json
path: https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rl01k/RL01K-RSTS-V70.json
---
{% include machine.html id="test1170" %}

2
devices/pdp11/machine/1170/4mb/debugger/README.md
View file

@ -9,7 +9,7 @@ machines:
autoStart: true
autoMount:
RL0:
path: http://archive.pcjs.org/disks/dec/rl01k/RL01K-RSTS-V70.json
path: https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rl01k/RL01K-RSTS-V70.json
---
{% include machine.html id="test1170" %}

2
devices/pdp11/machine/1170/panel/debugger/README.md
View file

@ -33,7 +33,7 @@ For more full-featured PDP-11/70 machines that also include a Debugger, see:
Toggle-Ins
----------
As DEC notes in the [PDP-11/70 Maintenance Service Guide](http://archive.pcjs.org/pubs/dec/pdp11/1170/PDP1170_Maintenance_Service_Guide_Apr88.pdf),
As DEC notes in the [PDP-11/70 Maintenance Service Guide](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/dec/pdp11/1170/PDP1170_Maintenance_Service_Guide_Apr88.pdf),
Chapter 4: "There are several useful toggle-ins that are probably not very well known." Excerpts are provided below. If you're
not sure how to "toggle in" code using a Front Panel, check out [Front Panel Basics](/devices/pdp11/panel/1170/#front-panel-basics).

2
devices/pdp11/machine/1170/panel/debugger/rsts/README.md
View file

@ -10,7 +10,7 @@ machines:
autoStart: true
autoMount:
RL0:
path: http://archive.pcjs.org/disks/dec/rl01k/RL01K-RSTS-V70.json
path: https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rl01k/RL01K-RSTS-V70.json
---
This machine is ready to boot [RSTS/E v7.0](/disks/dec/rl01k/rstsv70/) ("BOOT RL0").

4
devices/pdp11/machine/1170/panel/debugger/rt11/README.md
View file

@ -10,9 +10,9 @@ machines:
autoStart: true
autoMount:
RK0:
path: http://archive.pcjs.org/disks/dec/rk03/RK03-RT11-V40.json
path: https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rk03/RK03-RT11-V40.json
RL0:
path: http://archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json
path: https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json
PTR:
path: /apps/pdp11/tapes/absloader/DEC-11-L2PC-PO.json
---

2
devices/pdp11/machine/1170/panel/debugger/xxdp/README.md
View file

@ -10,7 +10,7 @@ machines:
autoStart: true
autoMount:
RL0:
path: http://archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json
path: https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json
sticky: top
machineScripts:
runEKBAD0: |

2
devices/pdp11/panel/1145/README.md
View file

@ -17,7 +17,7 @@ Use this [PDP-11/45](/devices/pdp11/machine/1145/panel/debugger/) to see the
Front Panel Basics
------------------
From the [PDP-11/45 Handbook (1973)](http://archive.pcjs.org/pubs/dec/pdp11/1145/PDP1145_Handbook_1973.pdf),
From the [PDP-11/45 Handbook (1973)](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/dec/pdp11/1145/PDP1145_Handbook_1973.pdf),
Chapter 8, p. 195:
> ### THE SYSTEM OPERATOR'S CONSOLE

2
devices/pdp11/panel/1170/README.md
View file

@ -16,7 +16,7 @@ Use this [PDP-11/70](/devices/pdp11/machine/1170/panel/debugger/) to see the [PD
Front Panel Basics
------------------
From the [PDP-11/70 Handbook (1979)](http://archive.pcjs.org/pubs/dec/pdp11/1170/PDP1170_Handbook_1979.pdf), Chapter 10,
From the [PDP-11/70 Handbook (1979)](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/dec/pdp11/1170/PDP1170_Handbook_1979.pdf), Chapter 10,
p. 325:
> ### CONSOLE OPERATION

2
devices/pdp11/pc11/README.md
View file

@ -45,5 +45,5 @@ used to control the device, such as choosing which tape should be "loaded" into
</device>
```
For details about the PC11 hardware, we relied upon the [PDP-11 Peripherals Handbook (1976)](http://archive.pcjs.org/pubs/dec/pdp11/other/PDP11_Peripherals_Handbook_1976.pdf),
For details about the PC11 hardware, we relied upon the [PDP-11 Peripherals Handbook (1976)](https://s3-us-west-2.amazonaws.com/archive.pcjs.org/pubs/dec/pdp11/other/PDP11_Peripherals_Handbook_1976.pdf),
p. 4-376 (p. 408 of the PDF).

4
devices/pdp11/rk11/README.md
View file

@ -34,12 +34,12 @@ used to control the device, such as choosing which disks should be "auto-mounted
```xml
<?xml version="1.0" encoding="UTF-8"?>
<device id="rk11" type="rk11" autoMount='{RK0:{path:"http://archive.pcjs.org/disks/dec/rk03/RK03-XXDP.json"}}' pos="left" width="35%" padLeft="8px" padBottom="8px">
<device id="rk11" type="rk11" autoMount='{RK0:{path:"https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rk03/RK03-XXDP.json"}}' pos="left" width="35%" padLeft="8px" padBottom="8px">
<name>Disk Drive Controls</name>
<control type="container">
<control type="list" binding="listDrives"/>
<control type="list" binding="listDisks">
<disk id="disk01" name="XXDP+ Diagnostics" path="http://archive.pcjs.org/disks/dec/rk03/RK03-XXDP.json"/>
<disk id="disk01" name="XXDP+ Diagnostics" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rk03/RK03-XXDP.json"/>
</control>
<control type="button" binding="loadDisk">Load</control>
<control type="button" binding="bootDisk">Boot</control>

4
devices/pdp11/rl11/README.md
View file

@ -38,12 +38,12 @@ used to control the device, such as choosing which disks should be "auto-mounted
```xml
<?xml version="1.0" encoding="UTF-8"?>
<device id="rl11" type="rl11" autoMount='{RL0:{path:"http://archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json"}}' pos="left" width="35%" padLeft="8px" padBottom="8px">
<device id="rl11" type="rl11" autoMount='{RL0:{path:"https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json"}}' pos="left" width="35%" padLeft="8px" padBottom="8px">
<name>Disk Drive Controls</name>
<control type="container">
<control type="list" binding="listDrives"/>
<control type="list" binding="listDisks">
<disk id="disk01" name="XXDP+ Diagnostics" path="http://archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json"/>
<disk id="disk01" name="XXDP+ Diagnostics" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rl02k/RL02K-XXDP.json"/>
</control>
<control type="button" binding="loadDisk">Load</control>
<control type="button" binding="bootDisk">Boot</control>

18
devices/pdp11/rx11/README.md
View file

@ -47,15 +47,15 @@ used to control the device, such as choosing which disks should be "auto-mounted
<control type="container">
<control type="list" binding="listDrives"/>
<control type="list" binding="listDisks">
<disk id="disk01" name="RT-11 V3 SYS (1 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-1.json"/>
<disk id="disk01" name="RT-11 V3 SYS (2 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-2.json"/>
<disk id="disk01" name="RT-11 V3 SYS (3 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-3.json"/>
<disk id="disk01" name="RT-11 V3 SYS (4 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-4.json"/>
<disk id="disk01" name="RT-11 V3 SYS (5 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-5.json"/>
<disk id="disk01" name="RT-11 V3 SYS (6 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-6.json"/>
<disk id="disk01" name="RT-11 V3 SYS (7 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-7.json"/>
<disk id="disk01" name="RT-11 V3 SYS (8 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-8.json"/>
<disk id="disk01" name="RT-11 V3 SYS (9 OF 9)" path="http://archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-9.json"/>
<disk id="disk01" name="RT-11 V3 SYS (1 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-1.json"/>
<disk id="disk01" name="RT-11 V3 SYS (2 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-2.json"/>
<disk id="disk01" name="RT-11 V3 SYS (3 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-3.json"/>
<disk id="disk01" name="RT-11 V3 SYS (4 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-4.json"/>
<disk id="disk01" name="RT-11 V3 SYS (5 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-5.json"/>
<disk id="disk01" name="RT-11 V3 SYS (6 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-6.json"/>
<disk id="disk01" name="RT-11 V3 SYS (7 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-7.json"/>
<disk id="disk01" name="RT-11 V3 SYS (8 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-8.json"/>
<disk id="disk01" name="RT-11 V3 SYS (9 OF 9)" path="https://s3-us-west-2.amazonaws.com/archive.pcjs.org/disks/dec/rx01/RX01-RT11-V03-9.json"/>
</control>
<control type="button" binding="loadDisk">Load</control>
<control type="button" binding="bootDisk">Boot</control>