Re: Prevent command prompt from popping up at system startup
- From: "KM" <konstmor@xxxxxxxxxxxxxxxxx>
- Date: Fri, 5 Jan 2007 00:45:25 -0800
Jure,
Honestly, I couldn't quite understand how launching a console app problem is
really connected to EWF. What I suggested earlier was creating a simple app
that calls into the EWF API [commit]. Obviously, this app wouldn't care
about any other console app(s) you might need to launch at run time but it
would do the commit function you need.
Any console app you can launch with ShellExecute[Ex] call providing the
SW_HIDE parametr as the nShowCmd argument (please refer to MSDN for more
info). It should hide the app implicit console window on start (won't work
for extra console windows that may be created by the app explicetely by
colling console alloc API).
KM
Thanks for your answer.
Is this the only approach? I'm asking that because maybe I'll have to
modify the command to execute and at that time I'll not be able to
recompile my app. Ok, it might be possible to supply the arguments in
e.g. a text file, but is there maybe an easier way to achieve that?
Someday I'll maybe have to call another console app in the same way,
and it isn't very practical to write a custom app for every such need.
Thanks
KM wrote:
Jure,
ewfmgr is a console app and that explains why you are seeing the blank
window blinking quickly at the boot.
The best way to fix this would probably be writing your own simple and
little app that will call in to the EWF API to commit the
overlay. You can make your app small and non-console so that it starts
very fast and no GUI seen.
--
=========
Regards,
KM
.
- Follow-Ups:
- References:
- Prev by Date: Tried to Use X13-3877 Update But Have Error
- Next by Date: Re: Creating policies and putting them into target image
- Previous by thread: Re: Prevent command prompt from popping up at system startup
- Next by thread: Re: Prevent command prompt from popping up at system startup
- Index(es):
Relevant Pages
|