|
|
Post by Leif Bloomquist on Apr 4, 2004 22:19:32 GMT -5
OK, there are a couple of outstanding issues yet, but this should let interested parties try some of the new stuff. home.ica.net/~leifb/bbs/BBS%20Server%201v0RC1.zipNew: -Added IAC Telnet Response Codes. Says WONT to every DO and DONT to every WILL. Was able to telnet to Linux boxen with this. -Fixed bug with COM port initialization order, so multiple instances can be run. -Fixed bug with ATH0 wrongly saying BBS was in "Waiting" state. -CR or LF can now be used as delimiter before AT commands ( Fox please test this) TODO: Fancier Hayes emulation to parse the entire string. As before, it only parses the first one after the "AT". Source will be forthcoming, hopefully tomorrow.  |
|
|
|
Post by Dr. Video/ADDiXiON on Apr 4, 2004 23:18:46 GMT -5
Outstanding! I will try to get it online tomorrow night!
|
|
|
|
Post by Dr. Video/ADDiXiON on Apr 5, 2004 13:22:53 GMT -5
Hmmm, I put my board back up on RC1 and everything was fine when I left for work, now when I try to telnet in, I don't even get an answer. I wonder what has crashed...won't know until I get home  |
|
|
|
Post by Jeff Ledger on Apr 5, 2004 15:02:09 GMT -5
Leif,
Looking forward to trying your new BBS server out! The ability to telnet to a linux box should permit the continued work on my linux/cbm bbs -- Did you use any special settings (login defs) on the linux site for the screenshots I saw?
Jeff
|
|
|
|
Post by Dr. Video/ADDiXiON on Apr 5, 2004 19:53:36 GMT -5
Hmmm, I put my board back up on RC1 and everything was fine when I left for work, now when I try to telnet in, I don't even get an answer. I wonder what has crashed...won't know until I get home Weird, I just got home, everything is up and running. I can CG Term to the BBS from my Win box. Must have been a problem with work? Hey someone call me now! hehe |
|
|
|
Post by Dr. Video/ADDiXiON on Apr 18, 2004 11:51:59 GMT -5
Leif, here is the latest sample from my BBS log, can you please briefly analyze it, maybe guesstimate what is causing the errors? Could it be an issue with running the BBS behind my LinkSys router? Maybe it is screwing up the timing somehow?
4/17/04 9:55:13 PM ATH0Z0
4/17/04 9:55:18 PM Connection from 192.168.1.1
4/17/04 9:55:18 PM Raising RTS on COM3
4/17/04 9:55:18 PM Raising DTR on COM3
4/17/04 9:56:16 PM RS232 Error: Overrun! Data Lost.
4/17/04 9:58:01 PM Data Set Ready = False
4/17/04 9:58:01 PM BBS closed connection via DSR, closing Telnet session 192.168.1.1
4/17/04 9:58:01 PM Using COM Port 3
4/17/04 9:58:01 PM Keeping COM Port Open (Hayes Emulation)
4/17/04 9:58:01 PM Lowering RTS on COM3
4/17/04 9:58:01 PM Lowering DTR on COM3
4/17/04 9:58:01 PM Carrier Detect = False
4/17/04 9:58:18 PM Data Set Ready = True
4/17/04 9:58:18 PM Carrier Detect = True
4/17/04 9:58:19 PM ATH0Z0
4/17/04 11:00:52 PM Connection from 67.171.224.14 but BBS is down.
4/17/04 11:05:15 PM ATH0Z0
4/17/04 11:05:23 PM ATH0Z0
4/17/04 11:05:31 PM ATH0Z0
4/17/04 11:12:45 PM Connection from 192.168.1.1
4/17/04 11:12:45 PM Raising RTS on COM3
4/17/04 11:12:45 PM Raising DTR on COM3
4/17/04 11:21:35 PM Data Set Ready = False
4/17/04 11:21:35 PM BBS closed connection via DSR, closing Telnet session 192.168.1.1
4/17/04 11:21:35 PM Using COM Port 3
4/17/04 11:21:35 PM Keeping COM Port Open (Hayes Emulation)
4/17/04 11:21:36 PM Lowering RTS on COM3
4/17/04 11:21:36 PM Lowering DTR on COM3
4/17/04 11:21:36 PM Carrier Detect = False
4/17/04 11:21:53 PM Data Set Ready = True
4/17/04 11:21:53 PM Carrier Detect = True
4/17/04 11:21:53 PM ATH0Z0
4/17/04 11:31:44 PM ATH0Z0
4/18/04 12:00:46 AM ATH0Z0
4/18/04 12:00:54 AM ATH0Z0
4/18/04 12:10:39 AM ATH0Z0
4/18/04 12:51:37 AM Connection from 217.238.81.243
4/18/04 12:51:37 AM Raising RTS on COM3
4/18/04 12:51:37 AM Raising DTR on COM3
4/18/04 12:51:51 AM Telnet session with 217.238.81.243 disconnected.
4/18/04 12:51:51 AM MSComm_OnComm(): Wrong protocol or connection state for the requested transaction or request (40006)
4/18/04 12:51:51 AM Using COM Port 3
4/18/04 12:51:51 AM Keeping COM Port Open (Hayes Emulation)
4/18/04 12:51:52 AM Lowering RTS on COM3
4/18/04 12:51:52 AM Lowering DTR on COM3
4/18/04 12:51:52 AM Using COM Port 3
4/18/04 12:51:52 AM Keeping COM Port Open (Hayes Emulation)
4/18/04 12:51:52 AM Lowering RTS on COM3
4/18/04 12:51:52 AM Lowering DTR on COM3
4/18/04 12:51:57 AM Data Set Ready = False
4/18/04 12:51:57 AM Carrier Detect = False
4/18/04 12:52:07 AM Data Set Ready = True
4/18/04 12:52:07 AM Carrier Detect = True
4/18/04 12:52:07 AM ATH0Z0
4/18/04 12:59:16 AM ATH0Z0
4/18/04 1:59:16 AM ATH0Z0
4/18/04 2:59:15 AM ATH0Z0
4/18/04 3:08:02 AM Connection from 217.209.13.175
4/18/04 3:08:02 AM Raising RTS on COM3
4/18/04 3:08:02 AM Raising DTR on COM3
4/18/04 3:08:14 AM RS232 Error: Overrun! Data Lost.
4/18/04 3:25:21 AM Telnet session with 217.209.13.175 disconnected.
|
|
|
|
Post by Leif Bloomquist on Apr 22, 2004 19:15:25 GMT -5
The MSComm_OnComm errors aren't a huge worry - my guess is the telnet client sends a last couple of characters and VB is trying to send them out the COM port even though the port is closed. As long as it recovers, it's a minor annoyance. I see those on my BBS once in a while too.
The Overrun errors are more concerning, but if the system recovers it's again an annoyance rather than a show-stopper. I'm not clear on what the difference is between that and the rx or tx buffers filling (which gives a separate error).
|
|
