sudo cp ./dl /usr/local/bin sudo chmod 755 /usr/local/bin/dl bkw@miata:~$ ls /dev/ttyUSB* /dev/ttyUSB0
bkw@miata:~$ cd ~/Documents/TRS-80/Model_200/files bkw@miata:~/Documents/TRS-80/Model_200/files$ ls DCPREP.DO RUN-CO.DO SERIAL.DO START.DO bkw@miata:~/Documents/TRS-80/Model_200/files$ sudo dl /dev/ttyUSB0 -v -p=. At this point, dlplus is running and you can use teeny or ts-dos etc from a m100. ----------- Before all that, the teeny installer requires a little more care. This you do just once to install: sudo cp teeny-linux /usr/local/bin/teeny sudo chmod 755 /usr/local/bin/teeny This one you have to do any time the usb device changes, or after any reboot if your /dev is dynamic (most are these days): sudo ln -sf /dev/ttyUSB0 /dev/ttyd0 Then you can run just "teeny" and follow the prompts carefully. teeny just assumes /dev/ttyd0, it's not settable by command line as far as I can tell. ----------- -- bkw On Nov 27, 2017 11:05 PM, "John R. Hogerhuis" <[email protected]> wrote: > Maybe try it with sudo to see if it’s a permissions problem. > > Also type dmesg to see if there are any kernel errors after it exits. > > Another possibility would be compile for debug and run it under gdb to see > if it hits an exception. Or step through to see where it fails. > > — John. > > On Mon, Nov 27, 2017 at 7:53 PM Peter Vollan <[email protected]> wrote: > >> ./dl /dev/ttyUSB0 puts me right back at the command prompt. And I can >> see ttyUSB0 in the /dev directory. Did I miscompile desklink? >> >> >> On 27 November 2017 at 15:37, John R. Hogerhuis <[email protected]> wrote: >> > When you plug in your usb serial device you can type >> > >> > dmesg >> > >> > And it will print out recent kernel messages. You can usually tell what >> > /dev/ttyUSBx device just got added from the scrawl. >> > >> > — John. >> > >> > On Mon, Nov 27, 2017 at 3:34 PM Peter Vollan <[email protected]> >> wrote: >> >> >> >> I am not certain which USB port I am on. But on the other hand, >> >> desklink gives the say result whatever port I enter, or if I enter >> >> none at all. >> >> >> >> On 27 November 2017 at 15:17, John R. Hogerhuis <[email protected]> >> wrote: >> >> > Shouldn’t do that. It should run and stay running unless you hit >> ctrl-c >> >> > >> >> > Guessing there’s a hardware problem with the port, or a software / >> >> > permissions issue. >> >> > >> >> > You could also try LaddieAlpha. >> >> > >> >> > — John. >> >> > >> >> > On Mon, Nov 27, 2017 at 3:14 PM Peter Vollan <[email protected]> >> >> > wrote: >> >> >> >> >> >> When I run "./dl" followed by the usb port of my usb adaptor, I just >> >> >> get the command line again. Shouldn't dlplus do something else, like >> >> >> it does in DOS? Dlplus seemed to compile fine in the first place. >> >> >> >> >> >> I realise that another possible wrinkle is that my cable(s) is not >> >> >> working. I am using a Radio Shack usb to serial cable and what I >> >> >> believe to be a null modem cable. >> >
