Probably impossible - control actions of .exe

jenn5175

Freshman
Joined
Apr 4, 2002
Messages
35
I am not sure if this is possible but I am guessing it is not. I figured it couldn't hurt to ask since a lot of you have creative ways around a problem.

Background:
One of the brands at an autoshow took a premade director interactive program (design your own car, see specs, etc) for use by an individual and are attempting to use it as a display on a large screen that participants can interact with using only a mouse to click through the pages.

My Task:
I was given the director exe and told I had to disable the "Exit" button in it since it was to be running on a plasma display and they didn't want people to shut it down and walk away. Since I did not have access to the code, the best I could come up with was to write a small vb6 app which runs the director exe and watches for when it exits and restarts it. The client was very happy with this solution. Now they have come back and said it is doing 2 more things they would like me to "fix" (keep in mind I cannot actually get into the director code)

(1) There are internet links inside the app. However, there is no live internet. So when someone clicks on a link, it pops up and says "you must first sign onto the internet" etc. They want this disabled.

(2) There is a spot where you can save a PDF to your computer and it pops up the whole "Save As" dialog and the desktop. This gives them access to the desktop which is unacceptable (my app runs the exe at full screen so they cannot see the desktop).

Is there a way for my VB6 app to disable any popups? My app simply runs a shell cmd to run the exe, so its not actually running the exe inside of a VB form. Can anyone think of a way around these things?

I am familiar with VB.NET and am not opposed to converting this small app to it if there is maybe a trick specific to it. Is there any way to halt any new windows spawned by the director exe? Let me know if you have ANY ideas, no matter how far-fetched they seem.

Jenn
 
Thanks - this is definatly a step in the right direction. However, is there an event fired when a new window is opened? I mean, there has to be but I can't find one on Microsoft's site. If my app is alerted that the Window is created it can destroy it. But otherwise I will have add more loops just waiting for all possible Windows to be created, right? Or am I not thinking about that correctly?

Jenn
 
Back
Top