Just an update on how my explorations went today. First I have to apologize to the group for misleading about the cable. When I took the covers off the cable I built I was dismayed to find that I had connected all control signals as indicated in the documentation. I remembered that I started out to do just a 3 wire configuration but changed my mind and did a full pinout. So I misinformed you. I do have a cable in the recommended configuration.
My USB serial cable was producing +/- 6V which is enough to get good TTL transitions on the Model 100 receivers. I can't check the receivers in the USB cable but I have no problem with TX or RX during testing. I could not get TEENY.EXE to work for me on DOSBOX. Could be something odd with my laptop (Dell Windows 10 Pro 64 bit) or USB cable (I don't even know if there's a brand on it). I cold started the M100 and executed the TEENY.DO text file download from Term. I loaded that file in basic and ran it. That seemed to work. I ended up with a TEENY.CO <http://teeny.co/> file. I installed LaddieAlpha on my Windows laptop, started it in a Windows command prompt, and gave it the COM port and the number 6 as command line parameters. LaddieAlpha started up fine with no error messages. But when I attempted to run TEENY.CO, the Model 100 just beeped and returned to the menu. I couldn't get a prompt from TEENY.CO. Just a beep and back to the menu. Maybe something I did wrong. I cold started the M100 again and installed mComm on my Windows laptop. Then I installed TEENY.CO following the on-screen instructions from mComm. After the transfer completed I followed the instructions on the M100 and started TEENY.CO and it worked! I tested a few simple file transfers. All worked as expected. I shut down mComm and started LaddieAlpha as I did previously. I started TEENY.CO on the M100 and it worked! I tested a few simple file transfers. All worked as expected. It appears that the TEENY client install using mComm got things working for me. I don't know why. But, YEA! It has been a lot of fun reading the responses to my question. I am grateful that all of you took the time to answer back. Your advice was right on. I've learned a lot today. Sincerely, Jerry On Tue, May 4, 2021, 6:07 PM John R. Hogerhuis <jho...@pobox.com> wrote: > I guess. But TBACK's ambition was always to be a command line Swiss Army > Knife for file transfer, in the absence of any client software, based on > the RUN"COM:98N1E" magic incantation. > > My main point with LaddieAlpha is laddiealpha was meant to be headless. It > sits over there on another machine and runs. Your only interface to it is > TS-DOS or TEENY on a laptop. > > Similar I think to Hurd's vision for dl. > > You could interactively use it to inject a DO file in a special mode if > such a feature were added. But given many other ways to do it, and it > not being its core mission, I just didn't feel a need to clutter it up. I > may add it eventually just to check off the box though, who knows. Like I > said my preference is to add a full-screen CLI mode to Laddie operable via > TELCOM. Since then I can offer other file operations including bootstrap > with a UI. > > For interactive TPDD emulators like mComm, DLPilot, an injector makes > perfect sense to me. The idea is a human operator. > > "The telcom way is just simply ridiculous" > > I think you're overstating it. It's a nice way to transfer a text file. > > LAPTAP.EXE's way is better, you should try that, I think you'll like it. > > -- John. >
