- After switching on the machine, the screen is supposed to stay dark, the "Floppy nicht bereit !" (floppy not ready message) is therefore "wrong" (but obviously present in the ROM).

- the serial port, timers/counters, iterrupt and daisy chain logic and some 256bytes of RAM are done using a MK3886 chip

- I have never seen mention of a 512K RAM card, only 64K or 256K

- banking: "You can access C000-FFFF on any of the activated banks 0-7 from the internal bank 8 without switching. This facilitates the exchange of common data" (service manual, p.17, this also has the values for selecting the pages via OUT F6H

- something about incomplete address decoding (and the subsequent repetition of memory regions) as well as the relation between main memory and (screen buffer?) memory on the video combination interface on p.50-52 of the service manual

- banking: "You can access C000-FFFF on any of the activated banks 0-7 from the internal bank 8 without switching. This facilitates the exchange of common data" (service manual, p.17, this also has the values for selecting the pages via OUT F6H

The 256K manual seems to imply the c000-ffff region is static and the 256K CPM on the ITT and SYS floppy images won't boot unless it's like that. Those images also currently hang if you try to run a command that doesn't exist, looks to be a fdc hookup issue. I added the screen color to try and match the image you posted earlier but it might be better for you to tweak by comparing to the screen directly rather than though a photograph.

crazyc, I think you matched the colour of that particular monitor very well!

Rene, thanks for the translation.

The keyboard's vexing: Shift-lock works, shift doesn't, but there seems to be no correlation between the position of the keys in the MAME source and the keyboard matrix in the "technical information" document.

One thing I found though is that special keys like SHIFT or CTRL are not special to the keyboard, but send their codes as any other key (service manual p.163).

Sometimes right after a reset, you have to press "B" twice before the keypress is registered, but the surplus b then shows up on the CP/M prompt.

This resounds with a tendency of the driver to "eat" keypresses, e.g. in the file select dialog where you sometimes have to press the arrow keys or Enter twice to register.

If you boot 3030inf0.td0, only every other keypress produces visible results, but spits out the previous character as well - don't know if those two phenomena are related.