From 36f48a3c3ccb8e8e1a204117b2f647aa0baf38fc Mon Sep 17 00:00:00 2001 From: Matthias Koch Date: Mon, 2 Jan 2023 18:13:54 +0100 Subject: [PATCH] Readme Links in Readme Links in Readme, corrected fix typo --- datapoint/README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 datapoint/README.md diff --git a/datapoint/README.md b/datapoint/README.md new file mode 100644 index 0000000..680f4c6 --- /dev/null +++ b/datapoint/README.md @@ -0,0 +1,17 @@ +Datapoint font +============== + +This directory contains the ROM font of the Datapoint 8600. + +ROM images were read out by the crew of the museum of computer history in Visselhövede, Germany, and are provided here: + +[905-007-1.bin](https://mecrisp.sourceforge.net/Datapoint/905-007-1.bin) +[905-008-1.bin](https://mecrisp.sourceforge.net/Datapoint/905-008-1.bin) + +The font data is in 905-008-1.bin and starts at $10AF. + +Font data in the ROM image is not directly mapped as a character generator but is read by the "bios" of the machine and stored into the actual character RAM area. The font is a 8x12 font, but only uppercase characters were available, with the lowercase characters later loaded by the operating system (RMS 2.8.J) for which unfortunately no data exists. + +The font data is organised as nine bytes for each character, with the MSB of these data bytes always 0 for inter-character spacing. Therefore, data exists for 7x9 bitmaps. Three empty lines are added when loading this font, one line on top and two lines at the bottom as seen when comparing with the cursor on the real machine in which has all twelve lines set. + +Bytes with MSB set denote the place in the character table (when masked with $7F). Then nine bytes of graphics data follow.