The package documentation should have come with instructions on how to use the computer and cassette recorder to make a "working copy" of the cassette. You need a blank cassette, and using the CLOADM / SAVEM, CLOAD / SAVE commands to make a duplicate of the original cassette, one file at a time. A little tedious, but that is how it was done "in the day". At least it could be a near term solution, if all you have is the computer and a cassette recorder and want to preserve your original cassette.
For owners that had a Model 1, 2, 3 or 4, and were using it as a primitive "file server" (via ASCII transfers over the serial port) instead of the cassette recorder, several people wrote BASIC programs to read a .CO program from memory, and convert to DATA statements in a small BASIC "loader" program. This "loader" program was used to "re-load" the .CO program back into the Model 100 computers memory. This process was used because initially when the Model 100 was introduced, it could only load/save .CO or .BA files in their native Binary format to the cassette recorder, and real "file server" programs with a "transfer protocol" didn't exist. It wasn't until a few years later that the TPDD (Tandy Personal Disk Drive) was introduced, which made using the Model 100 more like the other computers with disk drives. It did require a "driver" in RAM that contained the file transfer protocol, which had to be "unloaded" before most .CO programs could be run. Regards, Peter Message: 4 > Date: Fri, 30 Apr 2021 13:37:23 -0400 > From: Charles Hudson <[email protected]> > To: [email protected] > Subject: [M100] Memory release question > Message-ID: > <CAAbv=MAKwYoZdMkjO9h4-mKDgjFLVYK-Rf= > [email protected]> > Content-Type: text/plain; charset="utf-8" > > 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- > >
