New software for the K2000: phase 1 accomplished

Hi everybody,
 

 it is with great pleasure that I share that the first phase of my projects is over.
 

 The first step is, of course, to obtain the software (EPROM contents) one wants to modify.
 

 In order to do this, I borrowed my son's arduino, and built my first ever arduino project: an EPROM reader!
 

 It definitely took some time to build and program, and debug; but in the end it seems to be working fine.
 

 Dumping one OS ROM chip takes 3 min; one SETUP ROM chip, 1min 30; and the scanner EPROM chip, around 20 s.
 

 I may post details, and/or some pointers, for people who could be interested in replicating the experiment.
 

 I dumped the contents of the chips inside my K2000, so here we go with the versions:
 OS ROM: 3.87J
 Setup: V 1.30
 Scanner: V 14
 

 I have not done much more. I just spent some time comtemplating the HEX of the ROM, looking for "empty space" that could be put to use for new content. Apparently, roughly 1/4th of the chips is unused. If this estimation is correct, then it is great news: it is probably much more space than we will ever need.
 

 I did the same for the scanner EPROM: 1/8th of it is definitely unused. But since this 1/8th is at the very beginning, one may ask: is it really usable?
 

 Today, the scanner is not the priority; finding my way in the OS code would rather be it.
 

 ***
 I am looking for additional documentation with respect to what everybody can easily find online: a 133 pages version of a document called "The K2000/K2000R service manual". This document is incomplete. It is only mentioning the Calvin chip, never Janis; it has a nice "audio board theory" section, but no such thing about the engine board (although I cannot be sure such exists in a more complete version); also the parts listing is missing; and finally, either the printing was bad, or the scanning process was not of the best quality; the result being that deciphering the symbols on the lines of the schematics is not always easy.
 

 Now I am really grateful for having this document, with all its limitations: what I learnt with its help I probably couldn't learn without it.
 

 But if some good soul had a better scan, or better still, a complete version of the document, I would be very much interested.
 

 Any pointers to additional documentation, be it from Kurzweil, or general-purpose books, articles, would be warmly welcome.
 

 You may write at [email protected] if you want to start a private exchange of messages.
 

 Thank you for reading,
 

 Yann