In doing some research into this hard to diagnose bug in my and even the trunk version of TWX with Win 7.

I can confirm the error I have recently compiled the trunk version running it locally and all has been fine for over
4 days (albeit I have not opened the script window) but I decided to take the plunge tonight and open the script window
w/o running a script, TWX Promptly dies in about 5 minutes on Win 7 with the infamous 0x0000BABE access error.

I have looked into the Win 7 SDK and they state that they have "improved the generic dialogs" in Vista and Win 7.

I can no longer confirm that this same crash happens on Vista but that gives me some ideas.

I am not too sure how we could link to the old version Comctl32.ocx which I think worked under 2.04 but now is causing
us problems under Vista/Win 7 or 64 bit I am not sure which of the combinations is the guilty party.

Does anyone have any ideas how we could either alias our OpenDialog to a library that we know worked (Comctl32 comes to mind)

I also need some testers to try it out on Vista 32 bit and 64 bit and see if they also experience the crash, It shouldn't take that long 5-10 minutes is all it took for me to crash TWXProxy.
Open from taskbar right click select Scripts menu and then hit the cancel button, from there wait 5-10 minutes and it should crash.

If my suspicions are correct it is because vista/Win 7 have depreciated the old dialog controls and we need to find a replacement.

Hello Maniac,

If you still require a tester, you can e-mail me and give me a rundown to what you want, etc. I'll need the twxproxy as well so if there is a link to download I can grab it or you can attach it. Daala runs Vista 32 Premium, I'm on Vista 32 Basic. We'd be more than happy to help out.

Cheers

I think we're going to have to abstract out the class, and then either translate between old calls
and the new class, or write a new one from scratch.

I believe there are a few alternate classes. Take a look at Lazarus and FPC's dialog routines,
they don't rely on MS's com libraries AFAIK.

And yeh, I reached the same conclusions on the deprecated thing. They've made changes in the
new com controls and TWXproxy hates it.

glad someone is trying to work on this.

I dont have vista or I would try to help ya out.

First off thanks for all the offers to help.

I have uploaded my compiled version of TWX-Proxy that is based on the Trunk version.
Compiled with Delphi 2006 under Win 7 64 bit. (IIRC Delphi does NOT have a 64 bit compiler yet so it must be a 32 bit exe)

I also noticed something from last night's crash.... the dialog box about TWX-Proxy has crashed and what do you want to do
I selected end TWX-Proxy. I forgot about it overnight and this morning I tried to compile the version I uploaded I got error about
not being able to write twxproxy.exe. Turns out there were 2 instances of TWXProxy running all night so the program didn't
gracefully close, using the Windows Error dialog. I had to manually open task manager and kill both instances.

My system might be fubared, I don't remember running more than 1 instance of twx in the last week, so I don't know where
the other instance came from.


It is in the SVN source under branches/MANIAC/Compiled-Versions/TWXProxy-Trunk.rar

If there is more interest I might find time to compile an executable against EP's last commit and any of my commits.

Hopefully EP will grant others write access and we can get a few more eyes on the source code.

Whenever the error occurs, the program gives a crash msg but leaves an instance of the .exe in memory. Maybe it was
from your previous attempt.

I also have experienced, several times, TWX.exe remaining in memory. As many as 3 or 4 (when only 1 is currently running).

Dont think it matters for our problem though. Could be wrong.

Maniac,

Downloaded and ran your attachment. Loaded a script to run, then went to load a second and clicked Cancel. TWXProxy stopped responding after around 10 mins just as you predicted. This happened on both Vista Basic and Premium. All we get is the window popping up saying that TWXProxy has stopped responding and all we can do is stop the application and close.

No issues with XP.

Cheers

Now I don't think this is related to the TOpenDialog because I have replaced the original one with a replacement and still
get same error in the same time frame.

Is anyone else compiling TWXProxy from source?

Please report on what your using .... i.e. Delphi 7, Delphi 2006, Delphi Lite,

Delphi 2006 added a TrayIcon component to the VCL and I am wondering if that could be it... I am compiling with 2006 version.

Elder took out the old TrayIcon component and substituted something else for it but don't know what yet.

I have narrowed down the time required for error to between 6-7 minutes on my system.

Let me see if I can replace the TrayIcon component with something equivalent.


Edit about half an hour later.....

TrayIcon replacement doesn't stop the error msg either....
but with my dialog box replacement I get a memoryleak error of like 8 bytes will investigate it later.

If you comment out the open dialog reference and re-compile. you won't get the crash. It's definitely related to the problem. Maybe your replacement is just as fubar. You can click on the tray icon and mess with stuff all day long and not get the crash.



Trunk, BDS 2006.



Nod. You read my workup on it? lol



Could've told ya that

Any time you open the open file dialog, the timer starts. It actually does vary a little, but not much. I had it at 5m at one point.