Re: Prevent command prompt from popping up at system startup
- From: "steves" <steves_garbage@xxxxxxxxxxxxx>
- Date: 5 Jan 2007 15:25:15 -0800
I'm curious - Why do you want to do this?
If you commit EWF at every boot, you are committing - nothing really.
The system has just been restarted, and no-one has had time to make any
changes, so.... what are you committing?
Maybe you really don't need the EWF if you are committing it all the
time anyhow?
SteveS
StevesATeyeDASHimagingDOTcom
Jure wrote:
Thanks for your help. I'll do what you suggested.
Jure
KM wrote:
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
.
- Follow-Ups:
- References:
- Prevent command prompt from popping up at system startup
- From: Jure
- Re: Prevent command prompt from popping up at system startup
- From: KM
- Re: Prevent command prompt from popping up at system startup
- From: Jure
- Re: Prevent command prompt from popping up at system startup
- From: KM
- Re: Prevent command prompt from popping up at system startup
- From: Jure
- Prevent command prompt from popping up at system startup
- Prev by Date: Re: QFE update confusion
- Next by Date: Re: Prevent command prompt from popping up at system startup
- 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
|