PlanetSquires Forums

Support Forums => Other Software and Code => Topic started by: James Padgett on May 11, 2010, 01:00:00 PM

Title: Process runs with no dialog window
Post by: James Padgett on May 11, 2010, 01:00:00 PM
I am using an eventtrigger to run a splash screen with certain events occur however the process runs ie. it shows up as a running process, but the dialog window never becomes visible.
It works fine if I double click it, or run it from a command line...  but not if it gets triggered by the eventtrigger.
Title: Re: Process runs with no dialog window
Post by: Paul Squires on May 11, 2010, 01:42:20 PM
?

So, your splash screen is a separate exe than your application?

You are invoking that exe from an "eventtrigger"? Could you explain what type of event you're talking about here.

Title: Re: Process runs with no dialog window
Post by: James Padgett on May 11, 2010, 01:55:33 PM
I have a single .exe that is a single dialog with a picture control and a label.
If I double click on the exe.. the dialog opens as expected.
If I run it from a command prompt it works the same...
***  I don't think there is anything wrong with the app or firefly :-)  ****

I have an eventtrigger that eventually will trigger the .exe above to run on a PC if there is a disk error, but for testing I simply have an event trigger to  actuate if there is an information event posted in the Application log as follows:

eventtriggers /create /tr "MSI INSTALLER"  /l "Application" /Eid 1042 /d "msi test" /tk "c:\temp\esplash.exe"

note: the task scheduler must be running for the eventtrigger to work...

The trigger works and the esplash.exe runs, but the dialog doesn't appear... only the process esplash.exe shows it is running the task manager.
Title: Re: Process runs with no dialog window
Post by: James Padgett on May 11, 2010, 03:00:07 PM
Problem resolved..  I had to specify a /ru and /rp when creating the eventtrigger...
Title: Re: Process runs with no dialog window
Post by: Roger Garstang on May 12, 2010, 12:38:39 PM
Yeah, if it uses Task Scheduler it can run two different ways. One is in the current Desktop and the other is behind the scenes almost as a service with no desktop interaction...I think it is even running under the Service/System account, so would have limited network access and such too.