Re: FBA Generic command and EWF problem

On Thu, 8 Mar 2007 15:32:49 -0800, Matt Kellner (MSFT) wrote:

Ricky: Is there a particular reason you need a mode of EWF that uses an EWF
partition? RAM_REG mode provides all of the capabilities of RAM mode and
does not require (or configure) a special volume. This may prove more
flexible for your setup, although it does also restrict how you can enable
and disable the overlay (in order to disable it, you must commit it as
well). If you are already running RAM_REG mode, you can expect it to report
that an EWF volume can't be found, since one doesn't exist. You can still
query the protected volume via "ewfmgr c:", though.


There's no particular reason. In fact I setted up RAM mode because I don't
know exactly the limitations in RAM-REG mode.
The solution I found is this: I setted up EWF disabled on startup. Then, on
phase 65521 I run my script. After that, with autologon enabled, I launch
an FBA RunOnce script to enable EWF and restart. This way it works.
I can't tell why, if I enable EWF in a phase after my script and then
reboot it doesn't works.


The command to commit overlay data "live" is "ewfmgr
c: -commitanddisable -live" - you cannot commit "live" and keep the overlay
enabled. You must commit and disable in the same step, and you can then run
another command to reenable the overlay on the next boot - "ewfmgr
c: -enable". Also, this functionality is only supported in RAM and RAM_REG
mode, but not in DISK mode.


I tried to commit and then reboot with no luck. After the reboot the
changes I made via script are not committed.


One more thing: Are you attempting to run fbreseal at phase 12000 and have
your script and the EWF commands run in the same session? I don't believe
that is supported, since fbreseal wants to shutdown or reboot the computer
immediately when it finishes. (I don't recall if FBA stops or continues
running in the background while fbreseal does its thing.)


I have not yet setted up the reseal phase but I tought that phase 12000 is
after the reseal. Am I wrong?

Thanks a lot.

Ricky
.

Relevant Pages

  • Re: EWF/DUA help needed
    ... >> Your script does not reboot the device because it likely fails on the EXECUTE command. ... I suppose it is> mute though if there is a better way to update using ewf. ... >> With EWF command you just commit a registry change to move/replace the JP.exe file on next reboot. ... The file will be replaced each>> reboot until you commit EWF again. ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF/DUA help needed
    ... > Your script does not reboot the device because it likely fails on the EXECUTE command. ... I have changed the script file, ... it may not be good implementation of your script for the purpose of changing running app with EWF on. ... > With EWF command you just commit a registry change to move/replace the JP.exe file on next reboot. ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF RAM Reg mode after copying files to CF card
    ... > fdisk.exe todo the samme partitioning I don't get this error. ... Right now I'm just toying with EWF to se how it works. ... Both -disable and -commitanddisable requre you to do one reboot. ... commit is only a flag that tell to EWF that it should commit image. ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF/DUA help needed
    ... changing running app with EWF on. ... JP.exe file on next reboot. ... > reboot until you commit EWF again. ... EXECUTE command. ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF/DUA help needed
    ... Your script does not reboot the device because it likely fails on the EXECUTE command. ... it may not be good implementation of your script for the purpose of changing running app with EWF on. ... With EWF command you just commit a registry change to move/replace the JP.exe file on next reboot. ...
    (microsoft.public.windowsxp.embedded)
Loading