On Thu, 5 Apr 2007 06:58:45 -0400, "Gardner, Paul G."
<[EMAIL PROTECTED]> wrote:
>
>CM,
>
>What I've used in the past is an auto-run command list. In the Help index,
>enter this : "auto run when a window opens" without the quotes.
>
>In short, create a new command list. On the Command List tab in the
>configure dialog box, select the setup button. Go to the "Special List" tab
>and ensure that your new command list is the one listed in the "Open" drop
>down.
>
>Then, create a new list item. In the Name edit box put the caption
>"Sygate*" (without the quotes). Either put the call to the autoit script in
>the command list's "Enter Command" edit box, or create a PP script file with
>the AutoIt script file call and call the PP script from the "Enter Command"
>edit box. Usually, I use a win.debug('here') call first until I can get the
>Name right, then swap out the debug call with my real code. You might need
>to play with the caption some.
>
>If you need to use a wait call, then I recommend the script. My experience
>with the auto-run is that the additional check is unnecessary, but your
>machine might be different.
>
>I stay away from HookWindows. Every time I use it, I get in trouble, and I
>don't customize my machine so heavily that PP native abilities don't cover
>what I need.
>
>HTH
>Paul
>
Hi Paul,
Yes, hookwindowsevents is dangerous - I copied my script into this
group once more after faling to get the open window thing working.
This time, PowerPro opened up 453 instances of my script before I
managed to get PowerPro responding so I could move the shortcut out of
hookwindowsevents. Killing those 453 instances one at a time with Task
Manager was painful, and I should have known better - everytime I do
something with that hook group, something like this happens. Still,
that helpfile entry you pointed me to made me realise one thing: that
there are two ways to detect open windows. I had thought that
hookwindows was the only way, so it was the only way I had ever tried
to do stuff like this. Now I have my new group setup for open windows,
I can use that instead. It's less dangerous.
Anyway, I'll have to do some more experimenting with the new window
thing you mentioned. I created a new group for it, went into setup and
made sure that group was the one being used for new windows. I then
added a shortcut like you suggested - 'Sygate*' as the name field, and
then the path to the 'compiled into Windows .exe' AutoIt script.
However, when that Sygate window appeared, the script did not trigger.
It may be because the firewall loads before PowerPro in the Windows
boot sequence (the window usually pops up shortly after booting). I'm
not 100% sure (I have no way of telling), but I think the window
appeared before PowerPro loaded, which would explain why it didn't
work. While the window was still displayed, I opened up PowerPro
config, just to see if that would get PowerPro to see the window. It
didn't, and that's when I copied the shortcut into hookwindowsevent.
And what happened next is what I described above. The script works
fine - if I manually run the .exe when the Sygate window appears, the
script gets rid of it. If I drag a shortcut to the script into the
Windows startup folder, it gets rid of the window as soon as it
appears (it looks like the startup folder entries are run before the
firewall, which is a service). I could leave it at that, but I don't
really want the .exe running all the time, I like to keep my PC lean
and mean with background tasks. I just need to work out if it is
possible to get PowerPro to detect this window with the boot sequence
the way it is.
--
Regards,
CM
