System Crash when running two instances of SysTool

[t_ski]

I found a bug in the latest release of SysTool. I had SysTool running today when I accidentally started it again. When I tried to close out the second instance, I got a BSOD and the system rebooted.

Can anyone confirm this?

[Alec§taar]

Maybe it's not meant to run 2 instances of itself?

(This is pretty fairly simple for W1zz to correct imo... couple ways, actually).

First:

There are TONS of prebuilt functions he can get online that stall 2 instances of his app from running, & they use Win32 API calls like "FindWindow" (iirc, that's 'limited' to Win9x though, but there are NT/2000/XP/Server 2003 analogs)...

Second:

If needed? He could just write a small file to disk & use an If FileExists type call in his code that checks for said file on disk (in VB, which I doubt W1zz uses, the DIR function iirc, does this or can)...

So, if his temp file indicator is there on disk? Do NOT launch again... if not there? Launch the program!

(However, "method #2" up there? That might 'bugger out' though, if the program crashes & never gets to delete said file from disk though!).

* Anyhow/anyways - It happens... good catch by the way, if this is a 'bug'...

APK

[t_ski]

Were you able to duplicate the crash?

[Alec§taar]

Were you able to duplicate the crash?

Unfortunately no, I do not use that tool (but, I used to use W1zz's stuff in the past for ATI cards I had & liked ATI Tool a GREAT deal)... but, I have had to detect dual instances of apps before & just wanted to 'sound off' ideas on how he can 'fix' it, fairly easily too!

(Just by preventing/detecting dual instances of his app running... there's a variety of ways to do that & he has the skills/know-how, even though I have seen folks quote of him saying "I am not a programmer"... well, imo? He is... pretty good one too!)

APK