Recent changes to bugs

Access violations due to spurrious WM_USER events

Andrew Tonner — Mon, 21 Nov 2011 06:05:34 -0000

I'm getting an access violation around every 15 minutes while a script is running. If that wasn't bad enough, after I click OK twxproxy.exe stays running and I have to go kill the process myself.

I'm running Windows 7 Ultimate 64-bit on a Core i7 2600K.

Quick hack to work around it:

The access violation is coming from TWXProxy.dpr:192, where we're trying to dereference the window message's wParam as a TNotificationEvent pointer. I know very little about low level Windows programming, but Goggle found me some suggestions that Delphi might be using a bunch of WM_USER range messages internally (http://www.delphipages.com/forum/showthread.php?t=49257), so under the assumption that it was trying to (mis)interpret one of those, I tried bumping the message type up to WM_USER+105 (the receiving code at TWXProxy.dpr line 189 and the sending code at Core.pas line 227) and the problem went away.

Is this the wrong purpose to be using WM_USER-0x7fff message types for?
"These values cannot be used to define messages that are meaningful throughout an application, because some predefined window classes already define values in this range. For example, predefined control classes such as BUTTON, EDIT, LISTBOX, and COMBOBOX may use these values. "
- http://msdn.microsoft.com/en-us/library/windows/desktop/ms644931\(v=vs.85).aspx

After running into access violations ~ every 15 minutes, I grabbed the v211 source snapshot, and with some wrangling, got it building in Turbo Delphi Lite and then running in the debugger.

Under the assumption that the message might have come from something other than the TWXProxy code, I did a little Googling:

problems with versions

Anonymous — Tue, 15 Nov 2005 05:00:13 -0000

i was told to ask you for help with this, in having trouble
with scripts failing with incorrect version messages...

i was told u have a converter i could try, or any other
help would be appreciated

..mostly the trouble is with supg, and wildstar's scripts

Script Windows is not working properly

Michael Hagin — Sat, 09 Apr 2005 20:48:11 -0000

As outlined by spaazster on twxproxy.com:

script windows AREN'T working like in 1.09b I wish they
were. I liked those.

Logging Feature options

Michael Hagin — Sat, 09 Apr 2005 20:47:15 -0000

As outlined by Tweety on twxproxy.com:

yes i have something.

your logging feature. maybe grey out the two options if
you don't have log selected database checked. cause it
doesn't seem to log if you just check log as binary
without the top most one checked.

Missing Sector variables in v2.03

Michael Hagin — Mon, 04 Apr 2005 04:55:11 -0000

There is a issue with the setSectorParameter, or
getSectorParameter, that is causing the last sector
variable to disappear completely.

As discribed by Elder Propphet, set a couple of sector
variables with setSectorParameter. Move around the
universe for a few sectors. And then use the
getSectorParameter to see the previously set sector
variables. What you will find is, the last variable that
was set is now missing.

The get/setSectorParameter is not storing values correctly

Michael Hagin — Mon, 04 Apr 2005 04:28:33 -0000

There is a issue with the setSectorParameter storing the
values correctly. And Then the getSectorValue is also
retrieving the values incorrectly

script problem

Anonymous — Sat, 02 Apr 2005 09:23:47 -0000

World ssm crashes the program everytime i try to load
it. Deosn't matter if it is used with zoc or swath.
Command [TL=00:00:00]:[xxxx] (?=Help)? :

Loading and compiling script: C:\Games\Twxproxy
2.03\scripts\2_WorldSSM.ts

Command [TL=00:00:00]:[xxxx] (?=Help)? :
Script terminated: C:\Games\Twxproxy
2.03\scripts\2_WorldSSM.ts

[TELNET] INFO: DISCONNECTED

***
*** DISCONNECT
*** time 01:58:30
doesn't matter if i try the .ts or .cts

setEventTrigger is not working properly.

Michael Hagin — Fri, 01 Apr 2005 08:13:42 -0000

In the current TWX Proxy script API documentation. It
states the following:

setEventTrigger

Purpose: Creates a trigger that will activate on a certain
program event.

Syntax: setEventTrigger {name} {label} {event}
[{parameter}]

{name}: The name of the trigger to create. This name is
used for later references to the trigger.

{label}: A label within the script to jump to when the
trigger is activated.

{event}: The name of the program event to attach the
trigger to (see below).

[{parameter}]: Some (but not all) program events require
parameters. These are specified here.

Notes: Triggers mark the way in which TWX Scripts
interact with their environment (Trade Wars).

The event trigger will automatically jump to a label within
the script and start executing as soon as a program
event occurs matching its specification.

Currently, TWX Proxy supports the following program
events and their parameters:

SCRIPT LOADED : Activates when a script is loaded.
Its parameter is the name of the script loaded.

SCRIPT STOPPED : Activates when a script is
terminated. Its parameter is the name of the script
terminated.

CONNECTION ACCEPTED : Activates when TWX Proxy
connects to the remote server (no parameters).

CONNECTION LOST : Activates when TWX Proxy
disconnects from the remote server (no parameters).

CLIENT CONNECTED : Activates when a telnet client
connects to TWX Proxy (no parameters).

CLIENT DISCONNECTED : Activates when a telnet
client disconnects from TWX Proxy (no parameters).

TIME HIT : Activates when the click hits a certain time.
Its parameter is the specified time in system format.

Note that no triggers will activate unless the script has
been paused with a "pause", "waitFor" or "waitOn"
command.

After working on a script that requires the use of the
SCRIPT LOADED and SCRIPT STOPPED events. I
have found that the setEvenTrigger does not work as it
should. At least not the way it should for the SCRIPT
LOADED and SCRIPT STOPPED events.

If you include the script name as the parameter for either
of the two events. To show that you are looking for that
specific script to be loaded, or stopped. TWX Proxy
does not recognize that the script was loaded, or even
stopped. It just continues to set there waiting for the
event to transpire.

Using the above two events without the script name.
Produces the desired results, but has the draw back
that any script that is loaded, or stopped, to activate the
event. Which could have disastorous results with the
script.

NOTE: This bug is present in v2.00, v2.02 and v2.03
official releases, including the v2.03 build 13.

We can easily change the documentation to reflect the
current behavior, and proper use, of the events
mentioned above. Or we can fix the events, so that they
reflect what the docs state.

I have no idea if the TIME HIT event is also effected by
this bug. Will have to do some testing to find out.

Precision is not working properly

Michael Hagin — Tue, 22 Mar 2005 10:56:30 -0000

This was reported on the TWX Proxy support forums.

The SETPRECISION 0 is not working as intended.
Check to see if this was fixed in final build of v2.03. If
this was not fixed, then we need to fix it.