Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Communications Echo  <--  <--- Return to Home Page
   Networked Database  Communications Echo   [28 / 36] RSS
 From   To   Subject   Date/Time 
Message   mark lewis    James Digriz   Analog modems in the digital age.   April 5, 2018
 11:09 PM *  

 On 2018 Apr 04 17:11:44, you wrote to All:

 JD> Appreciate any comments or direction, and sorry if this is well-trod
 JD> ground in this echo.

actually, it hasn't really been trod on enough anywhere... it is also much
simplier than you're thinking...

older systems that still want to talk to analogue modems simply use a shim to
convert to telnet and a virtual modem...

in the windows world, the best and pretty inexpensive package is Mike Ehlert's
netserial and netfoss packages... netfoss handles the FOSSIL type stuff... i
don't recall if netserial is also needed or if they work independently... they
can be found on many BBSes as well as Mike's PCMicro site...

in the OS/2 world, the best is still the SIO package from x00 guru Ray Gwinn...

in the linux world, most of the mailers and BBSes talk directly to the whatever
 port they are configured on... there's no virtual modem or shim needed... if
you're running DOS doors on your native linux BBS, use DOSEMU and set all doors
 to talk to COM1... there's a setting in DOSEMU, command line i think, that
handles the tying together of the fake comm port and the telnet, ssh, or rlogin
 ports... native synchronet and mystic both operate this way... synchronet, i
know, offers telnet, ssh, rlogin, http, https, ftp and ftps access to it...

in today's world, the mailers operate, mostly, on their own port (24554 default
 for binkp) and so there's no real need for the old style front end mailer
sharing the same port as the BBS... it can still be done, though... i do it
here with my frontdoor/remoteaccess setup running on OS/2... there are not very
 many systems out there doing this so there's not much mail being transferred
over telnet mailer connections... the majority of today's systems are using
binkd or have a mailer that offers the binkp protocol...

i don't know if that answers your question(s) or not... hopefully it does help
some...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... You folks telling me that intolerance is a Traditional Family Value?
---
 * Origin:  (1:3634/12.73)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Communications Echo  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0925 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_t7phel59eqai9rkgril5ie59h5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_t7phel59eqai9rkgril5ie59h5, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_t7phel59eqai9rkgril5ie59h5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0