quote:Originally posted by tripwire

Orion_Blaster: If those are worthwhile, how about reading my posts more clearly?

quote:
EleBBS/W32 is my software. I have native incoming telnet support, but the outbound telnet support doesn't work right. I tried it.


Using ELE's telnet menu option makes my 1.33GHz machine behave like a 286. It LITTLERALLY takes around 60+ seconds to connect, takes 10+ seconds to echo a single character, and slows things down to much that a voice relay would go faster. And thats the whole machine. EVERYTHING slows down.

And the door, although a nice idea, is not going to work because it's a DOS door. So while it would be fine for DIALUP, anyone that telnet'ed to the bbs would have to go through a double wrapper. Win32 program calls Win32 Fossil emulator. Win32 Fossil emulator calls DOS door, Dos door calls Dos packet driver (which could cause problems under 2k), and then connects to localhost using DOS packet driver. Does not sound like a viable option to me.




I did read it, I figured that you must not have Telenet set up correctly for the BBS. It could be a configuration issue.

There exists other reasons why Telenet is slow, you could have a lot of spyware and adware on your system hogging your Internet bandwidth or slowing down part of the system. Windows 2000 is still prone to many Internet Worms that hijack Internet services, did you apply SP4 and the RPC patch? If so did you use Windows Update or download the updates from a different machine and installed them from the hard drive? If Windows Update was used, chances are you might have got one of the worms. It can fool NAV by patching NAV and other Antivirus programs into not seeing it. I've seen the same results you have had on other Windows 2000 machines that had the worm. Internet usage is slowed down or buggy. Of course they won't effect Dial-up as they do not hijack modem connections.

If your BBS software is so buggy, and it gives you nothing but trouble, may I suggest Synchronet? http://www.synchro.net/ Download it and install it to run on another port than EleBBS does, and then Rlogin into the TWGS server and see if it is slow as well. If it is slow, then consider something on your system is slowing it down. If it is fast, then EleBBS is messed up somewhere. You don't have to switch to Synchronet, but you can test things out with it to try and see where the problem really is. It is free to download and use.

BTW it is Blastar not Blaster, Mother and Father Blastar would not like me going by Orion Blaster.

Also we are trying to help you, but you are not giving us enough information to see what the problem exactly is, so most of us have to guess. Most modern BBSes have excellent support for Telnet and RLogin sessions built in. Not sure why yours is different, take it up with the mailing list see if anyone else has the same problems that you do.

Cute Orion_Blastar, Cute :>

I alredy determined that it's someting funny with the combination of EleBBS and TWGS on that machine because ANY other combination (including TWGS on an older slower macine elsewere in the room and going across the network from EleBBS) works fine.

I have determined that for the moment the best strategy is likely to just leave the TWGS on the alternate machine. Then I can just telnet to there from EleBBS. I am still not sure why this one combination results in a 99% cpu usage for TWGS and no other situations do, but at least for the moment I have a semi-feasable alternative.

I have the same problem running Mozilla and Seti@Home, if at the same time it seems to give me high CPU cycles for either one. Removing Seti@Home seems to have fixed it.

I suspect there is something the programs use in common that is conflicting?

I had to put in those other things because I do not really know your system, what is installed on it, what resources the programs use, etc. TWGS uses a lot of RAM, maybe your BBS does as well when it uses a Telnet connection? We got reports of people running TWGS with less than 128M and having sluggish issues on the forums here before. Without TWGS in memory you will have more resources free.

I have recently found that NAV 2004 is causing all kinds of lockups on my machine. I am ready to go to AVG or some other AV software. Shame on me for buying three copies of it for my machines. It just goes to show how some software conflicts with others. Windows being Windows I guess?

Could be. I'm actually getting ready to just format the drive and reinstall everytihing before too long. But before I do that I gotta back up a *LOT* of stuff I don't want to loose (like the BBS!). So I don't expect the format for a couple of months yet given my limied time :<

After that I'll try TWGS on the same box again. Who knows. Maybe it's just some kind of conflict.

One suggestion before you trash everything and reload, depending on your OS, I dont recall seing it posted in any of your posts, here is a link for some free utilities that may help you track down exactly what program, file, dll, etc. is causing your problem.
http://www.sysinternals.com/index.shtml
You might want to check out process explorer especially if your running NT/2k/XP, it does work on win 95/98 also, there are some other things there that can let you look at exactly whats going on real time and you might be able to track it down that way. Hope it helps.

New Spyware threat is out there and the current Spyware removal tools and Antivirus removal tools cannot remove it yet.

Look2Me msg118.dll look for it in your System Root directory. C:\WINDOWS\SYSTEM32\ for XP, C:\WINNT\SYSTEM32\ for 2000/NT, C:\WINDOWS\SYSTEM\ for 9X/ME. Also msguard.dll is another variation of it. It hijacks network connections and can cause programs to eat up CPU cycles by piggybacking on them. It infects Explorer, so the only way to remove it is to boot to DOS and delete the file.

For my Windows XP Pro system I had to boot using the BartPE CDR boot disk:
http://www.nu2.nu/pebuilder/

Why? Because the hard drive is formatted as NTFS and the XP Floppy DOS Boot creation is really a Windows ME boot disk that cannot read NTFS formats. The BartPE is based on Windows XP and can read, write, and format NTFS partitions.

I was using the demo of TWGS .56 and it would lock up my system, 99% CPU cycles and report bug crashes to Microsoft when I stopped the game server. I thought maybe it was a .56 bug so I went back to .55 but had the same problem. After removing the Look2Me Spyware I can run the server normally and stop it without having a crash report.

So in this case it was not TWGS crashing or eating CPU cycles, it was the Spyware program piggybacking on TWGS, Explorer and other Internet ready apps to monitor Internet useage and phone home the results. I suspect other Spyware/Adware programs cause similar problems. This Spyware app also installed other Spyware, Trojans, and other junk on my system which NAV 2004, Spybot, The Cleaner removed.

Tripwire, check for the msg116.dll, msg117.dll, msg118.dll, msguard.dll files on your hard drive. If they exist, you got the Look2Me Spyware software. This thing is hard to remove and if not removed properly it will come back. Also known as ZestySpy, NetSpy, and others. http://computercops.biz/postt18216.html

well if Spyware WAS the issue it's dead now. This is a cleanly formatted system now. Still installing non-essential items (AFTER installing NAV 2003 with all the latest updates).

After the re-format and re-install do you still have the same problems? Please let us know. Thanks.

Have not had time/ability to try yet. Having even more issues. I was suspecting MBD failure but when I contacted Asus they said the first thing I should do is shove a bigger P/S in the system. I'm running a 300 and they said they recomend a minimum of 400 for an AMD w/ 6 devices hooked into the P/S (2 HDDs, 1 FDD, 2 CD-RWs [CD-RW, DVD+RW], Zip-250 Atapi). So I'm ordering in a 500 Watt P/S. Once it gets here I'll shove it in, replacing the 300 watt I've got now. Then if things calm down (Which I'm hoping they will) I'll run some offical tests and let you know. I'm gona do some side testing but won't be completely surprised if the circumstances return.

Well, I did a quick test using the 300 Watt P/S since the 500 ain't arrived yet, and the results are nearly identical. TWGS still uses 99% of the cpu. Only real difference is that 2k handled it a lot better. The system was not as sluggish as before. But still unusable results. Hopefully the 500W P/S fixes it.

I seriously doubt that the 500 Watt Power Supply can make a difference in how programs run. I have run AMD systems with 300 Watts and not had that problem. I have a 300 Watt AMD Athlon XP system using XP Pro and can run the demo of TWGS on it without having 99% CPU cycles. I had a discussion with a friend of mine who runs a Linux server using the same motherboard and CPU as me and he says he can get away with 200 Watts. Well try the 500 Watt power supply and see what happens. If it does not work, I hope you can get your money back.

The only thing that caused the Athlon motherboard problems was an incompatable memory chip that caused serious blue screen problems in XP until I replaced the memory chip with a compatable one. Then the blue screens went away.

If you have more than one machine, there may be a solution for you. Use AnalogX's PortMapper program to map a port from the other machine to the machine that has the IP on the Internet. You can find their Networking programs here:
http://www.analogx.com/contents/download/network.htm

That way BBS users can play the Game by Telnetting to the other machine, and the other machine can have 2002 or whatever TWGS is running at mapped to your BBS machine so it is seen as being on that machine to the outside Internet and players can Telnet to your BBS machine at port 2002 or whatever and play TWGS. BTW, IIRC PortMapper is a freeware app so it should fit your budget.

Good luck.

Why don't you just go to using Synchronet? That software is still supported and still being updated and it's FREE.

Tripwire,
I am very interested in how your problem turns out. I admit that I haven't run a BBS in 15 or so years, I did at one time, and I did run TradeWars games.

QUESTION - Is it possible that the reason the system resources pegs out is that TWGS is listening to port 23 (standard Telnet port) and thus listening to ALL your telnet traffic, waiting for someone to contact it? I have read this whole thread, and I noticed that when you set up Trade Wars on a slower machine across the room, it seemed to work fine. I was wondering if the BBS software sending out telnet sessions was slamming into the TWGS listening port?

If the above sounds whacked out, excuse my ignorance. It's been a long time for me, but I want to help if I can.

Paladyne