Hi, thanks :) Your gentle encouragement led to this: https://archive.org/details/trs-80-m100-norwegian
Regards, Rune Devik On Sun, Jan 25, 2026 at 8:02 AM B 9 <[email protected]> wrote: > Wow, great job with the documentation! Once you’re finished, I'd like to > gently encourage you to consider storing it also on archive.org. > > For deskewing the pamphlet images, you can do it when converting to PDF. > In particular, the ocrmypdf command has a --deskew option. This is what I > did on my Unix computer: > > *img2pdf* --title "TRS 80 Modell 100: Kortfattet brukerveiledning" \ > --keywords "TRS-80, m100, Norvegian" \ > --creationdate "January 01, 1984" \ > Pamphlet*.png \ > | *ocrmypdf* --deskew - pamphlet.pdf > > By the way, it may make sense to add the original JPEG photos to the > repository. PDFs usually work best with JPEG or TIFF images, not PNG, as no > conversion is necessary. > > And, yes, the soigeneris Backpack looks quite nifty. I don’t have one yet, > but plan on getting one whenever they are back in stock. > > —b9 > > On January 24, 2026 11:24:01 AM PST, Rune Devik <[email protected]> > wrote: > > That universal backpack looks nice :) >> >> I'm almost finished documenting my machine, the box it came with, the >> pamphlet, Cassette (not yet recorded but...), ROM etc. And I have put >> everything up on GitHub for now (of all places..): >> https://github.com/Warshi7819/TRS80-M100-Norwegian >> >> Regards, >> Rune Devik >> >> On Sat, Jan 24, 2026 at 2:09 AM B 9 <[email protected]> wrote: >> >>> The double cassette deck sounds like the way to go. I don't know about >>> testing the .wav file out, other than just playing it back from your >>> computer and loading it on your Model T. If you need to do it in emulation, >>> a good bet is to try MAME's tandy102 as that emulates the device at the >>> chip level. >>> >>> If you are not so fond of cassettes any more, you may want to >>> investigate getting a REX# chip or a Universal Backpack >>> <https://www.soigeneris.com/universal-backpack-drive>. I held off for a >>> long time because I wanted to experience the way computing was "back in the >>> day", but eventually, it just made more sense to get one of the modern >>> solutions. >>> >>> —b9 >>> >>> >>> >>> On Fri, Jan 23, 2026 at 12:59 PM Rune Devik <[email protected]> >>> wrote: >>> >>>> Hi! >>>> >>>> Thanks for the transformed dump :) >>>> >>>> I have a new double cassette deck at my cabin (three years old) so I >>>> was thinking about bringing in that bad boy to dump the tape. Is there >>>> software that can take a wav file and create a cas file for the trs-80 >>>> model 100? And is it possible to load a cas file on the emulator (Virtual >>>> T) to test that the dump actually works? >>>> >>>> The belts I bought was for the specific model I have (Philips D6280). >>>> And they seemed good. A lot tighter than the once I had initially at least >>>> but not too tight either. But the speed of the cassette deck is still going >>>> up and down.. Could be slipping as you say. You can hear it very well when >>>> playing music cassettes on it. And I was not able to record and load a >>>> short program on my trs-80 coco (or was it the Dragon) with it either so >>>> it's not doing it's job it seems. I'm not sure I like cassettes for >>>> software. Me, cassettes and Azimuth head alignment go way back as nobody in >>>> Europe could afford floppies back in the 80's... :) >>>> >>>> >>>> On Fri, Jan 23, 2026 at 9:32 PM B 9 <[email protected]> wrote: >>>> >>>>> By the way, a slow speed recording can be easily corrected as long as >>>>> it is consistent. If I remember right, the TRS-80 audio data format starts >>>>> with a tone of a specific frequency, making it relatively easy to see (in >>>>> Audacity's spectrum mode) if the speed is steady and how much of an >>>>> adjustment is needed. If your cassette deck isn't having other problems, >>>>> like chewing up tapes, I think it'd be worth a shot uploading the >>>>> incorrect >>>>> speed. >>>>> >>>>> I would not suspect capacitors or the motor for the speed problem, at >>>>> least, not at first. Did you buy a replacement belt of exactly the same >>>>> size as the old belt? If so, it likely would be too loose since they get >>>>> stretched out. Another problem I've seen is the rubber of the pinch roller >>>>> hardening to a glaze and slipping. >>>>> >>>>> —b9 >>>>> >>>>> On Fri, Jan 23, 2026 at 4:30 AM Rune Devik <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> So, attached is the dump of the ROM. The file romdump_real.txt is the >>>>>> output from running Clinton's basic script. The output_hex.txt file is my >>>>>> creation by extracting all the numbers from the romdump_real.txt file and >>>>>> then converting the numbers to hex pairs using python format(int(value), >>>>>> '02X') >>>>>> >>>>>> I was kinda expecting that I would find some version info or some >>>>>> ascii text in the rom dump but browsing through it I didn't see anything >>>>>> like that in my hex editor. >>>>>> >>>>>> Anyways, please share any insights you might get when looking at >>>>>> these dumps :). >>>>>> >>>>>> Also back to another of B9's questions: Yes, I have the cassette that >>>>>> came with the unit as well but I haven't recorded it yet. Basically >>>>>> because >>>>>> my cassette deck I have at hand is not behaving correctly at the moment. >>>>>> I >>>>>> haven't had the time to fix it yet. The motor is not running at full >>>>>> speed >>>>>> (I have changed the belts) so either caps or the motor itself. The M100 >>>>>> also came with a Norwegian pamphlet and the full hefty Tandy M100 manual >>>>>> (in English). I will try to scan the Norwegian pamphlet and share that on >>>>>> arhive.org as well. >>>>>> >>>>>> Regards, >>>>>> Rune Devik >>>>>> >>>>>> On Fri, Jan 23, 2026 at 11:30 AM Rune Devik <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi >>>>>>> >>>>>>> Also verified that >>>>>>> * PEEK(63789) returns Year (ones place) >>>>>>> * PEEK(63790) returns Year (tens place) >>>>>>> >>>>>>> Just like the US and UK model in your table. >>>>>>> >>>>>>> On Fri, Jan 23, 2026 at 11:24 AM Rune Devik <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> Unfortunately PEEK(1) returns 167 on my Norwegian model as well. >>>>>>>> Which means that it's probably based on the American version and that >>>>>>>> is >>>>>>>> also indicated by the sticker on the back where it says "Custom mfd. in >>>>>>>> Japan for Tandy Corporation". But as stated before the date format is >>>>>>>> DD/MM/YY. >>>>>>>> >>>>>>>> I'll send the full dump of the ROM as soon as I have had the time >>>>>>>> to do it! >>>>>>>> >>>>>>>> Regards, >>>>>>>> Rune Devik >>>>>>>> >>>>>>>> On Fri, Jan 23, 2026 at 10:34 AM B 9 <[email protected]> wrote: >>>>>>>> >>>>>>>>> Did you send the value from PEEK? That file contains this >>>>>>>>> repeating sequence: >>>>>>>>> >>>>>>>>> ``` >>>>>>>>> 00 >>>>>>>>> 01 >>>>>>>>> 02 >>>>>>>>> 03 >>>>>>>>> 04 >>>>>>>>> … >>>>>>>>> FC >>>>>>>>> FD >>>>>>>>> FE >>>>>>>>> FF >>>>>>>>> ``` >>>>>>>>> >>>>>>>>> Oddly symmetric indeed! >>>>>>>>> >>>>>>>>> —b9 >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jan 22, 2026 at 4:39 PM Rune Devik <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi >>>>>>>>>> >>>>>>>>>> After reducing the speed to 1200 bauds I finally managed to dump >>>>>>>>>> the rom but I think this script dumps the *optional* rom? And >>>>>>>>>> not the "main" rom? It dumped the data but it seemed strangely >>>>>>>>>> symetric >>>>>>>>>> when I saw the data pass by lie it was repeating itself over and >>>>>>>>>> over so >>>>>>>>>> not sure there's actually any info there. Which makes sense as there >>>>>>>>>> is no >>>>>>>>>> optional rom installed. Or I might be completely wrong and this is >>>>>>>>>> it. I >>>>>>>>>> could not make sense of it in a hex editor either... But this is not >>>>>>>>>> my >>>>>>>>>> expertise so any help appreciated :) >>>>>>>>>> >>>>>>>>>> At least the file is exactly the correct size as it should be. >>>>>>>>>> >>>>>>>>>> On Thu, Jan 22, 2026 at 7:05 PM Joshua O'Keefe < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> > On Jan 22, 2026, at 7:43 AM, Joshua O'Keefe < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> > >>>>>>>>>>> > I'm fairly sure I've seen software to do this posted here on >>>>>>>>>>> the list in the past. I'd be willing to bet Stephen A. has >>>>>>>>>>> something on >>>>>>>>>>> hand because this is very much his wheelhouse. >>>>>>>>>>> >>>>>>>>>>> Curiosity got the better part of me. Stephen does have such a >>>>>>>>>>> utility posted[1] that ought to work with a USB/RS-232 bridge on >>>>>>>>>>> the other >>>>>>>>>>> end. It produces a hex dump rather than binary data, so you might >>>>>>>>>>> need to >>>>>>>>>>> poke around for a utility to decode ASCII hex pairs to binary. >>>>>>>>>>> >>>>>>>>>>> [1] >>>>>>>>>>> https://www.club100.org/memfiles/index.php?&direction=0&order=&directory=Steve%20Adolph/ROM2S >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> mvh, >>>>>>>>>> Rune Devik >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> mvh, >>>>>>>> Rune Devik >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> mvh, >>>>>>> Rune Devik >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> mvh, >>>>>> Rune Devik >>>>>> >>>>> >>>> >>>> -- >>>> mvh, >>>> Rune Devik >>>> >>> >> >> -- mvh, Rune Devik
