Has anyone used Windows 7 and TWX?

For future reference..
Everything runs good..
until

I get this:

Application Error
Exception EAccessViolation in module TWXProxy.exe at 000C3429.
Access Violation at address 00623429 in module 'TWXProxy.exe'.
Read of address 0000BABE.


I have no idea what that means other than I cant run TWX on the latest copy of Windows 7... for long anyway.

actually, I can run TWX and Zoc all day long.

When I fire up mombot is when I get the error and TWX closes.

Is there some kind of XP compatible mode to try?

Well.. seems Im not quite right.. yet.

Looks like ANY script will cause TWX to crash.

I still dont have it pinned down totally.
Seems like I can open TWX and Zoc, then connect, and it will stay connected all day.

If I run a script, of any kind, it will crash soon after (5-10 mins)


@Sing, yep.. it has options to run a specific programs in "Compatibility Mode". You have a choice of almost everything back to Windows 98. I've tried all of them with Twx.exe. I have installed both 32bit and 64bit versions of Win 7. Both do the same thing.

Since the scripts are not recognized as programs, I dont get that option for them.

So I dont know what the problem is.. or whats interfering with scripts. I have even went through windows services and disabled a ton of them 1 by 1 and tested with running a script. No luck yet. Too bad.. I like Win 7 so far. But I cant use an OS that doesnt support TWX fully.. that would be insane.


There is a possible fix, but I am unable to try it. Virtual PC for Win 7 is out now.. but to use it you have to have a CPU that supports the Virtualization Technology (Intel VT or AMD-V). Microsoft says this will cure almost 100% of compatibility problems with programs. Guess we will see what 100% means to Microsoft this go around.

Could it be that the windows is misinterpriting them as malicious programs? I know that my virus program has reported a few scripts that have been sent email to me as a virus.

I have had McAfee's mcShield.exe (need fries and a shake to go with that) go nuts when some of my scripts run and pegs the CPU above 90% (through task manager on mcShield). I have yet to figure out mcShield's issue with my scripts other than they usually are writing data files. Usually end up with a frozen window for all intents.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Any script at all? I bet it's an API call (or mebbe a system call getting harfed by a security thing) that's wigging out. You using the default port 23 for twxproxy? Or have you changed it?



Because they aren't programs. They're all just translated into bytecode and processed by the TWXproxy interpreter. All of the handling is done inside of the interpreter, so that's the app you'd have to mend.



Ah Microsoft, love how they never let up with the crap. Get virtualbox, install XP under it, have fun. I've been using twxproxy and swath under wine on ubuntu w/o a problem for the last few weeks.



Given that anti-virii scan files and any firewall components tend to monitor traffic, anything that generates files, traffic or both could certainly effect them. I've used AVG and Avira w/ TWXproxy w/o any problems.

..

Yep.. as far as I can tell. I tried several. At first I thought it was just mombot. Then I realized even something as simple as 'Keepalive' was doing it also. So I tried citkill.. same thing.

I let it sit for 5 hours (no scripts loaded) and it stays up. I load keepalive.. down in 5-10 with application error.

Although.. something I just thought about.. I was at points using twx'x autologin which loads login.ts script..right?
and it was running well after that.

Maybe something to do with loading a script thru twx after its completely up?

As far as ports.. Ive tried a couple.. not 23 yet though.

Be interesting to see what command(s) are doing that. Any public scripts you've tested? Any logs? Would be interesting to compare the 2.

As for port 23, k. The default port is that, so I was thinking it could be a firewall/security conflict. Prolly not.

Interesting.. I setup Twx to load mombot with 'Autoload'.

It ran all night. No application errors. Even relogged.




Also.. found out that files are being stored in an unusual way compared with what im used to in Win XP.

If I look in my TWX directory on XP - I see the folders - "data", "logs", & "scripts" (plus the few other files)

Using Win 7 - My Twx folder only holds the folder "scripts"
---- "data" & "logs" are being stored in another location.

For example, in Win 7, the path for the main TWX folder is -- Local Disk C: -- Program Files -- TwxProxy

Data & Logs are being stored in -- AppData -- Local -- VirtualStore -- Program Files -- TwxProxy

Sigh. So windows 7 virtualizes app access to split program data from program files. Yuck, what a way to take something simple and make it complex.

I'm so glad to be done w/ windows.

As for mombot, who knows. Without actually digging into the commands and debugging scripts step by step, you're never going to know if it's random or reproducible.

Been there, done that. Have McAfee stop scanning files in your twx directory and that will fix it forever. When you write files, McAfee has to scan them every time.

Traitor - thanks for the info on that. I will give it a shot.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."