Dr Who:

I know EXACTLY how my bbs works thank you very much. Hell I have the SOURCE CODE SITTING HERE IN FRONT OF ME!

I Know how the telnet functions work. And for anything that is not TWGS telnet works fine.

As far as logging the user into the game though, that is not possible to automate unless there's some kind of file that twgs can read or someting because once a telnet session is initiated, all I/O goes to the user. There's no way to "log the user in and then pass control".

And as far as this "It's not good", What the HELL do you know? Not like you've ever logged into my BBS!? I have a fossil emualtor called NetFoss. It takes fossil enabled programs and reroutes the output to a tcp/ip socket. Does it quite nicely too actually. But that is for DOS based Doors. If you care to read back I'm using a Win32 native BBS software. That means NO FOSSIL DRIVER! Win32 doesn't use fossils! It connects to the com port via a Win32 com handle. Com/IP is DAMB expensive. Netfoss is free and that is one of the reasons I like it!

As far as "Get a better BBS" What the hell are you talking about? And what would you suggest? (And don't you even suggest Wildcat! or anything like it!) I am a very poor person. A BBS software I have to pay for is a BBS software I will not run.

Sounds like you got what you paid for.

Shorty: I cann't AFFORD to BUY BBS Software!

I came here looking for HELP, NOT to get my Butt chewed off for my choices in software. I happen to have put a ***LOT*** of time into getting this BBS up. If you want to make CONSTRUCTIVE COMMENTS, then you're welcome to log on and look around. Make some CONSTRUCTIVE CRITICISIM and I'll take it gracefully. But comments like:

quote:
Sounds like you for what you paid for.


really don't help.

Now I'm sorry for snapping at people. I admit my temper gets the better of me at times. But PLEASE people. Help me out? I REALLY want to get this working.

Thanks!

quote:Originally posted by tripwire

Dr Who:

I know EXACTLY how my bbs works thank you very much. Hell I have the SOURCE CODE SITTING HERE IN FRONT OF ME!

I Know how the telnet functions work. And for anything that is not TWGS telnet works fine.

As far as logging the user into the game though, that is not possible to automate unless there's some kind of file that twgs can read or someting because once a telnet session is initiated, all I/O goes to the user. There's no way to "log the user in and then pass control".

And as far as this "It's not good", What the HELL do you know? Not like you've ever logged into my BBS!? I have a fossil emualtor called NetFoss. It takes fossil enabled programs and reroutes the output to a tcp/ip socket. Does it quite nicely too actually. But that is for DOS based Doors. If you care to read back I'm using a Win32 native BBS software. That means NO FOSSIL DRIVER! Win32 doesn't use fossils! It connects to the com port via a Win32 com handle. Com/IP is DAMB expensive. Netfoss is free and that is one of the reasons I like it!

As far as "Get a better BBS" What the hell are you talking about? And what would you suggest? (And don't you even suggest Wildcat! or anything like it!) I am a very poor person. A BBS software I have to pay for is a BBS software I will not run.




I wasnt being Rude about "Your Board".. My OP was about the BBS Software that your running..
But I'll tell you this now, The TWGS isnt something that likes to be neglected when it comes to system resources.. Sure it pegg'd the processor at 99% but there could have been a few reasons for that, it has a few login bugs..

Running UD, Winamp, and other high memory, high cpu programs isnt something that's going to go well with a TWGS Sever..

You say your low on cash and the TWGS Software/Upgrade isnt cheap. If your users play the door (and you trust them not to use the bug/exploits) then I would stick with that for them to be honest.

The TWGS will accept straight telnet connections or RLogin.. The Telnet setup should be a breeze for you really..
You do have the source there so it shouldnt be a real problem.. As to the outbound telnet connection handing everything straight over to the user.. well.. I find that a bit hard to understand as the BBS will see it (after all it will do the translation and send it to the user).. Not to mention that the user will have to have some type of Esc Sequence to break out of the outbound shell.. So I still stand with
"you should be able to telnet to the TWGS, and use a script to send the Username and Password, then log into the game (or at least the Game Start Prompt)"

It's been a long time since I have been around BBS's.. I dont even remember that much about the BBS Software that I used to use/coop/ectect..

There's no escape commands or anything like that. Now Winamp may have been UP but it was not RUNNING. However, I'll give it a shot. I'll down everything but the minimums and try it again. Although I do wonder why if I telnet to the TWGS outside of the bbs given same conditions, it does not exhibit same behavior.

Watch for a response soon.

Well, I closed down all the extra stuff. Very little running now beyond what Windows 2000 wants to run. Still maxed out the CPU. I was only running:

The BBS Telnet server
The BBS mail system
Norton Antivirus
TWGS
One active BBS connection (local login)

As you can see from http://thedungeon.dnsalias.net/stillmaxed.jpg, not a whole lot of effect :<

I don't get it. Why is it so hard to make this work? Is there a way I could trace what is happening in the TWGS? It only seems to be a bad combo when it's the BBS that connects to the TWGS. If I telnet using the windows telnet program, it's fine. If I connect from my firewall, it's fine. But if I connect from the BBS, no go.

I don't get it. I appreciate any advise that leads twards getting this to work.

TWGS supports RLogin and Telnet connections. They are pretty standard connections. Syncronet, Wildcat, Worldgroup, and several other BBS packages support them and work fine with TWGS. I really wish it worked for you with your BBS software, but don't blame EIS that your BBS software is buggy.

Harley,

Have I EVER stated I blamed EIS? I am just asking EIS for ideas because you guys have access to the source code for TWGS. I know they are pretty standard connections. If I had TWGS's source code I could debug it myself. But I don't, you do. I know it's some kind of incompatabliity, but the question is: WHAT? Twgs works fine with all but my BBS SFW, and my BBS SFW works fine with all but TWGS. So it's obvious the conflict lies between the two. I have never stated otherwise, nor have I ever said "TWGS IS BUGGY! FIX IT!" have I? I am meerly trying to obtain ideas on how to make it work is all. Is that so much to ask?

I don't think it could be anything like packet overloading, but who knows. Maybe I'll do some redirections through a logger and see what that pulls up.

If you have other ideas on things I could check on, I'm all ears. Really that is all I'm asking for. Ideas on what I can try to make it work.

Actually, as far as I know, John is the only person who has access to the TWGS source code. I'm sorry if I seem a bit touchy, has been a lot of discontent lately with TWGS revisions. Things like:
quote:These are the reasons I'm getting exceedingly frustrated with EIS. They have taken an awsome BBS online game and made it completely UN-BBS'able from my perspective.
make me think you blame EIS (and judging by the responses from who and shorty, I'm not the only one). I've never heard of your specific problem with TWGS, the CPU spiking during connection.

I can understand if you are a bit touchy. But I do hope you can understand my point of view. When I was a younger sysop I loved Tradewars. THen EIS bought it. I figured development would continue. I had no idea that John was planning on making a Win32 TCP/IP only version and having it be the only version.

I'm toying around with my firewall to see if I can route a connection through it to watch the packet flow. That is my only guess as to the cause, that somehow the connection to TWGS from EleBBS is generating too many TCP Packets, although I cannot see how.

I will post the results when I'm able to get them. May not be tonight but when I get results I will post.

Ok. This is REALLY strange. On a hunch I D/Led a copy of TWGS onto another machine in this room that is networked. It's a fairly old machine and does not get used for much since it's soo slow. I setup a quickie Game on there, and telnetted in. BEAUTIFUL. Connection about a second later, it responded well. But running on the same one here (which btw is a LOT faster and I don't think that much bogged down) really kills things.

I guess for now I'll leave things alone. Tomorrow I'll configure the syetem properly over there and see how it works. I don't want to go all over the room (rather decent sized room and machines are on oppisite sides) so I guess I'll find some RemoteAdmin software I can install between them to use.

I guess the packet flood idea is a bust if it works over there :>

Anyone familiar with any issues telneting to localhost from within the BBS or anything? I don't know. Maybe this is something that John should look at when he gets a chance. I'm not trying to say "BUG BUG BUG". I'm just saying that if he has access to the code then perhaps he could figure out what's up.

quote:Originally posted by tripwire

Ok. This is REALLY strange. On a hunch I D/Led a copy of TWGS onto another machine in this room that is networked. It's a fairly old machine and does not get used for much since it's soo slow. I setup a quickie Game on there, and telnetted in. BEAUTIFUL. Connection about a second later, it responded well. But running on the same one here (which btw is a LOT faster and I don't think that much bogged down) really kills things.

I guess for now I'll leave things alone. Tomorrow I'll configure the syetem properly over there and see how it works. I don't want to go all over the room (rather decent sized room and machines are on oppisite sides) so I guess I'll find some RemoteAdmin software I can install between them to use.

I guess the packet flood idea is a bust if it works over there :>

Anyone familiar with any issues telneting to localhost from within the BBS or anything? I don't know. Maybe this is something that John should look at when he gets a chance. I'm not trying to say "BUG BUG BUG". I'm just saying that if he has access to the code then perhaps he could figure out what's up.




Generally speaking, I would never telnet to localhost.. I would telnet to the local ip (there is a difference), It will be treated differently in the stack..
ie
if ipconfig shows your internal ip to be 192.168.1.100 then I would use that vs 127.0.0.1..
shrug..

Well really that is what I was doing. Localhost is just a generic term. The IP of this machine is 192.168.0.10 and so I was telnetting to 192.168.0.10:2002

sorry for not using correct terminology. By telnetting to localhost I meant telnetting to the same machine I'm on.

--- Dan

quote:Originally posted by tripwire

Well really that is what I was doing. Localhost is just a generic term. The IP of this machine is 192.168.0.10 and so I was telnetting to 192.168.0.10:2002

sorry for not using correct terminology. By telnetting to localhost I meant telnetting to the same machine I'm on.

--- Dan


Localhost is 127.0.0.1..
Since you tried using your real ip then try using localhost (127.0.0.1) and see if that makes a difference.. The windows stack is something that I dont know much about so I cant say if it will make a difference.. but it is DIFFERENT so you never know

Tried it both ways Dr. Thanks for the tip though. If I had not already tried that it would have been worth a shot.