Looks like my host is having some routing issues with the IP block that is dedicated to the BBS server. I have tickets in and hopefully will be solved soon. Not everyone may be affected, but somewhere they are dropping packets to a specific IP block, but not all my blocks.
I recently joined and not having a Synchronet BBS I had to make my own client to work with their service. As promised I am also releasing the source.
It is written in C# against .NET 2.0 and *might* work in mono on linux. You will have to test.
Update: I made a small change to the dropped carrier handling and disconnections. The door should now handle dropped carrier and exit correctly. Let me know if you have issues.
Update: Removed Github links.
I have removed the flash versions of the telnet client on the website and replaced with an HTML5 HTTPS Websockets only applet. All connections to the BBS from this website are 100% encrypted. Downloading and uploading files works as well through the applet, which was the only reason I was keeping the flash version around. If you are connecting via telnet client instead of the applet, your connections are not encrypted. Just a heads up.
I have enabled RIPScrip support on the BBS. Although most will never use it, it’s nice to have the option. Currently all menus are stock, but the mouse does work.
There are some small issues with the door games that do support RIP, sometimes the mouse is not over what the game expects to be a button. LORD does this sometimes where you have to move the mouse below the button and click. I am not sure what is causing this problem currently.
If you have a RIPScrip enabled telnet client like RIPTel or RIPTerm running inside a DOSBox give it a shot. You can connect with any telnet client to the main address: telnet://ssl.archaicbinary.net
During all of my testing running a full BBS inside DOSBox I have had to test many different compilations. Take note that I am running virtual modem software that adds virtual modems to Windows and then DOSBox just does a directserial pass-thru. Also, I am running real DOS 6.22 inside the DOSBox as a real OS, using DOSBox as just the PC emulator.
At first I tried using the normal DOSBox installation, and it did not have network card support to allow DOS to connect to a file server. Without network card emulation, I could not run multiple copies of DOSBox and TriBBS over the network for each node. So this one is out.
I then tried H-A-L 9000’s DOSBox build. This build worked great, networking support and everything ran fine…sorta. HAL9000’s build does not have the required patches to allow the date and time to be synced to the host machine once the clock rolls over past 24 hours. Instead the time rolls, the date does not. For a BBS, this is a requirement. Damn.
Okay, after some more searching I found the raw source code patch but I didn’t feel like building my own DOSBox at the moment, unless I had to.
I then found Taewoong Daum SVN DOSBox builds. He has all of the HAL 9000 patches as well as a date roll over patch that works very well.
After using the Taewoong build, I had DOSBox running TriBBS great. So far stability has been awesome, the machines run very fast, and I am running four nodes on the same ESXi virtual machine.
If your looking for a DOSBox build that has a nice list of patched features try the Taewoong build.
Update: The Taewoong build provides NE2000 network card support and following some information on http://www.jacco2.dds.nl/samba/dos.html#msclient should get you moving in the right direction for DOS networking.