Is there anything that can be done to let FrontDoor control a telnet-
only bbs?
---
* Origin: *Square One BBS telnet://sq1.no-ip.org (1:123/22)

Is there anything that can be done to let FrontDoor control a
telnet- only bbs?

hunh? do you mean where FD can handle telnet accesses? if so, then the answer is a resounding "yes"... i've been doing it here for years...

the "trick" i use for it is _not_ following the m$ lemmings and running windows... i (still) run IBM's OS/2 Warp and Ray Gwinn's SIO comm driver replacement package that comes with VMODEM which creates virtual modems...

the key thing to it is virtual modems... no matter what OS you run, you need something to create virtual modems or that will at least tie the comport stuff to the TCP/IP stack... *nix has a way of doing it with DOSEMU and i understand that the newer DOSBOX, which comes in several OS flavors, also provides some method of doing this... unfortunately i've not had any time, extra machines, or
$$$ to throw at an OS i won't use to try to play with this...

what OS are you running?

what BBS software are you running?

how do you envision doing this?

my setup looks and operates exactly the same as it does on the POTS side... in fact, joho told he that it brought tears to his eyes when he telnetted into my system a few months ago and he was greeted with the frontdoor banner as he was passing thru to the bbs O:)

)\/(ark


* Origin: (1:3634/12)

my setup looks and operates exactly the same as it does on the POTS side... fact, joho told he that it brought tears to his eyes when he telnetted into system a few months ago and he was greeted with the frontdoor banner as he passing thru to the bbs O:)

I wish he'd telnet over here and see FD 2.33 ;) .... Just wish it would be updated to fix some zmodem issues and the IP logging via caller id. It
tosses it together as one number instead of how it is reported to FD. :(

EXEBBS 115200 2 10080 1 /2446199124 N/A
^^^^^^^^^^^

Sigh. :( But I will forever use FD! ;)

... Don't worry, I'm fluent in weirdo

--- Renegade v09-30.6 DOS
* Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)

the "trick" i use for it is _not_ following the m$ lemmings and running windows... i (still) run IBM's OS/2 Warp and Ray Gwinn's SIO comm driver replacement package that comes with VMODEM which creates virtual modems...

I don't use OS/2 any longer, so winblows is all thatis left. I use NetSerial (www.pcmicro.com) which emulates com ports for Windows. Works just as well as SIO did IMO.

--- Renegade v09-30.6 DOS
* Origin: His juggling is almost hypnotic. Like a lava lamp. (1:229/426)

my setup looks and operates exactly the same as it does on the
POTS side... fact, joho told he that it brought tears to his eyes
when he telnetted into system a few months ago and he was greeted
with the frontdoor banner as he passing thru to the bbs O:)

I wish he'd telnet over here and see FD 2.33 ;) .... Just wish it
would be updated to fix some zmodem issues

what zmodem issues? and 2.33 is the shareware version??

and the IP logging via caller id. It tosses it together as one
number instead of how it is reported to FD. :(

EXEBBS 115200 2 10080 1 /2446199124 N/A
^^^^^^^^^^^

do you have FD logging it in the log file? what's it look like in there? are you sure that it isn't reported like that to FD? what seems to indicate such? TTBOMK, FD logs and reports the data between the ring signals exactly as it is sent to it...

)\/(ark


* Origin: (1:3634/12)

the "trick" i use for it is _not_ following the m$ lemmings and
running windows... i (still) run IBM's OS/2 Warp and Ray Gwinn's
SIO comm driver replacement package that comes with VMODEM which
creates virtual modems...

I don't use OS/2 any longer, so winblows is all thatis left.

i wouldn't say that... one can still get OS/2 ;) and there's also the *nix stuff but for many, that's a bit harsher world than the had with DOS although there are a lot more features and capabilities that the m$ world is still trying to catch up with...

I use NetSerial (www.pcmicro.com) which emulates com ports for
Windows. Works just as well as SIO did IMO.

great! i don't suppose you have anything written up on yuor setup and how you have FD interfacing with netserial?? it would be a big help for others... i could even add it to the FAQ section in my support forum...

)\/(ark


* Origin: (1:3634/12)

what zmodem issues? and 2.33 is the shareware version??

2.33.mL is the commerical version I paid for years ago. Upgraded from 2.20c.

do you have FD logging it in the log file? what's it look like in there? ar you sure that it isn't reported like that to FD? what seems to indicate suc TTBOMK, FD logs and reports the data between the ring signals exactly as it sent to it...

Hummm .. will look into that. I looked at Netserial's log file and it is reported corectly, but once it hits the DOBBSx.BAT file it gets crapped out. :(

... My mind isn't always in the gutter - sometimes it comes out to feed.

--- Renegade v09-30.6 DOS
* Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)

great! i don't suppose you have anything written up on yuor setup and how y have FD interfacing with netserial?? it would be a big help for others... i could even add it to the FAQ section in my support forum...

Almost EXACTLY the same way SIO was setup, except you just load the program at start (windows startup -- in system tray), and use any FOSSIL (DOS or windows based). That is the only major difference. Otherwise, a virtual comport is a virtual comport. Maybe one day I'll write something up.

... Retreat h*ll! We're just fighting in another direction!

--- Renegade v09-30.6 DOS
* Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)

what zmodem issues? and 2.33 is the shareware version??

2.33.mL is the commerical version I paid for years ago. Upgraded
from 2.20c.

ahhh... i just didn't remember the version numbers...

do you have FD logging it in the log file? what's it look like in
there? are you sure that it isn't reported like that to FD? what
seems to indicate such TTBOMK, FD logs and reports the data between
the ring signals exactly as it sent to it...

Hummm .. will look into that. I looked at Netserial's log file
and it is reported corectly, but once it hits the DOBBSx.BAT file
it gets crapped out. :(

it is possible that netserial is formatting what you are seeing in its logs...

)\/(ark


* Origin: (1:3634/12)

great! i don't suppose you have anything written up on yuor setup
and how you have FD interfacing with netserial?? it would be a big
help for others... i could even add it to the FAQ section in my
support forum...

Almost EXACTLY the same way SIO was setup, except you just load
the program at start (windows startup -- in system tray),

ok... so not in the config.sys as a very lowlevel device driver... hummm... that may explain some of the problems i've read about with several windows based virtual modem "tools"...

and use any FOSSIL (DOS or windows based). That is the only
major difference.

cool... with SIO i don't have to load anything "extra" like x00 or bnu... just make sure that the vx00 driver is loaded...

Otherwise, a virtual comport is a virtual comport. Maybe one day
I'll write something up.

definitely include something about dialing... i know that that is one area of difference...

)\/(ark


* Origin: (1:3634/12)

it is possible that netserial is formatting what you are seeing in its logs

No ... I asked them. They emailed JoHo and Mats and got no response. PcMicro said that it was an FD issue and was willing to tell JoHo or Mats exactly what to change/fix, but no one ever cared enough to write back. :(

... OPINIONS? I have lots. Which one would you like?

--- Renegade v09-30.6 DOS
* Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)

it is possible that netserial is formatting what you are seeing in
its logs

No ... I asked them. They emailed JoHo and Mats and got no
response. PcMicro said that it was an FD issue and was willing to
tell JoHo or Mats exactly what to change/fix, but no one ever
cared enough to write back. :(

that's wierd... i seem to recall something somewhere to do with the formatting of the DFRS stuff but i don't recall if it is/was anything in FD or if it was settings in the modems i was using at the time... i don't know that it is anything critical, though... is it?

)\/(ark


* Origin: (1:3634/12)

that's wierd... i seem to recall something somewhere to do with the formatt of the DFRS stuff but i don't recall if it is/was anything in FD or if it w settings in the modems i was using at the time... i don't know that it is anything critical, though... is it?

22:21:29 Processing NetMail folder
22:21:29 No messages to send in this event
= 22:21:31 RING
= 22:21:34 CONNECT 115200/141158126138
+ 22:21:34 Incoming call at 115200 BPS
22:21:34 Sending text in \FD\BANNER2.TXT

Here's my log file. Wish I knew how to work around this. I can guess what the IP is, or check the netserial log, but it would be nice to have it imported into the BBS correctly tho. :(

... Things that appear simple, usually aren't.

--- Renegade v09-30.6 DOS
* Origin: The Titantic BBS Telnet - ttb.slyip.com (1:129/305)

that's wierd... i seem to recall something somewhere to do with
the formatt of the DFRS stuff but i don't recall if it is/was
anything in FD or if it was settings in the modems i was using at
the time... i don't know that it is anything critical, though... is
it?

22:21:29 Processing NetMail folder
22:21:29 No messages to send in this event
= 22:21:31 RING
= 22:21:34 CONNECT 115200/141158126138
+ 22:21:34 Incoming call at 115200 BPS
22:21:34 Sending text in \FD\BANNER2.TXT

Here's my log file. Wish I knew how to work around this. I can
guess what the IP is, or check the netserial log, but it would be
nice to have it imported into the BBS correctly tho. :(

that's in IP number??? it looks like a connect message to me...

here's what i get...


= 14:25:16 RING
= 14:25:20 RING
= 14:25:20 CONNECT 57600/ARQ/TEL FROM 192.168.42.7
+ 14:25:22 Incoming call at 57600 BPS
14:25:24 Sending text in X:\FD\BAN11.FD


definitely a different format... you'll probably have an easier time getting the folk who wrote your virtual modem driver to conform to a/the more standard format... the above is more like the following industry standardized format single line connect messages...

= 12:00:35 RING
= 12:00:41 RING
= 12:00:58 CONNECT 24000/ARQ/V34/LAPM/V42BIS

i can see why joho wouldn't want to have to recode that section... what you show is really "out there" ;)

not trying to be negative or dissuade you... it doesn't really look like bug that i can see...

)\/(ark


* Origin: (1:3634/12)