|
Post by Leif Bloomquist on Jul 6, 2004 4:38:07 GMT -5
Get it here: www.jammingsignal.com/files/I'd appreciate it if you could test it out and give me feedback on bugs or odd behaviour, before I release it to the hoi polloi on comp.sys.cbm . If you're already running BBS Server, keep your old copy separate for a fallback. However, if you copy your telnetbbs.ini file into the new directory, it will pick up all your old settings and assign defaults to the new ones. (But you must hit Save+Apply to update the file). New features/bugfixes: - Got rid of the popup boxes if an unknown IAC code is received (when a Real Telnet session is in progress).
- Checks the first incoming byte of the session, and 255="Real" Telnet session (i.e. to Linux), anything else means a Telnet BBS. In the latter case, data will be passed transparently so file transfers should work.
- If there is only 1 IP address on the system, always use it.
- Replaced the Sleep() for staying offhook with a Timer.
- Added an option for echoing data back to BBS when in command mode.
VB6 Source code is included in a zip-within-the-zip. FYI, there is some very old documentation here. I'll update this once the 1.0 feature set is stable. home.ica.net/~leifb/bbs/docs/
|
|
|
Post by Leif Bloomquist on Jul 6, 2004 11:50:28 GMT -5
Oops, found a bug. It will only stay off-hook for 1/1000 of the time you specify. Have fixed and will upload new files after supper.
|
|
|
Post by Riktronics on Jul 6, 2004 12:12:04 GMT -5
Hey, I tried it out for a second (it still doesn't disconnect when it receives a break, and I don't have time to edit that and recompile tonight) but it did make me think of another "feature request" that I had totally forgotten about. When it says "Connecting" you have it in the code just that way, so in CG mode it appears as "cONNECTING". When I changed the break in mine I also changed that to "connecting" so you either get "CONNECTING" in CG mode or "connecting" in ASCII. I know, its a very minor detail, but it might be nice if that string was changeable from the program. Having it disconnect when it gets a break (or the option) would be sweet to, but I have a feeling I am the only one that needs that...
Thanks!
|
|
|
Post by CosmoCommander on Jul 6, 2004 14:28:44 GMT -5
[/li][li]Checks the first incoming byte of the session, and 255="Real" Telnet session (i.e. to Linux), anything else means a Telnet BBS. In the latter case, data will be passed transparently so file transfers should work.[/quote] Leif, you are a genius. I am uploading CG Term v1.6 to my BBS right now as a test, using CG Term and X-Modem. So far, 247 blocks with NO ERROR.
|
|
|
Post by CosmoCommander on Jul 6, 2004 15:51:55 GMT -5
I just finished uploading CG Term to the BBS. 1622 blocks sent, with ZERO errors.
I also attempted to connect to the BBS from my wife's computer, while uploading, and got the busy message. Too cool.
Also, the amount of RS232 overruns and framing errors are few and far between now. This is fantastic!
Great work, Leif. ;D
|
|
|
Post by Leif Bloomquist on Jul 7, 2004 3:36:03 GMT -5
Leif, you are a genius. I am uploading CG Term v1.6 to my BBS right now as a test, using CG Term and X-Modem. So far, 247 blocks with NO ERROR. Hey, thanks for the feedback. Actually, the tip about checking the first byte in the session came from brain, so he gets the credit for that one.
|
|
|
Post by Leif Bloomquist on Jul 8, 2004 15:12:00 GMT -5
"Supper" took a bit longer than expected!
Anyway, the fixed RC2a is up, same site.
Rik, I'll make those changes for you and add them to RC3.
Has anyone tested it for dialing out yet?
|
|
|
Post by CosmoCommander on Jul 8, 2004 16:48:36 GMT -5
Actually, the tip about checking the first byte in the session came from brain, so he gets the credit for that one. In that case, good work Jim!
|
|
|
Post by Dan on Jul 9, 2004 2:12:21 GMT -5
I have found one bug whilst I was testing. If the bbs is down ie nothing on the serial port. The telnet session sits with connecting. If you exit the telnet session. The program gives a run time error and quits. But otherwise it's looking very good.
Thanks Dan
|
|
|
Post by Leif Bloomquist on Jul 10, 2004 10:45:02 GMT -5
I have found one bug whilst I was testing. If the bbs is down ie nothing on the serial port. The telnet session sits with connecting. If you exit the telnet session. The program gives a run time error and quits. But otherwise it's looking very good. Thanks Dan! I found and fixed the problem. RC3 is now available, same site as in the first post. This includes the changes Rik requested. Plus, I added an option for one other cool feature: If you're using BBS Server for dialing out from a Terminal program, you have the option of having any Winsock errors sent as well. This is useful if you're running BBS Server "headless" (ie, without a monitor) like I do. For example (not verbatim): atdt nonexistentsite.testing.cx NO CARRIER Authoritative answer: Host not found.
atdt 192.168.7.20 NO CARRIER Connection refused by remote host.Unless some horrible bug is found, I'll release this as 1.0 to the community at large tomorrow.
|
|
|
Post by CosmoCommander on Jul 10, 2004 18:13:06 GMT -5
RC3 is working good for me.
|
|
|
Post by CosmoCommander on Jul 11, 2004 15:54:17 GMT -5
I was still running RC2. I didn't notice that you had change the name of the .EXE file from Commodore BBS Server.exe to BBS Server.exe. I was still using my old shortcut, and it was pointing to Commodore BBS Server.exe. Haha. I have it fixed now, and will perform my tests over again.
|
|
|
Post by CosmoCommander on Jul 11, 2004 16:18:28 GMT -5
Yep. RC3 is working great. It is still allowing connections and uploads. ;D
|
|
|
Post by CosmoCommander on Jul 16, 2004 11:42:18 GMT -5
I've noticed a couple of things that aren't real big problems:
1. After logging onto the BBS (Image) locally, the BBS Server has to be exited and restarted to leave "Off Hook" status and return to "Waiting" status.
2. After telling BBS Server to Not Accept Calls, you have to exit and restart for it to accept calls again.
|
|