If one wants to use tcpser to listen on a TCP port then send modem commands to older software that is listening on a serial port, am I correct in believing that tcpser "creates" a virtual serial port and
that the serial port you are trying to emulate does not actually have to physically exist on the host machine?
commands to older software that is listening on a serial port, am I correct in believing that tcpser "creates" a virtual serial port and
that the serial port you are trying to emulate does not actually have to physically exist on the host machine?
On 05-11-20 10:11, alterego wrote to Blue White <=-
In my use case, I use another tool tty0tty which creates a virtual null modem. On one side tcpser listens (eg: tnt0), and on the other side the serial application connects to (eg: tnt1). In my case, I pass tnt1 to dosemu - which makes it available to a DOS machine as COM1.
Re: tcpser
By: Blue White to All on Sun May 10 2020 06:39 pm
commands to older software that is listening on a serial port,
am I correct in believing that tcpser "creates" a virtual
serial port and that the serial port you are trying to emulate
does not actually have to physically exist on the host
machine?
Not exactly.
tcpser is a virtual modem, and basically bridges a serial device to
a TCP socket and responds "OK" to modem AT commands.
You need to give it a device to listen on - which could be ttyS0
(if you have something physically connected to it).
In my use case, I use another tool tty0tty which creates a virtual
null modem. On one side tcpser listens (eg: tnt0), and on the other
side the serial application connects to (eg: tnt1). In my case, I
pass tnt1 to dosemu - which makes it available to a DOS machine as
COM1. ...????
You need to give it a device to listen on - which could be ttyS0
(if you have something physically connected to it).
If the /dev/ttyS1 exists, for example, but there is no actual physical hardware serial port that ttyS1 points to, it won't work then?
You need to think of serial ports as a piece of string, one end is
the kernel, the other end is the external port. You cannot have two applications (eg: dosemu and tcpser) attached on the kernel side -
it just doesnt work. (Hence tty0tty).
...????
On 05-11-20 15:24, Blue White wrote to alterego <=-
If the /dev/ttyS1 exists, for example, but there is no actual physical hardware serial port that ttyS1 points to, it won't work then?
In my use case, I use another tool tty0tty which creates a virtual
null modem. On one side tcpser listens (eg: tnt0), and on the other
side the serial application connects to (eg: tnt1). In my case, I
pass tnt1 to dosemu - which makes it available to a DOS machine as
COM1. ...????
That is what I would be hoping to do... have a dosemu machine which
would identify an emulated modem as a COM port.
So, using your string analogy, if one wants to use tcpser to communicate with a DOS BBS running in dosemu, where does tty0tty fit onto the
string?
One side of the string (/dev/tnt0) is tcpser, the other side of the
string (/dev/tnt1) is (in my case) DOSEMU - which is configured it
as COM1.
So when a dos program opens COM1 and sends "AT", tcpser says "OK".
If you "ATDT <something>", tcpser will attempt to make a connection
to whatever <something> is resolved to. If it connects, then
anything between the TCP socket will be sent to COM1 and visa
versa. ...????
And tty0tty sets up the two ends of the string for tcpser and dosemu to send/listen on, right?
Re: RE: tcpser
By: Blue White to alterego on Wed May 13 2020 06:54 pm
And tty0tty sets up the two ends of the string for tcpser and
dosemu to send/listen on, right?
Right.
When you load it you'll get 4 (strings) pairs of devices:
/dev/tnt0 /dev/tnt1
/dev/tnt2 /dev/tnt3
...
/dev/tnt6 /dev/tnt7
You have something connect to the "odd" end, and something else
connect to the "even" end and whatever is written to 1 end will
appear on the other. ...????
OK so that is just the bomb! <grin> I got tty0tty and tcpser installed in a virtualbox devuan ascii machine. Also installed dosemu. The only issue I am having now is that the virtual machine does not have xwindows on it. So dosemu runs but, unlike on my host, if I fire up a dos
program all hades breaks loose as far as the display settings go. I
need to figure out how to fix that, probably in my dosemu.conf.
Re: RE: tcpser & dosemu!
By: Blue White to alterego on Fri May 15 2020 07:39 pm
OK so that is just the bomb! <grin> I got tty0tty and tcpser
installed in a virtualbox devuan ascii machine. Also
installed dosemu. The only issue I am having now is that the
virtual machine does not have xwindows on it. So dosemu runs
but, unlike on my host, if I fire up a dos program all hades
breaks loose as far as the display settings go. I need to
figure out how to fix that, probably in my dosemu.conf.
It is pretty awesome when stuff like this works ! :)
ENTER key twice and as best as I can tell only the ENTER key. All other key strokes appear only once.
Any ideas there?
On 05-18-20 08:34, alterego wrote to Blue White <=-
See what happens when you log into my (1990) BBS. Its the setup I've described with tcpser and tty0tty.
No idea at all.. I certainly dont have that problem.
Where did you pull your code from? I pulled mine from:
Re: RE: tcpser & dosemu!
By: Blue White to alterego on Mon May 18 2020 02:40 pm
Where did you pull your code from? I pulled mine from:
Oh, I wasnt aware that there may be multiple sources.
OK, it looks like my tty0tty is from here: https://github.com/freemed/tty0tty.git
And tcpser is the same as yours:
https://github.com/FozzTexx/tcpser.git
I'm wondering now if there were changes in any of the forks...
...????
Could be. However, one thing I noticed is that I have the
double-CR issue with syncterm and with the linux telnet client, but
I don't have the issue with apam's magiterm, or with qterm
(although it does not render the ANSI exactly right).
In past, I have had a similar issue with syncterm and my DOS BBS,
but only after I had downloaded a file. Otherwise, one CR = one
CR.
It may be because telnet specifies a line ending to end with CR+LF,
where as magiterm just sends CR I think. It probably should send
CR+LF but I found dropping the LF made it more "compatible".
Some things like BRE etc used to do double line feeds, which I
narrowed down to CR+LF as dos tends to just expect CR.
Can you throw a link up again, I missed it the first time and
would like to do something for parents that have had a rough way
to go in life.
Also I hope you don't mind I sucked up your old domain name and am
going to use it being I a little bit prev!
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 512 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 192:10:27 |
| Calls: | 8,283 |
| Files: | 15,515 |
| Messages: | 927,806 |