Telnet BBS need some advice I think. reddit / bbs ---------------------------------------------------------------------- Vaneshi · 2014-07-25 13:36 I'm taking a trip down nostalgia avenue and getting a late 90's BBS running via telnet. So far I've got RemoteAccess 2.6.2 firing up, complaining I've not given it any .ANS files and shutting down. :) Thing is, when using telnet it doesn't send back a CONNECT xxxxxx string when RA sends ATA. Is this just because I'm using a generic telnet client instead of one aimed at BBS's, do I need a different FOSSIL than x00 or is it something I can jiggle in RA (i.e. when it detects RING from the modem is interprets that as CONNECT 14400)? Once I figure this out and get the ANSI done... then on to Fidonet (if I can figure out where the UK coordinator is LOL). ---------------------------------------------------------------------- derfherdez · 2014-07-25 15:25 The only FOSSIL driver I've used for telnet was [RLFOSSIL](ftp://archives.thebbs.org/fossil_drivers/rlfossil.zip), which worked pretty well. The fossil driver should send the connect string, I used the vmodem,sio stuff on OS/2 for my board and that's how it's handled. I managed to use [Windows 3.0 and rlfossil](http://virtuallyfun.superglobalmegacorp.com/?p=1130) and got a multinode board running. I'm pretty sure the issue with Windows/386 was me configuring the nodes incorrectly. Are you running this under emulation or on a physical computer? ---------------------------------------------------------------------- Vaneshi · 2014-07-25 15:42 Emulation, DOSBox specifically and using it's serial to telnet system. ---------------------------------------------------------------------- derfherdez · 2014-07-25 15:55 Oh.... drop the fossil, and set the serial port to the modem emulation it'll work much better. when you telnet in, it'll "RING" which is all done in dosbox. I mostly use it to dialout, but it works pretty good. ---------------------------------------------------------------------- Vaneshi · 2014-07-25 16:09 It's already set to modem emulation: serial1=modem listenport:5000 Without the FOSSIL driver RemoteAccess (or Proboard for that matter) doesn't find the modem. With the FOSSIL I can connect to the board; although I need to manually type in CONNECT on the client but after that it's working fine. It's just getting the software to not wait for a response from ATD and assume it's a v90 connection whenever the 'modem' has an inbound call. ---------------------------------------------------------------------- derfherdez · 2014-07-25 16:13 not even generic hayes? open up a com program, and make sure you can atdt to something... vert.synchro.net or whatever... then with the term program open telnet to yourself it should ring ring then you type in connect and it should .. connect... id guess there is an init string goofing it...? ---------------------------------------------------------------------- Vaneshi · 2014-07-25 16:26 > then you type in connect and it should .. connect... It does. I need to automate the typing of "connect " > id guess there is an init string goofing it...? That's where I am currently, I'm also pondering poking at RA's modem responses... kind of : If modem says RING process it as "CONNECT " sort of thing. Still it's all good for a giggle. Kind of tempted to throw an actual modem in the mix just for the lulz :D ---------------------------------------------------------------------- derfherdez · 2014-07-25 16:55 it's been a while so yeah when you 'dial' through telnet it'll go RING RING to which the board answers ATA and then the 'modem' tells the board CONNECT 57600 it should do it automatically, and I just fired up procomm plus and it does... [you get the idea](http://i.imgur.com/dTjLipt.png).. test it in a terminal. also my preferences... [serial] serial1=modem listenport:5000 ---------------------------------------------------------------------- Vaneshi · 2014-07-25 17:11 Hmm... we've got the same serial1 settings but different responses... I'll keep poking at it until it stops being fun LOL :D ---------------------------------------------------------------------- derfherdez · 2014-07-25 17:21 ah-ha.. obviously thats the problem ;) im using stock dosbox 0.74 on OS X... Id try different builds of dosbox. ---------------------------------------------------------------------- Vaneshi · 2014-07-25 18:08 SHE RIDES! Got it signaling a connection... then wondered why RA wasn't seeing it. Turned the cycles down and it started seeing 'stuff' (garbage) a little faster and CONNECT 57600 dully appeared. Thanks for the help :) EDIT: And now it doesn't... at least I know it CAN work LOL. ---------------------------------------------------------------------- derfherdez · 2014-07-26 01:34 that is very strange.. I was using a default 3000 cycles, I guess more is less in this case... ---------------------------------------------------------------------- mro_1337 · 2014-07-27 14:34 only fossil driver you should be using is ADF use atz as your init string change your modem result strings to match what is really being sent. i've always used dosbox with the hal patches aka bbsdosbox for this stuff. anyways, better to use a win32 vm and run it. with dosbox you will run into a lot of issues. ---------------------------------------------------------------------- archaicbinary · 2014-08-09 22:23 I have use a few different DOSBox builds for BBSing and I found http://ykhwong.x-y.net/ to be one of the best. It has all the HAL patches plus more that really help. I needed this build running a DOS BBS because it has date rollover patches that actually kept the correct date and time when going over 24 hours runtime. I used it to run real DOS 6.22 instead of it's emulated DOS because some games were complaining and just not running correctly.