./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.
