I run SWATH 1.94 and TWX 2.04 EP on Windows XP SP 3 with 1 GB RAM. All is fine and stable until I load up M()Mbot (happens with all versions) and try to run the more complex scripts, (such as ugrid, patp etc.), TWX and SWATH freeze. When I open up task manager, to manually shut down, TWX is using 36k or 50% of CPU. Once that is closed ,the 50% usage jumps to SWATH. After that, most of the processes running have to be shut down manually, and restart the computer.
I have reinstalled everything, set up SWATH and TWX using the example from Vid, uninstalled some other memory-hog programs, used msconfig to remove some unnecessary background processes, but I am running out of solutions on how to fix this. Any ideas?

I have ran into this before and 98% of the time you are running 2 scripts at the same time that are for some reason corrupting your TWX database. Delete all files associated to that current game and reconnect do a complete CIM update and then re-test again. You can run the scripts from M()M without loading the bot, might try that as well.

I have not had a corrupt DB in quite sometime but when it does it yep it is a pain this is the one that used to get me all the time (Rintaliation). Hope that helps.

Thanks for your reply, but what about the other 2% of the time? I did as you suggested with deletiing all files. Reconnected and ran a CIM .I logged in to m()mbot and was running only patp. It all froze up about 5 minutes after starting the script.

I suggest you connect to TWX without SWATH and see if the problem persists. I have seen instances where the data coming down is too much for SWATH to handle, and the console appears to freeze, but a connection via MS telnet still shows the data scrolling in.

+EP+

That would be obvious from looking at the process list's CPU usage, wouldn't it?

try using twx proxy 2.04 Beta.. if that fails then maybe scan your hard-drive for bad clusters

It sounds like you're getting hit by the burst macro scroll bug.

For a very small group of people, on some computers, a large amount of text scroll causes the CPU to spike and lock up. If you run anything with a large amount of burst macro scroll (like a buydown or a mover script) w/o any pauses in-between, then you harf and die. It does not matter if it's twxproxy, swath or a telnet.exe burst macro.

There are others that have had this problem. I think mombot had a script, MD's product mover (is that in mombot?) that was written for this particular problem. Find that and run it, compare it against my vacuum. Do you get a lockup using my planet vacuum? Do you get a lockup using MD's product mover? Let me know. Get CK's buydown (or use the mombot buydown, same script) and compare a "best" buy versus a speed buy (bot buy f s, bot buy f b) and see what happens.

As for the solution... the only solution we've had in the past was to get a new computer. Never did find out what it was, but I suspected it was a NIC card or some kind of compression. Heck, it could be the anti-virus/firewall for all I know (you running Norton? Or...?) You wouldn't happen to have an emachine would you?

Thanks everybody, for your suggestions.

Eeeek at the thought of an e-machine, no I do not have one of those, but I am guilty of running Norton Internet Security. I did disable it(if thats truly possible) to run a test, but still got the lockup and the same CPU usage to twx as before. I am considering uninstalling it to see what might happen.
Before I used mombot, I used ck_buydown extensively, both the speed and haggle versions, and did not have any problems.
I have been able to run the mover script in mombot with no issues. I don't think I have seen the planet vacuum script before, but I have used LoneStar's planet stripper successfully.
I have used TWX with two different versions of zoc and was able to replicate the same error.
Yesterday a new thing happened where even Col2 from TWX froze up. That has never happened before.
Bottom line, I am willing to try all kinds of things to make this work, including getting extra memory if anybody thinks that would help, but getting a new computer at this time is not possible.
Thanks guys for all your help.

I have a new beta I should make public. Maybe in a few days, if time allows.

+EP+

*drool*

Had a thought that perhaps your 'lock-ups' might be related to your Video Card. On my desktop, for example, I have to keep the game-text-display area as small as possible (sizing the main swath window down, and/or, sizing the COMMS pane up to about 70% of the screen leaving only about 15 displayable lines), so that I can use swath. In other words; the computer can't cope with the DOS ANSI-text --be it swath or windows-telnet. Try making the game text display area in swath as small as possible. Or if using Telnet overlay another window (ie Explorer, or Notepad), over the majority of the Telnet Window. I know this sounds crazy, but it just might be crazy enough to work

That's the one that fixes the crash on exit, right?

Correct. The crash on exit was due to some issue with the Delphi 6 compiler. That crash disappeared when I ported the source to Turbo Delphi.

There are still a number of routines I'd like to clean up, but the code is good enough for a beta release.

+EP+