problem now
I would first think of the dial translation that also strips and adds prefixes.
I would first think of the dial translation that also strips and adds
prefixes.
Yes. But how to strip or add a space? :)
Hello All,after
What would be the easiest way to make FD to call to a non-standard telnet port with vmodem/sio on os/2 system? Vmodem/SIO needs the port number
the host name, separated by _space_. I cannot find a correct format of PHONE statement in FDNODE.CTL. The space character seems to be the problem now.
On 2017 Sep 26 07:46:38, you wrote to All:
Hello All,
What would be the easiest way to make FD to call to a
non-standard telnet port with vmodem/sio on os/2 system?
Vmodem/SIO needs the port number after the host name, separated
by _space_. I cannot find a correct format of PHONE statement in
FDNODE.CTL. The space character seems to be the problem now.
i use environment variables so i have entries like this in
FDNODE.CTL...
PHONE 2:2448/400 $[tobiasB1]
Hi Tommi!
I would first think of the dial translation that also strips and adds
prefixes.
Yes. But how to strip or add a space? :)Em, err... well, I... hmm....
[silently leaving the room, pretending to go to the restroom] :-D
What would be the easiest way to make FD to call to a
non-standard telnet port with vmodem/sio on os/2 system?
Vmodem/SIO needs the port number after the host name, separated
by _space_. I cannot find a correct format of PHONE statement in FDNODE.CTL. The space character seems to be the problem now.
I can make a private nodelist with phone entry that contains the
space character. That way FD dials out ok. But that is not very
easy way. :)
What would be the easiest way to make FD to call to a
non-standard telnet port with vmodem/sio on os/2 system?
Vmodem/SIO needs the port number after the host name, separated
by _space_. I cannot find a correct format of PHONE statement in
FDNODE.CTL. The space character seems to be the problem now.
I can make a private nodelist with phone entry that contains the
space character. That way FD dials out ok. But that is not very
easy way. :)
If you cannot get this to work, let me know and I'll compile a
version which translates a given character (% perhaps) to spaces.
Many functions in FD exist and/or behave the way they do for a
reason. If you read the documentation from top to bottom (I'm not
asking you to :)), you'll see there are a *lot* of flexibility and configuration options. That is not to say that things are not
missing.
Things are missing. And they will be addressed. That is why I'm here.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,049 |
Nodes: | 15 (1 / 14) |
Uptime: | 90:27:40 |
Calls: | 235,752 |
Calls today: | 2 |
Files: | 60,336 |
D/L today: |
134 files (102M bytes) |
Messages: | 20,616,130,458 |