Re: [M100] Model 100 System ROM dload?

[Joshua O'Keefe]

> On Jul 3, 2024, at 5:09 PM, Jim Anderson  wrote:
> 
> I tried visiting several of the pages (including the one for PERIOD) and they 
> all worked with a little bit of URL rewriting.  For instance, the broken link 
> for further info on PERIOD is [...]

Jim, thanks for digging into this a bit deeper, I appreciate it. Since the 
software itself proved so difficult to come by, I've archived it on my bucket 
here:


If I get a chance, I'll try to put together a package of documents from the 
broken website mirror, and get those up on archive.org .



Happy Independence Day to those who partake!

Re: [M100] Model 100 System ROM dload?

[Joshua O'Keefe]

> On Jun 25, 2024, at 6:52 AM, RETRO Innovations  wrote:
> 
> It's a bit disappointing the images were not of some earlier version of
> the OS,

Has any variant of the system ROM been found, at least one that isn't a 
localization or a date hack? It seems like the production ROM sprung 
fully-formed from the forehead of Zeus and remained largely unchanged.

Re: [M100] Model 100 System ROM dload?

[Joshua O'Keefe]

> On Jun 25, 2024, at 2:11 AM, Walt Perko  wrote:
> 
> How about posting the ROM files so they can be shared with others for 
> comparison, or maybe repaing a Modle 100 computer?  

If you simply need a copy of the production ROM, there's a binary that ships 
with VirtualT. I maintain an updated fork with the various unmerged patches and 
fixes (including the ability to run on macOS properly) so the ROMs can be found 
here among other places:


There is a (buildable) disassembly with heavy commentary at:


And another at:


I look forward to seeing if Jim's (as yet unshared) ROM turns out to be the 
same thing.

Re: [M100] Baldur's Gate/ "Dungeon Delver" on Model 100

[Joshua O'Keefe]

Just a quick follow-up on my threat to make a REX .by file image with this game 
already loaded:

It's here:


Just import the BG31.BY file into your REX, switch to it, and CALL 45568
The requisite CLEAR has already been taken care of, since the game is already 
loaded.

In the course of whipping this up, I was able to confirm that, yes indeed, the 
.CO file of the game can be loaded via TS-DOS's "DOS-ON" mode with a simple 
LOADM"0:BG31.CO"

There are no apparent conflicts with the DOS-ON stub in memory, and the game 
runs great! So for those folks without a REX, it's a simple matter to load the 
game from disk.

Re: [M100] CSAVEM bugfix to CloudT

[Joshua O'Keefe]

> On Jun 13, 2024, at 11:22 AM, John R. Hogerhuis  wrote:
> 
> I fixed the bugs... so if I Add File BG31.CO , I can CLOADM 
> and then CSAVEM it back out as a new file, download it, and they hash to the 
> same value.
> 
> -- John.

Thanks for this, John. I'd been planning to validate the CO file being 
generated by the new Makefile in roughly this way, and would have run into 
exactly this bug on CloudT. I appreciate you both fixing the bug and doing the 
validation both!

Re: [M100] Baldur's Gate/ "Dungeon Delver" on Model 100

[Joshua O'Keefe]

> On Jun 12, 2024, at 3:11 PM, John R. Hogerhuis  wrote:
> I opened an issue to request CO files be included. 

While I didn't submit a PR to the engine project, I did submit a PR to the 
"Baldur's Gate" project that updates the build script to produce a CO — and 
validated that the resulting file ran just fine on CloudT.



It's not the most glorious method, since the ORG is hardcoded into the makefile 
rather than divined from the source, but it worked.

Re: [M100] "CIA Adventure" - Ported from Model I to Model 100

[Joshua O'Keefe]

I have patched up some of the bugs reported; note that the game is not 
necessarily fully playable. As a port from a system with a larger screen, some 
text may scroll off the screen. Also be aware that this isn't actually a very 
good game; as I mention in the README, I only ported it because I didn't get a 
chance to finish it as a 9 year-old, and the main port targets qb64, not the 
M100. The intent is to make as pure a port as possible with as few invasive 
changes as I can.

Hint: The TRS-80 Model I was an uppercase-only system. Your caps lock key is 
going to get a workout unless you add a line of code to upcase the input.

Also hint: The first screen offers a suggestion on how to get help: "ORDERS 
PLEASE"

The updated release is at:

Re: [M100] "CIA Adventure" - Ported from Model I to Model 100

[Joshua O'Keefe]

> On Apr 24, 2024, at 9:14 AM, David Plass  wrote:
> 
> Also line 465 says "IF ... PRINT" but it needs a THEN.

> On Wed, Apr 24, 2024 at 12:02 PM Justin Poirier  > wrote:
> I think that some syntax, while not throwing an error, will still need to be 
> fixed to work correctly on the Model 100. An example would be in Line 6, 
> containing the statement R1=RND(9). In some MS BASIC implementations, like 
> the Color Computer, this would return an integer between 1 and 9. But the 
> updated statement on the Model 100 would be R1=INT(RND(1)*9)+1 to get the 
> same 1-9 integer result.

Good catches! Thanks for spotting them! I'll make some fixes to these and 
commit an update.

[M100] "CIA Adventure" - Ported from Model I to Model 100

[Joshua O'Keefe]

Hi folks,

After stumbling over the game on a TRSDOS disk image, I started doing a bit of 
porting work on the game "CIA Adventure" — I had never finished it back in the 
1980 — with the original aim to port to the modern qb64 BASIC compiler. When 
that succeeded, I decided to add on a bonus port to the M100, since the changes 
were about the same.

The whole enchilada is at


But if you just want to get the tokenized BASIC file to try out, or the 
macOS/Windows ports (the Linux build is on the to-do list), they're here:



Enjoy.

Re: [M100] Windows 98 solution for TPDD emulation

[Joshua O'Keefe]

There's also a backport of Framework 3.5 to Windows 9x here:


Utterly fascinating reverse engineering work done to make this possible — 
originally as a backport of Framework 2.0 to Windows 95 — documented here:

Re: [M100] VirtualT mainline source code

[Joshua O'Keefe]

> On Mar 16, 2024, at 10:37 PM, B 9  wrote:
> 
> Is Virtual T no longer being released by the original developers? (Ken Petit? 
> Stephen Hurd?) 

I am not the upstream by any stretch of the imagination, but I am also 
maintaining what I think is the "best of breed" fork with as many of the 
patches and fixes that I've found across all the forks floating around:


I wound up doing this because the current upstream code outright doesn't work 
on macOS, lacks some of the Linux build fixes, and lacks some UI fixes in the 
weird "devterm" fork that forked from an ancient version of upstream. PRs for 
this kind of thing to upstream have gone unanswered for months or years it 
seems?

So while I wouldn't consider myself or declare myself authoritative by any 
means, I absolutely do welcome PRs and promise to merge 'em.

Re: [M100] Adding Gotek to T100 Disk Video Interface

[Joshua O'Keefe]

> On Mar 15, 2024, at 4:03 AM, Gary Wilkinson  wrote:
>  if anyone can help to either describe how I can create a disk image from the 
> T200 DVI floppy disk, or if anyone already has a T200 DVI disk image file 
> that they could supply, then I'd be very grateful!

Steve put in a bunch of effort towards both of these things quite a while back:


The image there (apparently in "dd" type sector dump—probably what you'd want 
to try with a Gotek—as well as the ancient "TeleDisk" format for DOS utilities) 
is described as being the T200/T102/M100 triple-compatibility disk, which I 
would assume is the 26-3806 disk.

Re: [M100] looking for assembler/debugger

[Joshua O'Keefe]

> On Mar 13, 2024, at 1:04 PM, Will Senn  wrote:
> 
> Now, I'm interested and looking for an assembler - help appreciated.

Hi there, Will,

I have a small collection of files that were hard to find anywhere else, and 
that includes "ZBUG" (Radio Shack's 26-3823), which is the Microsoft assembler 
sometimes called EDTASM on other platforms. If you're looking for a native 
platform assembler, it's not a bad choice:


There are several hobbyist-written assemblers out there as well, most written 
in BASIC, and then there's the ML monitor/assembler inside ROM2/Cleuseau, if 
you have a way to load an option ROM.

Re: [M100] Message Database

[Joshua O'Keefe]

> On Mar 9, 2024, at 9:24 PM, Hiraghm  wrote:
> 
> I just noticed that in Thunderbird mailer, I have mailing list entries dating 
> back to 2013.
> 
> I was thinking of going through them, and making a database of topics that 
> people could search for past conversations.

Hi Hiraghm,

The list archive itself, dating back to 2011, is searchable (and downloadable) 
at:
 

While that doesn't provide a topic-based, curated database like you propose, 
it's a great place to start or to expand on your dataset.

Re: [M100] virtualt on Linux problem

[Joshua O'Keefe]

On Feb 25, 2024, at 12:27 PM, Joshua O'Keefe  wrote:
> 
> I've consolidated the various forks and branches of virtualt that are 
> floating around into a single fork:
> < https://github.com/majick/virtualt-code >

As a convenience, I have released precompiled binaries for Linux amd64 and 
macOS aarch64 (sorry if anyone was hoping for Intel macOS binaries — I wasn't 
up to spending time working out how to build dual-arch).  Hiraghm, if you're 
still struggling with either building the program or using someone else's 
binaries, you're welcome to try mine.  The ldd from mine on a Debian bookworm 
box looks like:

$ ldd virtualt
linux-vdso.so.1 (0x7ffd999f9000)
libfltk_images.so.1.3 => /lib/x86_64-linux-gnu/libfltk_images.so.1.3 
(0x77152b6a7000)
libfltk.so.1.3 => /lib/x86_64-linux-gnu/libfltk.so.1.3 
(0x77152b573000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x77152ae0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x77152b121000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x77152ac1f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x77152b551000)
libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 
(0x77152b51b000)
libjpeg.so.62 => /lib/x86_64-linux-gnu/libjpeg.so.62 
(0x77152b08e000)
libXrender.so.1 => /lib/x86_64-linux-gnu/libXrender.so.1 
(0x77152b081000)
libXcursor.so.1 => /lib/x86_64-linux-gnu/libXcursor.so.1 
(0x77152b074000)
libXfixes.so.3 => /lib/x86_64-linux-gnu/libXfixes.so.3 
(0x77152b06b000)
libXext.so.6 => /lib/x86_64-linux-gnu/libXext.so.6 (0x77152b056000)
libXft.so.2 => /lib/x86_64-linux-gnu/libXft.so.2 (0x77152b03c000)
libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x77152abd4000)
libXinerama.so.1 => /lib/x86_64-linux-gnu/libXinerama.so.1 
(0x77152b514000)
libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x77152aa92000)
/lib64/ld-linux-x86-64.so.2 (0x77152b6e7000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x77152b01b000)
libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 
(0x77152a9c7000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x77152a99c000)
libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x77152a972000)
libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 
(0x77152a965000)
libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x77152a95e000)
libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x77152a40)
libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 
(0x77152a93b000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x77152a925000)
libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x77152a918000)

Re: [M100] virtualt on Linux problem

[Joshua O'Keefe]

> On Feb 24, 2024, at 7:04 PM, Hiraghm  wrote:
> 
> Can anyone advise me how to get virtualt working on Linux?

I've consolidated the various forks and branches of virtualt that are floating 
around into a single fork:
< https://github.com/majick/virtualt-code >

On this fork I have combined:
* Fixes to make it compile successfully on Debian with a modern compiler
* Fixes to make it compile properly on macOS / Darwin
* The fix to make the "shifted" keys work on macOS
* Backporting of some of the cosmetic fixes from "virtualt-devterm"

You might have better luck building this version rather than whichever more 
outdated version you were trying to build.

Re: [M100] Tandy TPDD-1 Drive

[Joshua O'Keefe]

> On Jan 11, 2024, at 10:46 AM, Scott Joyce  wrote:
> 
> I recently acquired a TDPP1 drive and just purchased a cable but am now 
> finding I need the Utility/Boot disk.  I would appreciate any help in getting 
> a copy of the disk so I can get this little gem functioning properly again.

Congratulations on scoring the hardware!

One option for getting the disk you want is to make one using pdd.sh:
https://github.com/bkw777/pdd.sh

The repository contains the disk image, and the pdd.sh utility can write it to 
a blank disk using your drive connected to a PC.

There are also other programs available that allow you to use the drive without 
the utility disk at all, such as TS-DOS or TEENSY.  TS-DOS is capable of 
issuing a format command to the drive, enabling you to make usable disks to 
read and write with, and offers quite a lot more functionality than the 
programs on the utility disk.  I don't remember if TEENSY can do disk 
formatting.  Quite a few other "DOS" programs are out there.

Re: [M100] 19.2Kbps on the Tandy 102

[Joshua O'Keefe]

> On Dec 13, 2023, at 1:34 PM, Brian Brindle  wrote:
> 
> building up a CP/M emulation environment on the TanPi

Feel free to reach out about this off-list.  I've done a fair bit of fooling 
around with the various CP/M emulation environments and have found RunCPM to 
work *really* well as a daily driver CP/M subsystem.  Happy to talk about that.

Re: [M100] 19.2Kbps on the Tandy 102

[Joshua O'Keefe]

> On Dec 13, 2023, at 6:22 AM, Brian Brindle  wrote:
> My whole setup is a total kludge / hack that I never expected to use long 
> term. I was just doing a POC and built the whole thing in about 10 minutes 
> with stuff I had laying around but here we are almost five years later... 

Brian, you may consider this rig a kludge, but I'm jealous and think it's 
gorgeous.  Using the T as a portable terminal with a perfectly capable tiny 
Linux box cleverly attached is a great hack.  I wish I had one of these!  A 
9-pin WP-2 version—what with the 80-column display—would be amazing.

Now that I think about it, have you tried using either one of the 80-column 
software setups, like ROM-View 80 or Ultrascreen100?  It might make for an even 
more pleasant terminal experience.

Gosh, I'm tempted to ask if you'd slap another one together in your copious 
free time!

Re: [M100] M100 ergonomics

[Joshua O'Keefe]

> On Dec 10, 2023, at 4:47 PM, runrin  wrote:
> I've found that it's pretty difficult for me to find a comfortable
> position to use my Model 100 for any length of time. I'm always bending 
> forward to get a better view when I sit at a table or desk, and when it's on 
> my lap the lack of palmrest causes the keyboard to slide too close to my body 
> making it hard to type.

When I put it on a desk, I either prop it on "Peg Leggs" (Peter Noeth, a list 
member here, makes carefully crafted legs that work perfectly) or set it on an 
aluminum "laptop stand" that's frankly a bit high for typing for more than a 
few minutes at a time.

Normally, I type with it on my lap.  I have the advantage, though, that I tend 
to sit cross-legged which gives me a bit more room to place the thing.  In 
general, though, I find that regardless of where I place the computer the key 
to avoiding a stiff neck has always been choosing good lighting and carefully 
adjusting the LCD twist.

Re: [M100] M100 ergonomics

[Joshua O'Keefe]

> On Dec 11, 2023, at 4:08 AM, Brian Brindle  wrote:
> I have a hacked together perl script that sends each key press from the Tandy 
> to the X-windows system as keyboard input 


Brian, I remember you mentioning you'd wired up the serial output to XTest in 
some fun way (wrapping xdotool or X11::Protocol::Ext::XTEST maybe?) to do this, 
but I think I lost track of the details.  Did you ever wind up posting your 
glue script?

It'd be really neat to have a straightforward way to listen to ttyS0 and emit 
input events.

Re: [M100] Alternate keymaps on the M100 (and a question about caps lock)

[Joshua O'Keefe]

> On Nov 25, 2023, at 4:54 PM, Stephen Adolph  wrote:
> 
>  I use the Telemark TASM32.  I think you can find it online, not sure.

bergen is a modern open source reimplementation of Telemark TASM, intended as a 
drop-in replacement that runs on modern platforms.  I haven't tested it but it 
looks like a pretty nice project:

https://github.com/kyleedwardsny/bergen
kyleedwardsny/bergen: Free and open-source replacement for the Telemark 
Assembler.
github.com

Re: [M100] Text Sweeper 2.7.3

[Joshua O'Keefe]

> On Nov 25, 2023, at 6:24 AM, ho collo  wrote:
> 
> Yes Ken — A majority of the world still uses windows. What would make you 
> think otherwise?

The vast majority of the planet runs on Unix-like platforms.  Windows is pretty 
much only popular on desktops, which are a tiny fraction of the computers 
people own or use on a daily basis in the modern world.

John was kind enough to create CloudT (see http://bitchin100.com/CloudT ) for 
the convenience of people who don't want to compile and install VirtualT for 
their platform, or who wish to access an emulated system quickly and easily.

I'm happy to report that Text Sweeper 2.7.3 seems to run like a dream on it!

Re: [M100] Model T clock doubler

[Joshua O'Keefe]

> On Nov 23, 2023, at 8:13 AM, Stephen Adolph  wrote:
> 
> If it adds value, getting a linux version would be nice too I think.
> I'm happy to share the files I compiled.

Hey Steve,

I'd love access to the source code to make an attempt at building a Linux 
version.  I'm far from a .Net guy but I suspect the differences on the serial 
port side won't be all that large, and everything else should hopefully be 
"close enough."

Re: [M100] Model T clock doubler

[Joshua O'Keefe]

> On Nov 23, 2023, at 5:27 AM, Stephen Adolph  wrote:
> 
> So now my windows machine has a terminal that obeys M100 screen codes, and 
> character set.

Since you're continuing to use the program, I'm curious how well it's been 
serving you.  Has this version mostly held up when you reach for it?  Your 
humble disclaimer about bugs aside, it sounds like the program has been a 
useful addition to your workflow.

As you might recall, I'm a REXCPM owner, but I've been slow to pull the trigger 
so far on installation -- too many projects on the backlog! -- but if the 
terminal program has been fairly solid day to day that's an enticement to start 
my installation... And to work on trying to fire up the terminal program on the 
other platforms I use.

Re: [M100] Model T clock doubler

[Joshua O'Keefe]

> On Nov 22, 2023, at 9:01 PM, MikeS  wrote:
> 
> MVT100 Windows application???

I think that's referring to this program:
http://club100.org/memfiles/index.php?direction===Steve%20Adolph/MVT100%20for%20PC;
To quote Steve: "This is a Windows program that is serial-fed terminal emulator 
specifically modified to match the M100 screen output. It enables an 80x24 
terminal screen. Compiled on Windows 10 using Visual Studio, based on .NET 4.8. 
Program is very early and possibly quite buggy"

Re: [M100] Convert integer to string WITHOUT leading space?

[Joshua O'Keefe]

> On Jul 9, 2023, at 7:22 PM, John R. Hogerhuis  wrote:
> 
> MID$(STR$(A%),2+(A%<0))

This is a lovely, compact way to address something I’ve used a verbose solution 
for.  Thank you!

Re: [M100] M102 bag trade for m100?

[Joshua O'Keefe]

Are you referring to the faux-leather carrying sleeve?  If so, I'd be up for a 
trade, since my "daily driver" is a 102, but my only intact sleeve is for a 100 
and it swims around loose in the thing.  I'll reach out off-list.

I'm a little surprised a 100 can even fit in the smaller one!

> On Jun 3, 2023, at 5:08 PM, Charlie Hoey  wrote:
> 
> 
> I picked up an M100 in a 102 bag at a flea a while back, and was wondering if 
> anybody had a 100 bag they would like to trade for a 102 bag? Not perfect but 
> not rips. 
> 
> Forgive me if there's a big value difference here I'm not aware of, figured 
> someone might be in the same boat. 
> 
> -C

Re: [M100] Variable Concordance - MTVarConcor

[Joshua O'Keefe]

> On May 1, 2023, at 5:03 PM, Mike Stein  wrote:
> 
> It worked fine on the test program; FYI, attached is the program it died on.
> 
I was able to reproduce the crash and ran it through gdb.

The last line of your "Eliza.bas" file seems to make line 100 of the code very 
unhappy.
It seems to be an 0x1a character and then a bunch of question marks.

If you delete that line of the input file, the program is parsed successfully.

Re: [M100] Variable Concordance - MTVarConcor

[Joshua O'Keefe]

> On May 1, 2023, at 3:58 PM, lloydel...@comcast.net wrote:
> Not using the output file is odd.   

I'm delighted to report that this turned out to be an operator error rather 
than a program error.

Re: [M100] Variable Concordance - MTVarConcor

[Joshua O'Keefe]

Hi Lloyd,

I'm happy to report your code compiled without error on a modern Linux system, 
although I did run into some very minor non-breaking bugs in operation.  
Currently it ignores the "output file" and emits the tokenization to stdout.  
After that, it produces output that matches your test output perfectly.

Thanks for providing source that made it so easy to run.  This can be very 
useful for program analysis.

Re: [M100] PC-8201A UsersGuide - page broken/unreadbale

[Joshua O'Keefe]

On Apr 22, 2023, at 11:56 AM, M100 Librarian  wrote:I believe I made a good scan of this manual. Here is the linkSince that link is login-only, and I have a throwaway account on that service, I have mirrored the document on my public S3 bucket and on the Internet Archive for those who don't have or want an account on the site:http://public.nachomountain.com/files/m100/8201A-users-guide.pdfNEC PC-8201A Users Guide : Free Download, Borrow, and Streaming : Internet Archivearchive.org

Re: [M100] Original ROM source

[Rev. Joshua O'Keefe]

On Tue, Mar 28, 2023 at 08:03:37AM -0400, Louis Ciotti wrote:
> Hi all,
> 
> Getting back into Retro Computing and out of curiosity is the source for the 
> original 100/102 ROMs available?

While there is not original OEM source, several folks have done
annotated disassemby:

https://github.com/eriktier/RomT102Disassembly

https://github.com/z88dk/techdocs/tree/master/targets/m100

And of course, Ken's original groundbreaking work:
http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/M100%20ROM%20Disassembly

Along with Steve's helpful copy of the guide to the ROM routines, from
TRS-80 Microcomputer News, Nov 1983:
http://www.club100.org/memfiles/index.php?=0==Steve%20Adolph/M100%20Rom%20Routines%20summary

There are commented disassemblies in the M100SIG archive, as well,
although partial:
https://github.com/LivingM100SIG/Living_M100SIG/tree/main/M100SIG/Lib-08-TECH-PROGRAMMING


I hope this helps your rekindled enjoyment!

Re: [M100] - Backpack

[Joshua O'Keefe]

> On Mar 2, 2023, at 3:45 PM, John R. Hogerhuis  wrote:
> The dinner bell interrupts you.

Is there a vector I can hook a routine to?  I have a ton of code I'd love to 
run at interrupt if it won't disrupt the dinner timing itself.

Re: [M100] - Text Sweet 2.3 Release

[Joshua O'Keefe]

> On Feb 28, 2023, at 11:21 AM, B 9  wrote:

> Last year I wrote a tokenizer in C. ¹ [well, lexx]
> https://github.com/hackerb9/tokenize
> 

Thank you for reminding me of this!  I was trying to remember it and it was the 
lexx I wanted!

[M100] dlplus naming

[Joshua O'Keefe]

> On Feb 24, 2023, at 7:55 AM, Brian K. White  wrote:
> dl2 makes the most sense if I didn't care about the "dl" part. It says what 
> it is and what to expect correctly and succinctly.

You are not obligated to take end user expectation into the equation here, 
however the end user is mostly just doing the same thing they've done with 
dlplus all along: grab some source, make it, run more or less the same command.

Many cool new features have accreted, adding some new options although some are 
transparent goodness.  Bootstrap capabilities have blossomed.  The end user 
experience, though, is pretty dlplus-(plus plus et al)-ish and it's not totally 
unreasonable to consider that in fork naming.

Do as you like, of course, the project is a boon to the community no matter the 
name!

Re: [M100] Radio Shack trs80 Model 200 for sale

[Joshua O'Keefe]

> On Feb 24, 2023, at 5:57 AM, Randall Kindig  wrote:
> 
> I didn’t get a response either.

After this thread revived (thanks b 9!) I received an off-list reply that it 
had been sold.  Nice to hear it didn't wind up making that dump run after all.

Re: [M100] Radio Shack trs80 Model 200 for sale

[Joshua O'Keefe]

Alas, no response.  I assume the poor thing went into the trash.On Feb 23, 2023, at 11:44 PM, B 9  wrote:Did Kevin ever respond to your offer? —b9On Sun, Feb 19, 2023 at 10:45 AM Joshua O'Keefe <maj...@nachomountain.com> wrote:Hello Kevin.Would you accept €150 for packing and shipping of the computer to the USA?

Re: [M100] M100 "VT52" terminal emulator for PC

[Joshua O'Keefe]

> On Feb 20, 2023, at 5:45 AM, Stephen Adolph  wrote:
> 
> After quite a bit of searching I finally found what I was looking for.
> It is a VT52 terminal emulator written in C#, and compilable in Visual 
> Studio.  I've been able to install the tools and been able to compile it.

Steve, this is exciting!  For values of "exciting" that perhaps only certain of 
us are capable of truly appreciating.

Bringing a full-blown modern-ish desktop computer into the display end of 
things really opens up the options a lot.

Did you evaluate something like qodem [1] in the process, taking that 
old-school DOS-like approach?  I'm curious if you poked through or evaluated 
text mode / curses type stuff or kept your searching mainly to the cool 
graphical CRT emulations a la cool-retro-term [2].  I could see getting a 
pretty gorgeous CRT-like DVI experience from that if the VT52 works.

[1] qodem has a site at https://qodem.sourceforge.net/ that really shows off 
that nice DOS era terminal emulator feeling, and it claims specifically VT52 
support separate from the VT100/102 emulation.

[2] cool-retro-term at https://github.com/Swordfish90/cool-retro-term is so 
much fun to play with because of the CRT emulation and font stuff but I haven't 
poked at the VT52 end of things.  

Re: [M100] Radio Shack trs80 Model 200 for sale

[Joshua O'Keefe]

> On Feb 18, 2023, at 12:11 AM, Kevin Lee  wrote:
> 
> Offers welcome.  Or it heads for the trash. 
> 
> T200 with multi plan option rom and instructions. 
> Including protective briefcase.   
> 
> Shipping from Central Europe.  

Hello Kevin.
Would you accept €150 for packing and shipping of the computer to the USA?

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[Joshua O'Keefe]

> On Feb 19, 2023, at 6:58 AM, B 9  wrote:
> 
> TextSweeper could benefit from more rows, which ROM-View 80 doesn't do. Does 
> anyone know if there is a ROM to do that?

Ultrascreen100 can do this.  I found my copy in Gary Weber's member upload 
area.  At 10 lines the font is not beautiful for text, but for a game or a 
program without close reading on the part of the user it might work out pretty 
nicely.

Re: [M100] One Tiny Battery Pack (Cryptronics, RAM+ expansion)

[Joshua O'Keefe]

> On Feb 17, 2023, at 9:49 PM, Brian K. White  wrote:
> I can't find a copy of tsload on-line anywhere unfortunately.


I ran into this same rarity problem and Kurt came to my rescue.  Because it was 
such a pain to lay my hands on I stuck it in my S3 bucket: 
http://public.nachomountain.com/files/m100/

As far as I'm concerned, please do feel free to fold it into the far less 
obscure dlplus as a bootstrappable binary blob, et al.

Re: [M100] CloudT fix for touchscreens

[Joshua O'Keefe]

> On Jan 16, 2023, at 7:32 PM, John R. Hogerhuis  wrote:
> 
> Might work on iOS too, haven't tried it.

Worked for me on iOS with touch, a touchpad, and the OEM's stylus -- all of 
which are semi-distinct pointing methods as far as the platform is concerned.  
I didn't get a chance to haul out a mouse, it's buried under a pile of travel 
stuff at the moment, but I can't see any reason it wouldn't work.

Re: [M100] TS-DOS Option ROM

[Joshua O'Keefe]

> On Dec 21, 2022, at 4:48 PM, Jerry Davis  wrote:
> So here's my vouchery: [ followed by details ]

I would like to confirm having done business with Jeff, Gregory, and Stephen, 
in addition to Peter and other individuals on this list.  In every instance the 
outcome has been positive, reliable, and in no way concerning from outset to 
outcome.  This is not to mention the many other similar interactions I've had 
with folks around other communities for other systems.

While I certainly appreciate the convenience of being able to work with an 
automated storefront -- Jeff and Gregory offer these as options and it's made 
life easy for me in the past -- it's certainly not the only way or even my 
preferred way to do things every time.  This is particularly true when dealing 
with bespoke hardware I'm unfamiliar with.

The list is full of attestations to the usefulness of the REX series of 
hardware gadgets and Stephen's support of them.  I'll gladly add my voice to 
that: my REX was a joy to acquire and is a joy to use.

Re: [M100] Generating and detecting other tones via the cassette port

[Joshua O'Keefe]

> On Nov 22, 2022, at 11:49 AM, Douglas Quagliana  wrote:
> 
> Has anyone experimented with generating and detecting tones on the cassette 
> port other than the standard cassette mark and space frequencies?  

Douglas,

While this isn't a direct answer to your question, for which I apologize, it 
may be a useful lead to mention that the original heritage TRS-80 Models I / 
III used the cassette port as audio outputs for music and in some cases speech. 
 I believe the circuit and method of operation was similar -- your approach 
seems reasonable.

Re: [M100] Bitchin' 100 on Bing

[Joshua O'Keefe]

> On Nov 13, 2022, at 6:07 AM, bir...@soigeneris.com wrote:
> 
> Looks like something in the specifier is broken, a more generic set of terms 
> works fine. 

Hi Jeff,

You may notice that the screenshot of results you found include many results 
that include the text "bitchin100", none of which are hosted at bitchin100.  As 
data, it does not appear to be prevented from being shown.  Only when a result 
has metadata showing origin of a document at bitchin100 does it appear to be 
"removed" from results shown to users.

This is consistent with the behavior described by the blog entry linked earlier 
in the thread.  Bing simply loses entire sites out of the index, for no 
discernible reason, entirely orthogonal to the content or behavior of the site, 
the site's users, or the intent of the person searching for it, and Bing's 
operators do not know or understand why nor even appear to have awareness that 
it is an ongoing problem.

When using Bing as an end user, or using products that incorporate Bing 
indexing upstream, be aware that search results can be incomplete.  The tool 
has its purpose and place, it's just buggy and not really production-ready yet.

Re: [M100] Club100 Personal Library

[Joshua O'Keefe]

> On Nov 12, 2022, at 6:07 AM, Jason White  wrote:
> I would like to create a library there and upload some of my programs that 
> don't seem to be anywhere.

Hi, Jason.

I don't have any control over Club100 whatsoever, but I would gladly publicly 
mirror any M100 related files you (or anyone else) would like to share.  Please 
feel free to reach out off-list.

Re: [M100] Notoriously S.L.O.W BASIC posted - help speeding it up appreciated

[Joshua O'Keefe]

> Cover will be a picture of me with lockdown beard and a Model 100 strapped on 
> the back of my 286cc motorcycle. Where is he going? Nowhere exceedingly fast

I'll admit my primary interest in this notional book -- a high interest, I 
should add -- is in its content, the bike and beard will certainly add to buyer 
satisfaction in my case.

Somewhat more seriously, this is something I do care deeply about at a larger 
level.  There's knowledge and systems understanding, some only recently 
uncovered, at risk of disappearing into time unless we leave some marks on the 
cave walls, and I encourage you and anyone else with a story to share, a design 
insight to show off, or the benefit of experience, to consider publication.  
More than a few such folks are gathered here.

Re: [M100] Notoriously S.L.O.W BASIC posted - help speeding it up appreciated

[Joshua O'Keefe]

> On Oct 31, 2022, at 1:31 PM, John R. Hogerhuis  wrote:
> The other way to do that is filesystems and backup agents that give you a 
> time machine feature.

My TPDD emulator of choice is pointed at a corner of my home directory.  My 
home directory is in a ZFS dataset.  The ZFS dataset is snapshot every 15 
minutes, rolled up into a week's worth of dailies, three month's worth of 
weeklies, a year's worth of monthlies, and a few year's worth of yearlies.

I have a habit of trying to keep DOS-ON when I can so most on-device BASIC dev 
can be sent off-device with an occasional SAVE"0:THING if I happen to be at my 
desk.

The notion of hooking SAVE to commits, though, is pretty attractive!  The 
granularity would be nice.

Re: [M100] Notoriously S.L.O.W BASIC posted - help speeding it up appreciated

[Joshua O'Keefe]

> On Oct 27, 2022, at 8:39 PM, B 9  wrote:
> 200 REM Print 2 hexits

In all my years, this is the first time I have seen the term "hexit."  From the 
code it's apparently another way of describing a hex representation of a 
nibble!  Quite a good couple of days for learning from the list, that's for 
sure.  Thanks.

Re: [M100] Notoriously S.L.O.W BASIC posted - help speeding it up appreciated

[Joshua O'Keefe]

> On Oct 26, 2022, at 12:27 PM, John R. Hogerhuis  wrote:
> 
> 110 PRINT@B,MID$(H$,A/16+1,1);MID$(H$,AMOD16+1,1);" ";

John, I just want to compliment you on an elegant idiom here.

Re: [M100] machine language monitor

[Joshua O'Keefe]

> On Oct 24, 2022, at 6:46 PM, runrin  wrote:
> 
> hi all!
> 
> i was wondering if anyone had recommendations for a machine language
> monitor similar to supermon on commodore 64.

The DBG facility in the ROM2/Cleuseau option ROM is a lot like a traditional ML 
monitor.  I haven't played with it much, but the ROM image is up on club100 and 
it works great in a REX.

Re: [M100] zbug on archive.org

[Joshua O'Keefe]

> On Oct 22, 2022, at 1:27 PM, runrin  wrote:
> 
> i was wondering if it would be okay with joshua if i (or someone else) 
> uploaded the zbug manual and binary to archive.org so it is easier for others 
> to find. because it's known as zbug to many people, that doesn't make it easy 
> to track it down with only the original title.

I certainly have no objections.  Please do archive it!

Re: [M100] Keep getting DS ERROR when loading via serial.

[Joshua O'Keefe]

> On Oct 21, 2022, at 10:32 PM, r Gi  wrote:
> 
> I am repeatedly getting a DS ERROR most of the time when I try to load a 
> program. It happens a short time after starting the upload. Any help would be 
> appreciated

Nearly all of the DS ERRORs I have received while reading BASIC programs over 
serial have been victims of formatting errors.  There are many on the internet, 
particularly in the CompuServ archive, that have been line wrapped.  I've run 
into this with programs OCRed from books as well.

Just as if you were typing the program, hitting Enter too early and then 
continuing to type would execute a direct statement.  Doing so is not allowed 
while you're LOADing.  That's what happened to me while loading these various 
files.

Fixing the line wrapping solves the issue.

Re: [M100] Planning out some weekend projects.

[Joshua O'Keefe]

> On Oct 19, 2022, at 3:33 PM, Peter Noeth  wrote:
> " Assembler/Debugger" part number 26-3823. I have been looking for this 
> software package for a number of years myself, just to make my collection 
> complete.  

Hi Peter,

If you're just hoping to use the software I have the Tandy editor/assembler 
debugger in my bucket[1], along with the manual.  I believe it has been labeled 
variously "ZBG" or "EDTASM" (as other Tandy assemblers) as well.  The 
underlying assembler and debugger are the Microsoft package, I believe.

Another member found it on the Internet Archive mirror of the defunct xibalba 
site.

If you're hoping for a physical item, I've never seen one.

[1]. http://public.nachomountain.com/files/m100/

Re: [M100] Serial on M100

[Joshua O'Keefe]

For chucking text files back and forth I have had relatively OK luck just 
"cat"ing a file to or from the serial port, with the caveat that XON/XOFF flow 
control and a low baud rate make it more reliable.

This works relatively well for logging in to a getty, too.  I haven't spent 
enough time poking around launchd to tell you how to fire up a getty on Darwin 
but it ought to be possible without too much hassle and you could always just 
run one by hand for testing it out.  There's a great terminfo file out there 
that pretty much Just Works; I think it was b 9's efforts to get it into such 
nice shape.

Because of the variable processing speed of the BASIC interpreter, just 
blasting away at the serial port with cat rarely works great when I try to do 
it to LOAD untokenized BASIC.  My best results by far have been with using 
dlplus bootstrapper mode.

It's been decades since I used minicom but I think it does offer the ability to 
enable software flow control if you don't want to wade into the intricacies of 
stty.

Re: [M100] Modems and the modern world

[Joshua O'Keefe]

> On Oct 7, 2022, at 7:41 AM, Will Senn  wrote:
> I unpacked the .deb file and after a bit of sorting out dependencies, got it 
> running on my mac:

For future reference, I keep a tarball of this (plus a distribution with bit of 
stuff to build a Docker image) in my bucket[1].  It's a touch easier to install 
for folks who don't use Debian-based packaging.

> Cool - kinda like a python dlplus... Is this the same mcomm you're referring 
> to? 

Python mComm is a fairly recent innovation.  I think many folks who use mComm 
are referring to the Android or Windows software of the same name.  I don't 
have Android or Windows so I can't speak to the feature set of those particular 
implementations but as far as I'm aware Python mComm doesn't have modem 
emulation.  A cursory examination of the code doesn't show anything that looks 
like it.

One of mComm's differentiating features is special support for the Sardine[2] 
dictionary image. I don't believe other TPDD emulators have Sardine disk image 
support.

> Is there a man page somewhere?

If there is, I haven't found it.

[1.] http://public.nachomountain.com/files/m100/

[2.] The spell checking software available as a stand alone option ROM or in 
Ultimate Rom II.  It does raw sector access of a specially-formatted TPDD disk 
containing the dictionary.

Re: [M100] Modems and the modern world

[Joshua O'Keefe]

> On Oct 6, 2022, at 4:55 PM, Will Senn  wrote:
> 
> Awesome. Now, all I gotta do is figure out how to telnet from my m100...

I won't spoil too much for your journey of discovery, but let's just say I 
really like my WiModem 232.

Re: [M100] When 10 GOTO 10 doesn't go to 10

[Joshua O'Keefe]

>> All: Does anyone have a Tandy 102 who's willing to try GOTO10.BA?
> 
> My 102 full of precious data is downstairs.  I will go abuse it.

Trip report:
After some fussing around with my Samba server because apparently an iOS update 
made it impossible to write files over SMB again, I just extracted the mime 
attachment out of the email on disk, stuck it in the designated TPDD directory 
in my $HOME, and brought it over with TS-DOS on REX.  LaddieAlpha [1] was the 
TPDD client, which I believe does some basic sanity checking on .BA.

Results:
Program LOADs from RAM filesystem into BASIC as expected.
Program LISTs in the manner that appears to be intended, if my eyeballing the 
tokenized file in vim reads right.
Program RUNs in the manner that appears to be intended, or at least congruent 
with the running commentary it provides.
Program BREAKs as expected with S-Break
A cursory inspection shows no obvious ill effects

Platform description:
T102, USA, Aug 1987 dated
32K RAM, heavily occupied by real data
REX Classic 4.9 6(1)
TS-DOS 4.10 /KM in REX option rom space
LaddieAlpha 05/05/2019 10:09:54 File Version : 2.1.0.0 on whatever version of 
Mono is in the default Docker mono image

Re: [M100] When 10 GOTO 10 doesn't go to 10

[Joshua O'Keefe]

> On Oct 6, 2022, at 4:00 PM, B 9  wrote:
> 
> All: Does anyone have a Tandy 102 who's willing to try GOTO10.BA?

My 102 full of precious data is downstairs.  I will go abuse it.

Re: [M100] is the m100 a trs-80? In walks like a, not is categorized as a

[Joshua O'Keefe]

> On Oct 6, 2022, at 9:47 AM, Mike Stein  wrote:
> 
> It's quite different from systems like Commodore etc. where BASIC does indeed 
> supply the main interface and control.

Hah, I was just about to comment on some of the Commodore operating 
environments by way of comparison!

The T offers an equivalent of a CP/M BIOS or Commodore KERNAL in the ROM.  It 
offers a command interpreter suitable for file operations and program 
launching, much like CP/M's command shell, though far more programmable in many 
ways; it also includes a great menu driven launcher and file browser.  The most 
popular of the Commodore environments -- that of the C64 -- had quite a bit 
less capability in terms of file management without significant extension 
although several earlier and later Commodore ROMs included such capabilities.

To top it off, much like CP/M and other things that meet the traditional 
definition of an operating system, several good utilities are included with the 
T's operating environment, like TEXT, TELCOM, and the mini-databases.

I won't define it for others but such a package meets my own definition of an 
operating system better than some of the other operating systems I've used.

Re: [M100] is the m100 a trs-80? In walks like a, not is categorized as a

[Joshua O'Keefe]

> On Oct 6, 2022, at 9:04 AM, Brian White  wrote:
> 
> I think I've seen BASIC 80 before but couldn't say where so it might be 
> imagination. 

BASIC-80 is, as best as I'm aware, the product name of the various Microsoft 
BASIC implementations for 8080 and Z80.  It's documented with that name in this 
manual which also refers to BASIC-86 which might be presumed to refer to the 
8086 implementation:

https://ia800708.us.archive.org/8/items/BASIC-80_MBASIC_Reference_Manual/BASIC-80_MBASIC_Reference_Manual_text.pdf

As such, I think it would be reasonable to call the BASIC interpreter itself on 
the T "BASIC-80", although the OS is obviously more than just the included 
BASIC.

Re: [M100] Programs from books and magazines without typing

[Joshua O'Keefe]

> On Oct 1, 2022, at 1:51 PM, Wayne Lorentz  wrote:
> 
> Some of you will be adept enough to be able to use OCR software to convert 
> the pages of the books into text that you can then send to your M100.

With the last couple of type-ins I've done, I just took archive.org's existing 
OCR (plain text is one of the download formats of many books) and cleaned it up 
a little in a text editor.  Two seconds in unix2dos and it's ready for loading.

For those with access to Acrobat, it does a perfectly good OCR -- somewhat 
better than Internet Archive's.  There are also plenty of decent open source 
OCR options already in most distributions of most operating systems, as well as 
in Homebrew.

All the same, I've been happy just using Internet Archive's so-so-at-best OCR 
as a starting point.

Re: [M100] the battery backup

[Joshua O'Keefe]

> On Oct 1, 2022, at 10:20 AM, Will Senn  wrote:
> 
>  Given that my new m100 is 39 years old, should I expect that parts need 
> replacing inside?

The generally accepted wisdom seems to be that when doing intake of a "new" 100 
to replace the NiCd and all capacitors ASAP.  They risks to the life of the 
machine.  A 102 may not need capacitors replaced quite so urgently, but that 
NiCd still has gotta go pronto.

Re: [M100] is the m100 a trs-80? In walks like a, not is categorized as a

[Joshua O'Keefe]

> On Sep 29, 2022, at 8:05 AM, Chris Trainor  wrote:
> 
> But still mostly a brand… the basis for the 80 was the Z80

This is how I understand it from reading "Priming the Pump: How TRS-80 
Enthusiasts Helped Spark the PC Revolution" a while back.  The "80" reflected 
the processor in the branding but shorty thereafter the reference to the coming 
decade made "TRS-80" an appealing brand to unify the entire computing product 
line under.  To my memory quite a few brands of products and media used the 
number 80 as a kind of allusion to modernity and the future.

Under the TRS-80 branding, lots of computers were offered, few of which were 
compatible or partially compatible with the original Model I/III.

The Pocket Computer was a rebadged Sharp PC-1121 and the Pocket Computer II was 
a PC-1500.  The PC-3 dropped the TRS-80 name for Tandy mid-way through its 
lifecycle and subsequent Pocket Computers -- based on Casio calculators -- were 
Tandy branded.

The TRS-80 MC-10 was quite similar to a Color Computer superficially but 
incompatible with it.  

The Model II, released shortly after the Model I bore a bit of similarity to it 
yet had no compatibility whatsoever and even used a completely different disk 
size and format.  It spawned a series of other TRS-80s (the 12/16/16B and 
eventually the Tandy 6000) that had some limited degree of compatibility among 
themselves while being architecturally independent of the I/III/4 series that 
dominated sales during the era.

The TRS-80 Color Computer was completely unlike the computers that inaugurated 
the TRS-80 badging although they found a popularity of their own.  The CoCo 2 
and 3 were offered only under a "Tandy" name as far as I know.

Then, of course, you have the TRS-80 Model 100 and Tandy 200 computers.  The 
Model 100 is almost entirely a rebadge of the Kyocera Kyotronic 85.  The 200, 
never sold under the "TRS-80" banner, is incompatible.  The Tandy 102 is a 
cost-reduced version of the 100 taking advantage of surface mount technologies 
which reduced the weight of the computer; a handful of other changes were made 
to the system.

Long story short:  "TRS-80" started as a name for the first pre-assembled 
microcomputer for retail, became a trademark banner under which Tandy/RS 
designed or rebadged more computers, and eventually went away when it became 
less descriptive and the trademark itself lost its cachet.

Importantly, it doesn't describe anything technical about a computer.

Re: [M100] assembly language first steps

[Joshua O'Keefe]

> On Sep 26, 2022, at 5:13 PM, Will Senn  wrote:
> I believe there is a basic assembler program in the wild and I've read about 
> Custom Software's assembler, are either or both available online?

Take this with a little bit of salt since I haven't actually used it but it 
might not be totally out of place to familiarize yourself with Radio Shack's 
EDTASM/ZBUG (26-3823) depending on if you want a self-hosted solution or not.  
It's a Tandy-licensed version of Microsoft's assembler/debugger package.

It's sitting on my bucket which I mentioned in this thread:
http://lists.bitchin100.com/private.cgi/m100-bitchin100.com/2021-March/053381.html

in this message:
http://lists.bitchin100.com/private.cgi/m100-bitchin100.com/2021-March/053384.html

Re: [M100] transferring files both directions

[Joshua O'Keefe]

> On Sep 26, 2022, at 5:24 PM, Will Senn  wrote:
> find the DB-25, null-modem adapter, and DB-9 to USB adapter

That is essentially what I use (although I picked a 9-pin<>USB adapter that was 
pre-wired null since I have no use cases for a non-nulled connection).

USB gadget: https://smile.amazon.com/dp/B008634VJY/
25/9: https://smile.amazon.com/dp/B87RYP/
Coupling: https://smile.amazon.com/dp/B00066HP5G/

This setup has worked flawlessly for talking to every serial device I've tried 
to talk to in the last several years.

For most ASCII file transfers I've had decent luck just catting the file to or 
from /dev/ttyUSB0 without an intervening serial terminal emulator, although I 
have to rummage around in some very old memory to remember how I want to stty 
it.

Note, I'm not sure what Darwin names serial devices as I haven't tried this on 
Darwin in years.  Your character device name may differ.

Re: [M100] Questions about tokenizing BASIC in UNIX

[Joshua O'Keefe]

> On Sep 25, 2022, at 8:59 PM, Daryl Tester 
>  wrote:
> 
> I've got a todo item to see how
> to enable the dev_dbg() messages

I looked, hoping to spare you from rebooting with debug enabled the old 
fashioned way.

If the kernel has DYNAMIC_DEBUG=y [1] then:
https://stackoverflow.com/a/63682160

TL;DR: mount debugfs if not mounted, tell 
/sys/kernel/debug/dynamic_debug/control the kernel file you want output from, 
look in kern.log

Just tested the debug control procedure against ftdi_sio.c and it worked fine 
to produce some output.  Unfortunately said serial chip is downstairs and I'm 
stuck upstairs for several more hours so it's a bit inconvenient to 
reinitialize the chip from here to watch it come up.

DYNAMIC_DEBUG is pretty neat!  It didn't exist last time I touched driver code.

[1] https://www.kernel.org/doc/html/v4.11/admin-guide/dynamic-debug-howto.html

Re: [M100] what's the Right Way to code and assemble on model-t hardware

[Joshua O'Keefe]

> On Sep 8, 2022, at 9:10 AM, MikeS  wrote:
> 
> What and where is BYTEIT?

I hadn't heard of this, either, but a quick Google turned it up on the club100 
programming library.

The club100 programming library is at:
http://www.club100.org/library/libprg.html

It lists BYTEIT as "A really good 80C85 assembler"

Re: [M100] M100 Linux keyboard via inputattach?

[Joshua O'Keefe]

> On Sep 8, 2022, at 9:09 AM, MikeS  wrote:
> Where can I find a good termcaps file?

I don't have a file in termcap format but the terminfo I use is in my bucket.  
It's by far the most comprehensive of those I've come across:

http://public.nachomountain.com/files/m100/

Re: [M100] Writing binary files from BASIC

[Joshua O'Keefe]

> On Aug 18, 2022, at 11:12 AM, Joshua O'Keefe  wrote:
> conjecture, but aren't ^@, ^H, and ^Z control characters that affect console 
> output 

Apologies for replying to myself; I realize on reflection CHR$(127) is ^? (DEL) 
rather than ^H (BS) isn't it?

Re: [M100] Writing binary files from BASIC

[Joshua O'Keefe]

> On Aug 18, 2022, at 10:17 AM, B 9  wrote:
> And you cannot use the 3 Control Characters, NULL (0), Control-Z (26) and 
> Back Space (127).
> 
> While it doesn't explain everything, like what special meaning CHR$(127) has 
> in a DO file,

I'm away from both my systems and documentation, so this is nothing more than 
conjecture, but aren't ^@, ^H, and ^Z control characters that affect console 
output behavior when sent?  Perhaps exceptions are carved out because of their 
relationship to the console output stream.

Re: [M100] REX# and Option ROMs: Qs from a noob

[Joshua O'Keefe]

> On Jul 6, 2022, at 5:53 AM, Charles Hudson  wrote:
> I found the OR files at http://www.club100.org/library/librom.html and 
> inspected a few.  Immediately I was out of my depth, so pardon me for 
> inquiring:

Hi Charles,

I'd suggest you might want to start with the binary files at 
http://bitchin100.com/wiki/index.php?title=REXsharp#Option_ROM_Images_for_Download
 as that's a pretty comprehensive slice of the ROMs out there which work with 
the device.  Conveniently, they are already converted from HEX format into the 
BY format used by the REXMGR.

Re: [M100] Bump

[Joshua O'Keefe]

> On Jun 14, 2022, at 12:28 PM, John R. Hogerhuis  wrote:
> Hope everyone is enjoying their summer :-) 

It's been a mixed bag for me so far but I've managed some victories on the 
retrocomputing front.  On a long stay away from home I managed to score a fully 
operational (but not recapped / re-batteried) Mac 512Ke for about a quarter of 
the going price.  I also scored a PowerBook Duo 280c with damn near every 
accessory ever made and an extremely hard to find memory upgrade.  It ought to 
be here next week.

My REXCPM arrived a while back but the M100 I planned to put it into suffered 
something unexpected when I diked out the battery: it paints the menu and clock 
and then hangs.  It didn't do that before my hackneyed surgery so I assume I 
did some damage.  Or does the 100 not operate properly with 0V across the 
internal battery?  If that's not it I might need to poll the list for someone 
taking repair work.

I could put the REXCPM into my 102 but I actually use the 102 pretty regularly 
for actual tasks and am loathe to disturb it from its ideal state.

Other projects still pending: my MRC C64-clone ITX case arrived, awaiting a 
build of indeterminate nature.  The PowerBook G4 1.67 needs attention, too.  At 
last check, rummaging around the internals to upgrade it caused the nearly 
irreplaceable ribbon from the upper case to become unreliable and it's gone 
through two different front loading optical drives already.  I'd hoped to turn 
that into a MorphOS machine.

Lots of toys.  Very little free time.

Re: [M100] is the list actually working?

[Joshua O'Keefe]

> On May 3, 2022, at 10:02 AM, John R. Hogerhuis  wrote:
> You say "messages will look a little different from these users." 
> Can you talk more about that? Are you talking about mail service software or 
> people reading the list?

End users (us!) will see messages from the list with a From: that says 
something along the lines of "From: John R. Hogerhuis via m100 
" which will show to the end user (depending on their MUA 
/ mail reader software) as "From: John R. Hogerhuis via m100" potentially with 
or without the  bit.  Many modern clients (iOS Mail, Outlook, many of 
the webmail clients I've seen) will show just the front bit and require a click 
to reveal the second bit, which will no longer be the submitter's email address.

This will work for the majority use case: mail traffic will show up in 
subscriber's inboxes, the submitter's name will be visible (if slightly 
different), and hitting the Reply button will send a reply to the list.  The 
submitter's email address will not (as far I can tell from the docs) be 
visible, making it just a little more friction to take a discussion off-list 
since you can't copy the email address off as easily.

Happy to continue the discussion or implementation details off-list.  I'm sure 
most of us don't need to read more of my strong opinions on running mail 
infrastructure.

Re: [M100] is the list actually working?

[Joshua O'Keefe]

> On May 3, 2022, at 9:30 AM, John R. Hogerhuis  wrote:
> If anyone has a suggestion that I can try in Mailman I'll try it.

Hi John,

In my own opinion the safest thing to do is to sigh and implement one of 
mailman's two header munging policies:

Option A is:
set dmarc_mitigate_action to munge_from
set (if not already enabled, it appears to be) reply_goes_to_list
net result: mailman will look up the submitter's DMARC record, and if 
policy=quarantine or policy=reject is set, munge the header; messages will look 
a little different if submitted by one of those users.

Option B is:
set dmarc_mitigate_action to munge_from
set dmarc_mitigate_unconditionally
set reply_goes_to_list
net result: mailman will always munge From: regardless of the submitter's ESP 
policy; messages will look a little different.

Option C -- leaving well enough alone -- should be on the table as well, for a 
variety of reasons.

Note also that I haven't run a mailman of my own for over a decade, well before 
the publication of RFC7489.  The suggested configurations are based on doc 
reading and applying the lessons of running (non-mailman) mail systems at work 
that deliver a million messages a day.

Re: [M100] is the list actually working?

[Joshua O'Keefe]

> On May 3, 2022, at 8:20 AM, Cedric Amand  wrote:
> 
> By implementing DMARC records, you know who's trying to send mail "on your 
> behalf" and I noticed that in the DMARC reports, this mailing list's server 
> was one of them.

This is true for users who control their domain and can manage mail flow as a 
result of reports .  The vast majority of users do not: they use large public 
services that are highly incentivized to use DMARC records with adkim=s and 
asps=s, breaking customary email use cases and offering end users no choice in 
the matter of the policy selected by their ESP.

This is orthogonal to SPF failure: any non-broken implementation of SPF uses 
the envelope From, which would not interfere with mailing list deliverability.  
A message may pass SPF & DKIM, only to be rejected by DMARC because DMARC pins 
its mechanism (called "alignment" in the RFC) to the header From: 

Long story short is that the world has largely adopted strict DKIM alignment 
policies, for good or ill and as a result anyone who sends messages on behalf 
of end users has to munge the From: header or face deliverability problems and 
sender reputation degradation.

Re: [M100] is the list actually working?

[Joshua O'Keefe]

> On May 3, 2022, at 7:09 AM, Cedric Amand  wrote:
> I did not investigate this much ; but I would look at the DMARC and « from » 
> problems 

DMARC is definitely one -- potentially the main -- issue here.  If someone with 
a strict DMARC record submits a message to the list for broadcast, many list 
recipients will quarantine or reject the message unless the From: header is 
munged.

Mailman has some potential mitigation strategies against this[1], none of which 
are great, but DMARC fundamentally broke the way email works by pinning its 
mechanism on the From: header.[2]

[1] 
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/docs/dmarc-mitigations.html

[2] RFC7489 §5 says, essentially: requiring trust in From: was the only way to 
make DMARC go.  It doesn't actually justify doing so beyond saying (in §6.7) 
acceptance is a local decision.  The RFC takes no responsibility for 
establishing a de facto status quo that is broken.

Re: [M100] is it just me , or..

[Joshua O'Keefe]

On Apr 26, 2022, at 7:50 AM, Chris Trainor  wrote:
> it's super important you flag it as not spam to train Google that it's not 
> junk.

My personal experience over the past 18 years of using Google mail systems is 
that it's completely untrainable and learns absolutely nothing from end user 
flagging.  Whatever signals it's mis-training on are massively outweighing end 
user input.

Re: [M100] is it just me , or..

[Joshua O'Keefe]

On Apr 26, 2022, at 4:39 AM, Stephen Adolph  wrote:
> Mail from the mailing list really seems to be out of sync these days.
> I'm seeing replies to emails that I have never seen the original post for.

This has been a sporadic issue for me that seems to be getting worse.  
Previously the missing messages were primarily from Yahoo addresses and getting 
incorrectly marked as spam for what appeared to be SPF reasons.  This is a 
Google header parsing/spam routing bug (even if you have rules to deliver these 
messages anyway!) and I still have to go retrieve those periodically although 
less often lately.

Currently some replies are being delivered hours or days before the originating 
message.  Sometimes the originating message is not delivered at all.  I'd have 
to see John's MTA logs to know why but as someone whose professional 
responsibilities include deliverability of messages with rewritten headers I've 
seen comparable problems when the receiving MTA is greylisting delivery 
attempts due to bad heuristics.

Both you and I are using Google mail infrastructure so that might be the 
commonality to start pointing fingers.

Re: [M100] Scripsit 100 (cat. 26-3830)

[Joshua O'Keefe]

> On Mar 8, 2022, at 10:07 AM, Joshua O'Keefe  wrote:
> Scripsit 100 (C. 26-3830)

Thanks to everyone who sent files and links.  I'm looking forward to playing 
around with it.  If I can get it up and running I'll see if I can't share a REX 
memory image of the installed system for the convenience of others.

[M100] Scripsit 100 (cat. 26-3830)

[Joshua O'Keefe]

Folks,

I have something of an affinity for poking around word processors and text 
formatters across many platforms, plus a fondness for the various forms that 
Scripsit came in over the years.  I've turned up occasional references[1] to 
Scripsit 100 (C. 26-3830) which was available on tape.  I have not, however, 
found either a capture of the tape or a transfer of the files on it.

Does anyone have the software?  If so, I assume that as is typical for M100 
word processors it relies heavily on TEXT for the heavy lifting and focuses on 
formatting and printing.

[1] http://www.trs-80.org/scripsit/  and
 
https://www.worthpoint.com/worthopedia/radio-shack-trs-80-model-100-scripsit-1947581092
 

Re: [M100] hardware scrolling patch

[Joshua O'Keefe]

> On Feb 23, 2022, at 7:17 AM, Stephen Adolph  wrote:
> I did a write up on the two patches that are needed.

Steve, I remember seeing you mention this a while back and I'm glad you were 
able to get back to it.  Your write-up was clear, informative and interesting.  
Thanks for sharing it.

I wonder why this controller feature was never exploited.  Was there perhaps a 
similar, earlier part lacking the feature that was swapped out late in the 
design cycle?  Simple time constraints like every engineer in history has 
faced?  I can imagine all kinds of scenarios and it's a shame we'll never know 
the real story of why the ROM is the way it is.

Re: [M100] Re-sending... Option ROM ID?

[Joshua O'Keefe]

> On Feb 9, 2022, at 10:57 PM, Carlos M. Nunez, M.D.  wrote:
> What does the Polar Engineering ROM do? I tried searching but can’t find 
> much.

It is a software development tool.  ROM2 in particular is a tool for assembly 
development.  I've only ever seen it combined with Cleuseau, which is a tool 
for BASIC development but this might be a stand-alone version.

Club100 has an addenda to the manual for it, though it seems the manual itself 
is not there.  I do have a copy somewhere, though.

> Also, how do I create a dump of the ROM that would be useable?

There are some BASIC utilities that can write out the ROM to a serial device.  
If I were taking a shot at dumping the ROM I would rummage up one of those 
utilities, hook up to my serial cable, then just capture the input from 
/dev/ttyUSB0 to a file using cat.  The hard part would be tracking down the 
existing utilities so I wouldn't have to look up ROM addresses and write a 
PEEK/PRINT# loop.

Re: [M100] Re-sending... Option ROM ID?

[Joshua O'Keefe]

On Feb 9, 2022, at 2:48 PM, Carlos M. Nunez, M.D.  wrote:
> Re-sending without the attached image. It was flagged as too big.
>> I don’t know if the email list supports attaching files, but does anyone 
>> recognize the attached Option ROM, pulled from a T11?
>> M100  ROM2
>> Copr   1985
>> v4.840219

Polar Engineering ROM2 perhaps?  The v4.8 versioning seems earlier than the 
identified one on the Club100 archive (annotated "v5.2/3.2" presumably for the 
ROM2 version and Cleusau version), but an unidentified one is also annotated 
with "(Developer)" and "v?"

As far as I'm aware the "Developer" version was a Club100 distribution with 
some feature changes but I do not know how it was marked.  That's before my 
time as a participant.

Re: [M100] Cassette relay 1 Model 100

[Joshua O'Keefe]

> On Feb 4, 2022, at 7:10 PM, Rob  wrote:
> I'm just playing around with the basic software. The question I have, is 
> there a peek and poke to turn on relay 1.

I've spent pretty much no time on cassette functions for personal reasons but 
as far as I'm aware the high level way to control the cassette motor is the 
BASIC command "MOTOR", which can be called as "MOTOR ON" or "MOTOR OFF".  It is 
documented on page 160 of the User's Guide.

You could also rummage around that fancy new disassembly of the ROM to find out 
what it's up to when it does that:

https://github.com/z88dk/techdocs/blob/master/targets/m100/m100.asm#L7563

Re: [M100] How to delete then re-install VirtualT 1.6

[Joshua O'Keefe]

> On Feb 4, 2022, at 10:37 AM, b...@pigford.org wrote:
> My laptop is not organized like you suggest.  I have tried to move folders to 
> make it look like your examples but I have not been successful. 

I'm not much of a Windows person these days but the location of AppData can be 
determined, if your system is configured in a highly unusual way:
   
https://www.freecodecamp.org/news/appdata-where-to-find-the-appdata-folder-in-windows-10/

If VirtualT's Windows version takes advantage of the AppData facility of the 
OS, you may find something there.

Re: [M100] test

[Joshua O'Keefe]

On Jan 29, 2022, at 1:29 PM, Peter Vollan  wrote:
> well, mComm has stopped working on me.
> Sorry but I don't see my posts, just your answers to them

Peter, it looks like your messages are getting through to the list just fine as 
they are being archived here:
  
http://lists.bitchin100.com/private.cgi/m100-bitchin100.com/2022-January/054880.html

I don't normally get my own messages back from the list, but if that's 
something might be able to change in your listserv settings.

Don't have any useful advice for mComm, as I've only played with the Python 
version a little and don't have any Android devices with which to use the other 
version.

Re: [M100] New (again) Model 100 owner

[Joshua O'Keefe]

On Jan 28, 2022, at 11:43 PM, Carlos M. Nunez, M.D.  wrote:
> 1. Are there any recommended sources for a null modem cable? I would prefer 
> the PC end to terminate in a USB plug, so I believe it will require a serial 
> to usb converter somewhere.

You may receive a torrent of responses, as for one reason or another this is an 
area where quite a few people hold very strong opinions.  Personally, I grabbed 
the first USB/serial null cable I could find that had an FTDI chip:

https://smile.amazon.com/gp/product/B008634VJY/

It's unfortunately 9-pin so I had to pick up a 9-to-25 to make use of it, and 
of course a gender adapter to use with the Tandy.

Since I'm pretty much forever going to only have DTE on the serial end of this 
cable, I went with something null wired.  I use it frequently with several 
different vintage systems on the other end -- in fact I originally bought this 
to bootstrap an Amiga -- and it works flawlessly.  I plug it in and it 
magically shows up as /dev/ttyUSB0 and I can do whatever I want with it.

> Also, any good online information and/or tutorials that walk through the null 
> modem cable file transfer stuff?


TPDD emulation is the main way by which folks get files in and out of the 
machine.  Personally, I just keep a TPDD emulator (LaddieAlpha, as it offers 
directory support) running in a Docker container and plug in whenever I need to 
get files in and out, but I have the advantage of having TS-DOS in ROM on the 
Tandy -- REX makes it possible!

Before I got set up with a REX, I bootstrapped TEENY.CO to the system using 
dlplus and fumbled my way around getting that working.  After finding TEENY 
kind of inconvenient, I bit the bullet and brought TS-DOS over to sit in RAM.  
It's a satisfactory solution but doesn't leave a ton of working room on the 
computer.

The easiest solution by far is a REX: plug in the board, go through the brief, 
documented steps to get the REX up, plug into your favorite TPDD emulator, fire 
up TS-DOS from the REX, and files come and go as you please.

I've got a Backpack I want to try for when I start traveling again, but while 
I'm mostly in the house I prefer to write directly to the ZFS pool over a 
serial cable.

As far as I've seen, nobody's written a step-by-step guide to getting up and 
running.  There are a lot of choices depending on what you're doing, where 
you're going, what hardware you have and plan to carry with you, and how 
Windows-y or Android-y a person you are.  The basics of how all this works are 
pretty straightforward once you get your head around the fundamentals but there 
are tool choices to make for which a one-size-fits-most guide appears somewhat 
hard to write beyond: "Get REX, set up TPDD emulation to your taste."

Re: [M100] Backpack drive?!?1

[Joshua O'Keefe]

On Jan 28, 2022, at 9:20 AM, ~Art  wrote:
> Are these still available?  Who would I contact?

Hi Art!  I got mine from:
  https://www.soigeneris.com/tandy-tpdd-2-backpack-drive

Looks like he still has a few on hand, too!

Re: [M100] ROM disassembly updatec

[Joshua O'Keefe]

On Jan 14, 2022, at 3:21 PM, Stefano Bodrato  
wrote:
> I'm proud to announce that I finished copying in the M100 and MSX  the 
> comments found in the sources of mbasic for cp/m .
> This makes most of the complex stuff more understandable, just have a look!
> Moreover the same source can produce M10, M100 or KC85 ROMs identical to the 
> original ones. 

Stefano, this is outstanding!  Thank you for sharing it.

[M100] M100 freezes at menu

[Joshua O'Keefe]

I somewhat recently acquired an M100 in fairly decent condition, but the 
battery had not yet been changed and it needed the space bar properly 
re-mounted.  It was in operable condition, booted, and worked.  I opened it up 
to fix up the keycap and quickly dike out the battery to buy myself time to 
come back to the machine later.

After cutting out (and not replacing) the battery, the machine starts, prints 
the menu, and then freezes.  In this state the clock is not advancing.  I've 
yet to do any troubleshooting whatsoever beyond this point as I needed to put 
the unit away for a while.  When I come back to it, what are some things I 
should look for?  Considering it worked before I opened it I'm assuming I 
damaged something in the battery region while making my cuts.  I don't know if 
there's a trace or component in that area that'd lead the machine to run 
exactly long enough to paint the menu and then halt.  

Does this sound like a machine state anyone's seen before?

Re: [M100] The Living M100SIG

[Joshua O'Keefe]

> On Dec 17, 2021, at 9:48 PM, Brian K. White  wrote:
> 
> I got tired of running into simple fixable things and other update 
> opportunities in the M100SIG, and having no good place to put them.
> 
> https://github.com/bkw777/Living_M100SIG

Brian, thank you for this.  I have cloned the repo into my personal archives 
for convenience as well as set up live pull-only mirroring to GitLab as I'm 
generally dubious of Microsoft's long term commitment to GitHub as a public 
resource.  The more entry points the better.  Said mirror is available at:

https://gitlab.com/majick/Living_M100SIG

Re: [M100] GoTek floppy and DVI unit?

[Joshua O'Keefe]

> On Dec 5, 2021, at 2:07 PM, Gregory McGill  wrote:
> Someone has,  its back in the scroll somewhere it works fine with ff

I remember seeing this go by, too.  Found it!  Jerry gave an excellent detailed 
write up:

> From: Jerry Davis 
> Date: May 24, 2021 at 9:32:32 AM PDT
> To: m...@bitchin100.com
> Subject: Re: [M100] DVI + Floppy Emulation
> Reply-To: m...@bitchin100.com
> 
> 
> Yes.  I attached one to my DVI a few weeks ago.
> 
> I purchased a Gotek SFR1M44-U100 from Amazon.  The Gotek is a 3.5" drive 
> format.  To mount the Gotek into the 5.25" drive bay that the DVI has I also 
> purchased the following:
> 
> (1) Startek 3.5" to 5.25" front bay adapter (Amazon)
> (1) Kentek 6" adapter from 4-Pin Male Molex 5.25" drive power connector to 
> 4-pin Female 3.5" drive power connector (Amazon)
> (1) 34-Pin Card Edge to IDC Connector Adapter - 5.25" to 3.5" Floppy Cable 
> (eBay)
> (1) Gigastone Z90 32GB USB 3.1 Flash Drive (Amazon)
> 
> The flash drive I purchased is very short.  I didn't want a USB drive 
> sticking way out from the front because it gets in the way.  32GB is massive 
> overkill in terms of space for disk images but that's what was available in a 
> small package for a good price.
> 
> I installed the latest version of "flashfloppy" by Keir Fraser (and many 
> other contributors) onto the Gotek using the instructions on the flashfloppy 
> Githib Wiki.  The Gotek I received had the Artery chip installed which 
> required a special build at first but I believe is now supported on the 
> newest builds.  I saw a note on the flashfloppy discussion board that folks 
> were having fewer problems with Artery-based Gotek drives when using flash 
> drives supporting USB 3.1.  That's why I made sure I bought a USB drive with 
> USB 3.1.  That may be the standard today so getting USB 3.1 may be 
> unavoidable.
> 
> I loaded the flashfloppy software onto the Gotek using the instructions and 
> Youtube links contained in the flashfloppy Github Wiki.  Some Gotek hardware 
> versions have to be programmed with a USB-to-TTL cable attached to header 
> pins you soldered to the Gotek board, other hardware versions could be 
> programmed using only a USB-to-USB cable.  The Gotek hardware is subject to 
> change so be sure to check the Wiki for the hardware version you receive.  
> There is a lot of information on Gotek programming and hardware upgrades that 
> will help get you going on Youtube.
> 
> To start, I kept the original 180K floppy installed as Drive 0 and the Gotek 
> installed as Drive 1.  I copied the DOS system disk over to the Gotek and 
> then reversed the drives.  My DVI now boots from the Gotek, and the physical 
> floppy drive is available for creating floppy images from physical media.  
> Switching between the system disk and an application disk is done by pushing 
> the image selector buttons and cycling through the images on the flash drive.
> 
> The hardware upgrades available for the Gotek include adding an LCD display 
> and a rotary encoder.  I didn't do any of these as I wanted to make sure I 
> could get the stock Gotek running before attempting any modifications.  I may 
> go back to these at a later date. 
> 
> My FF.CFG which configures flashfloppy features is mostly stock and contains 
> the following entries:
> 
> interface = ibmpc
> host = unspecified
> pin02 = nc
> pin34 = nc
> write-protect = no
> side-select-glitch-filter = 0
> track-change = instant
> write-drain = instant
> index-suppression = yes
> head-settle-ms = 12
> motor-delay = ignore
> chgrst = step
> ejected-on-startup = no
> image-on-startup = last
> display-probe-ms = 3000
> autoselect-file-secs = 2
> autoselect-folder-secs = 2
> folder-sort = always
> sort-priority = folders
> nav-mode = default
> nav-loop = yes
> twobutton-action = zero
> rotary = none
> indexed-prefix = "DSKA"
> display-type = auto
> oled-font = 6x13
> oled-contrast = 143
> display-order = default
> display-off-secs = 60
> display-on-activity = yes
> display-scroll-rate = 200
> display-scroll-pause = 2000
> nav-scroll-rate = 80
> nav-scroll-pause = 300
> step-volume = 10
> da-report-version = ""
> extend-image = yes
> 
> My IMG.CFG file which defines the cylinders, heads, and sectors for the 180K 
> disk format used by the DVI looks like:
> 
> [*.m100dvi.img]
> cyls=40
> heads=1
> secs=18
> bps=256
> h=0
> 
> The configuration above works for me but could probably be tuned for better 
> performance.  I was able to format virtual disk images, write files to the 
> images, and read files from the images with no issues.  The DVI DOS copy and 
> backup utilities all worked as expected.
> 
> Hope this helps you.
> 
> Jerry
> 
> 
>> On Sun, May 23, 2021, 7:21 AM Dan Eicher  wrote:
>> Anyone using a GoTek or HxC floppy emulator with a Tandy DVI?

Re: [M100] Replacement Power Supply

[Joshua O'Keefe]

> On Nov 19, 2021, at 5:59 PM, Patrick McDougal  wrote:
>   Now, I am looking for an AC power supply.  Has anyone identified a good 
> after market replacement or am I better off finding a 6v adapter and rewiring 
> for the unusual negative center.

I've been totally pleased with this one, which I picked up because it was 
ready-to-go.
https://www.arcadeshopper.com/wp/store/#!/6v-power-supply-for-models-100-102-200/p/120510370/category=28313042

Re: [M100] NiCd Battery

[Joshua O'Keefe]

> On Nov 10, 2021, at 6:10 PM, Patrick McDougal  wrote:
> I was hoping for some advice regarding my next step.  Replace?  Remove? Leave 
> it alone?

Hi Patrick!

Please replace or remove until you are ready to replace.  Leaving it alone 
will, in time, result in damage to the system.

> If replacement is recommended, can anyone suggest a good vendor for the part?

This vendor (a member of the list) has provided me with excellent batteries:
https://www.arcadeshopper.com/wp/store/#!/Replacement-Batteries/c/32594049

Re: [M100] Yet Another Calendar Program...

[Joshua O'Keefe]

> Ken,
> 
>   You have unbalanced parenthesis. Can you please correct?

?SN ERROR 
READY

Re: [M100] Yet Another Calendar Program...

[Joshua O'Keefe]

Lloyd, your program looks great and makes me deeply regret blowing up the only 
continuous-feed printer I own with a rushed/botched repair attempt.

Re: [M100] Model 100 printer woes

[Joshua O'Keefe]

On Aug 19, 2021, at 11:20 AM, Lloyd Johnson  wrote:
> Anyway, I thought for the nostalgic aspect, I was going to use the old dot 
> matrix printed labels for Christmas cards this year.

Perhaps only marginally on topic, so please forgive me, but I did a small run 
of holiday cards (about 20 of them) in Print Shop on a Commodore 64 last year.  
I had blown up my dot matrix printer in a carelessly botched repair attempt so 
I had to do some contortions with printer emulation hardware to get them to 
paper.

Several recipients said they knew who the card was from before unfolding it.  I 
guess I have a reputation.

Re: [M100] How to clean plastic?

[Joshua O'Keefe]

> On Jul 26, 2021, at 3:06 PM, Jeffrey Birt  wrote:
> Are you wanting to polish the clear plastic? If so, take a look at Novus 
> plastic polish. I have used it in the past, and it has worked well for me.

I had excellent results with the 3-step Novus polish product on my screen 
cover. I used only the second and third steps, as the first step is intended 
for deeper scratches.  In my case I took no special precautions before 
polishing, such as taping off, and simply removed the top cover from my 102 
(which separates from the keyboard immediately, unlike the 100) and tried to 
follow the instructions that came with the kit.

I was surprised at how good the results were.