> New exe should not produce "running vista" any more.
It isn't producing debug so I think I have the right one :) I'll use
this one for a while and try and find some consistencies.
> Does this happen more consistently or less often with the debug version of
> exe you are currently using (not the one I just uploaded, although it should
> work the same).
It seems to go thru spells. I think I went a couple weeks with it
working fine, now recently it's been doing it more.
> I guess we also changed to not running in compatibility mode, so that could
> be an issue too. Did you always run in compatibility mode before?
Yes, in the hopes it helped with the lockups/keyboard macro's it's been
in compatibility since I did the initial install but I think it was
wishful thinking. My gut is telling me there was no effect (I do have
UAC off btw - but I think there's some security stuff I can't turn off
in windows 7, how windows and processes are isolated I think). I'll run
it as native for a while and monitor.
> What is shown by the putting *info expr(win.exename("rawactive"))
> on a button (pls ensure using rawactive) when PowerPro freezes?
I have a bar that has all the info
*Info .exe name: expr (win.exename("rawactive"))
of all the different class, exepath etc. I've set it to almost
transparent and mousethru so it'll always be displayed but not in the
way. I'll let you know what's on it when it locks up again. When I
change focus on windows, it does take ~1 second to reflect the change so
hopefully it'll be showing the right info.
Stay tuned :)
David Troesch | Atlanta, GA | ICQ# 2333123
"What distinguishes us one from another is our dreams, and what we do to
make them come about."
Funstuff: Underachievement: The tallest blade of grass is the first to
be cut by the lawnmower. www.despair.com
