The .Shell() has the following problem:when run from the runonce key or logon script, some functionality was not installed (as if the complete or some parts of thr user environment wasn't accessible at that time). When i run the script from the desktop, no problem exists!
I needed the functionality of .Shell() to install some InstallShield apps (they're starting another thread, and the normal KiXtart Shell '' installation freezes until i killed the GUI object which works in KiXforms 2.2.0). When i tried to drop the GUI object in KiXforms 2.3.0 RTM, this didn't work anymore. Shawn did some redesign and the GUI object drop does work now (however, the .Shell() still has the problem described above).
Good the hear Jan, I'm "happier" with the way things work now,
internally I mean, having $System=0 drop all GUI objects. One
down and one to go ... will look into. The info about the
"environment" will help narrow my search. Thx.
btw - I am getting some "pressure" (from other Kixforms
user's), to properly implement the .net Process and
ProcessStartInfo object, including redirection of input
and output, eager to implement this too. Stay tunded on
that.
Shawn, i can now use the $Gui=0 way to install InstallShield apps, so there's nu rush for the .Shell() problem anymore (but i would like to see it solved )
(i'm just saying this, off course there's a hurry, there's always a hurry.... 
