Re: Prevent command prompt from popping up at system startup

My guess is...

The actual commit is going to be done on graceful shutdown/reboot.
The storage is still protected (calls are redirected to the EWF overlay). So if sudden power loss occurs, it won't break the system.

And all the changes user makes are persistent. Sometime it may be required by a system specs.

However, there is still a risk factor in such approach. If RAM overlay used, user changes, if not controlled, may easy and quickly
increase the overlay size before the current session ends (reboot). The overlay will grow unlimitedly until it eats up all the
memory. Only cure (without being able to limit EWF overlay size) is to control what users can do at run time - lock the OS, shell,
turn off all possible OS, IE and app caches, disable background disk processes like defragmentator, etc.

--
=========
Regards,
KM


"steves" <steves_garbage@xxxxxxxxxxxxx> wrote in message news:1168039512.807761.192360@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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




.

Relevant Pages

  • Re: EWFMgrCommit question
    ... With EWF RAM Reg the overlay is going to be committed on graceful shutdown. ... safely commit the overlay and reboot the device. ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF Commit Question: What if file is corrupted in the overlay?
    ... This will commit whatever is in the overlay at the time the ... EWF does not do any validation on the data in the overlay, ... corrupt via another method. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Ewf live command
    ... This option do not exist as prevention since you would save working system in unknown state and compromise very thing that EWF ... > I was wondering if there was a way to commit changes to the hard disk ... > used when using the RAM based overlay. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Prevent command prompt from popping up at system startup
    ... If you commit EWF at every boot, you are committing - nothing really. ... I couldn't quite understand how launching a console app problem is ...
    (microsoft.public.windowsxp.embedded)
  • Re: Corrupted image after EWF commit was interrupted
    ... I pressed the restart button to restart and ... fortunately the image is still ok after commit and reboot... ... (such as during the boot process, or ESPECIALLY while an EWF overlay is ...
    (microsoft.public.windowsxp.embedded)
Loading