pcjs/disks at 7095cbea87f24d289bfbfbf166b68bce9b85ec4d - Retro/pcjs

Retro/pcjs

Watch

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
Jeff Parsons b54253acf9 Numerous changes to make paper tape configurations more consistent with disk configurations. This allows all devices to share the machine-wide "autoMount" configuration object, now that the PC11 has a proper device name ("PTR"), making its properties distinguishable from those for RK11 and RL11 drives (eg, "RK0", "RL0", etc). And all the tape/disk components now use "Load" functions to connect a tape or disk to a device ("Attach" is deprecated). And finally, all tape/disk components now support operations to deposit their media directly into memory -- although in this case, the names of the operations are necessarily different: "Read" for tape images, "Boot" for disk images. The difference is partly historical convention but also reflects the fact that a "Boot" operation is more limited: paper tapes were designed to be completely loaded into memory, whereas bootable disks are designed for only the first sector to be loaded and executed. Also, paper tape images are now flagged as non-auto-starting, because they often require some user action (eg, loading another tape, setting some switches, etc), whereas disk boot sectors are flagged as auto-starting (see the fStart parameter of the loadImage() interface in the RAM component).		2016-12-03 14:49:51 -08:00
..
c1p	Lots of tweaks in advance of PDPjs support for loading tape files	2016-10-17 15:19:01 -07:00
dec	Updated the PDP-11 SerialPort to support ALT-ENTER for LINE-FEED and ALT-DELETE for BACKSPACE, to stay in step with VT100 shortcuts	2016-11-27 13:48:23 -08:00
pcx86	Numerous changes to make paper tape configurations more consistent with disk configurations. This allows all devices to share the machine-wide "autoMount" configuration object, now that the PC11 has a proper device name ("PTR"), making its properties distinguishable from those for RK11 and RL11 drives (eg, "RK0", "RL0", etc). And all the tape/disk components now use "Load" functions to connect a tape or disk to a device ("Attach" is deprecated). And finally, all tape/disk components now support operations to deposit their media directly into memory -- although in this case, the names of the operations are necessarily different: "Read" for tape images, "Boot" for disk images. The difference is partly historical convention but also reflects the fact that a "Boot" operation is more limited: paper tapes were designed to be completely loaded into memory, whereas bootable disks are designed for only the first sector to be loaded and executed. Also, paper tape images are now flagged as non-auto-starting, because they often require some user action (eg, loading another tape, setting some switches, etc), whereas disk boot sectors are flagged as auto-starting (see the fStart parameter of the loadImage() interface in the RAM component).	2016-12-03 14:49:51 -08:00
README.md	Merged gh-pages README updates	2016-11-08 08:20:32 -08:00

README.md

layout	title	permalink
page	Disk Libraries	/disks/

Disk Libraries

Browse these PCjs Disk Libraries:

Additional selected software is available in the PCjs Software Archives.

PCx86 Disk Image Formats

PCx86 works best with disk images in a JSON format, to save conversion time, so that's the only disk image format you'll find in the PCjs Project.

If you're running the PCjs Node web server, you can convert any of our JSON disk images into an IMG file with the DiskDump API, by setting the format parameter set to img instead of json. For example:

{{ site.url }}/api/v1/dump?disk=/disks/pcx86/dos/ibm/2.00/PCDOS200-DISK1.json&format=img

As an added bonus, the PCjs Node web server automatically provides "onclick" handlers for all links to JSON-encoded disk images, automatically invoking the API for you.

See Creating PCx86-Compatible Disk Images in the PCx86 Documentation for more information about supported disks and formats.