Charles writes: > The RS M100 Assembler / Debugger application documentation has a brief >appendix of ROM routines, listing purpose, entry and exit conditions and >addresses, but unfortunately incomplete. One new objective is to find a >complete listing, hopefully commented
I would suggest starting with Robert Covington's M100 ROM map (it comes in 7 parts, plus another file on ports/registers) available at http://www.club100.org/library/libref.html under the heading "Maps and List". Here's a typical entry: 190FH - Read time from system clock and store it in the buffer pointed to by HL Entry: HL - Points to start of time buffer. The buffer will be filled with the time in the format hh:mm:ss. Exit: HL - Incremented to the end of the buffer. All other registers destroyed There's also two *REALLY* good and well commented Model 100 ROM disassemblies on Club100 at http://www.club100.org/memfiles/index.php?&direction=0&order=&directory=Ken%20Pettit/M100%20ROM%20Disassembly Also check out "Hidden Powers of the Model 100" and " Inside the TRS-80 Model 100" available at http://www.club100.org/library/libdoc.html Once you get to those Club100 pages, you'll probably find more stuff that's interesting to you. Regards, Douglas On Fri, Apr 30, 2021 at 12:37 PM Charles Hudson <[email protected]> wrote: > Thanks, Peter, for your explanation of the memory segmentation issue; the > fact that there is no 80C85 Jump Relative opcode and thus no relocation was > unknown to me. As you may deduce my depth on the M100 is pretty shallow. > Until recently I had only the bar code reader software to play with (other > than the ROM suite) and my bar code reader seems to be DOA, so not much > familiarity with machine code. > > The RS M100 Assembler / Debugger application documentation has a brief > appendix of ROM routines, listing purpose, entry and exit conditions and > addresses, but unfortunately incomplete. One new objective is to find a > complete listing, hopefully commented, such as the one I have for my Model > III ROM. > > Another objective is to develop a reliable method for tape duplication > before I damage or wear out the OEM distributions. I am thinking it might > be possible to make a digital copy of the OEM tape on my Win10 machine, > using a hi-fi tape deck as the playback source and Audacity as the DTR. > With luck reversing the roles will yield a functional copy tape. But > again, if someone has a better idea... > > Thanks again for your input. > -CH- >
