|
Post by Dr. Video / ADDiXiON BBS on Mar 6, 2005 5:01:26 GMT -5
Jim, if you havent already, please check your email. TCPSER seems to be getting its input/output streams confused when a second connection is made while someone is online. I sent you the details and how to perform a test to duplicate the situation. I can't go back online until this is resolved. Maybe its something specific to my situation, but I am not sure.
Thanks! Jeff
|
|
|
Post by Dr. Video / ADDiXiON BBS on Mar 6, 2005 19:59:54 GMT -5
Looks like your patch is working. Addixion is back online, now at 38,400 bps via Turbo232.
|
|
Mo
Newbie
Posts: 30
|
Post by Mo on Mar 6, 2005 21:13:30 GMT -5
|
|
|
Post by Jim Brain on Mar 6, 2005 23:12:57 GMT -5
I'll make up a RC9 for folks to dload.
Moise, how did you get 576 working with Centipede? I thought it maxed at 384?
Jim
|
|
|
Post by Dr. Video / ADDiXiON BBS on Mar 6, 2005 23:41:48 GMT -5
The Centipede manual says "With the Turbo232 only, you may select 57600, 115200, and 230400. These are the local (DTE) baud rates. Your actual modem rate (DCE) will generally be lower".
Well, in this case, if we have a cable modem, couldn't we be approaching 115-230.4k?
I have yet to try 57.6 myself.
|
|
Mo
Newbie
Posts: 30
|
Post by Mo on Mar 9, 2005 17:13:33 GMT -5
Well, I tried running at 57600. Started having some strange problems with it after just a couple logins. Would try to login via telnet, and get nothing except a string of garbage characters transmitted (Centipede would display fine on the BBS end). Then, disconnect, and reconnect, and login went fine. Let it run overnight, and then when I checked it the next day, nothing except garbage characters were getting transmitted no matter how many time I disconencted and reconnected. Again, Centipede was showing proper characters on the BBS side, and was receiving data properly. I was actually logging in, but was typing blindly. I tried to reset tcpser, no luck. Tried even rebooting the PC hosing tcpser, no luck. I rebooted Centipede, and everything started working again. So, It looks like it was Centipede that had the issue. Since then, I have configured Centipede, the PC hosting tcpser, and launch tcpser at 38400. Been running for a couple days now and the issues seem to have gone away. Still much faster than running it at 2400 bps. -Moise telnet://lostcavernsbbs.dyndns.org:6001telnet://lostcavernsbbs.dyndns.org:6002
|
|
|
Post by Dr. Video / ADDiXiON BBS on Mar 10, 2005 11:35:32 GMT -5
Yeah my BBS has been up at 38400 for 3 days now, and never had the garbage problem.
Mo, did you have any kind of tracing/logging going on? It is possible that TCPSER could not handle that. When I had full tracing and logging turned on at 38400, I had tons of dropped characters.
|
|
Mo
Newbie
Posts: 30
|
Post by Mo on Mar 12, 2005 7:38:00 GMT -5
I haven't enabled the logging, although I should! I'll do it right away, and let you know what I find. So far, been running for a few days with no issues at 38400. -Mo
|
|
|
Post by Jim Brain on Mar 13, 2005 17:34:54 GMT -5
Mo:
I would tend to agree that Centipede was having trouble. At 57600, that's a lot of IRQs every sec.
Dr. Video:
Logging at level 1,2,3 or so should be fine for production use. I'd not recommend DEBUG_X logging level for prod, nor would I recommend tracing. However, they should not cause dropped chars, as there is OS buffering.
Jim
|
|