Re: Prevent command prompt from popping up at system startup

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


On your point 1 below. FBWF does Selective commits immediately. EWF does a
commit on a reboot.

The operating system areas that are constantly read & writen to are
protected by FBWF's RAM overlay. i.e. the registry files. How frequent your
application writes to the flash will also be a factor, but you have some
control.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded
SupplementalToolkit


"Jure" <jure.br@xxxxxxxxx> wrote in message
news:1168424653.456198.67060@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I think i misunderstood the features of FBWF. I thought that with
selective commits, it was possible to commit the overlay *during*
system operation and not on reboots. That way I could protect the CF
from repetitive writes to the same location/file and flush the overlay
e.g. only every hour. I implied that by reading the following:
http://msdn2.microsoft.com/en-us/library/aa940862.aspx ("Selective
Commit is immediate and persists through reboots")

So, if I understand correctly (from the your posts and the
documentation):
1) with Selective commits, you commit only the files you want, but this
occours only at system reboot,
2) with Selective write through you can bypass the overlay and write
directly to the CF.

And the whole idea is to make a list of files which are possibly
changed by the running applications and put it in the FBWF's
write-through list. That way the RAM overlay wouldn't be filled up,
since all writes would be done directly to the CF. And additionally, if
any changes are made to any files not listed in the write-through list
(i.e. they are in the overlay), it could be still possible to commit
them at reboot.

Do I understand correctly?

But if that's how things are (no commit possible during system
operation to free the overlay and writing some most accessed and
modified files directly to the CF), I don't see how the lifetime of the
CF is protected? The only advantage I see is that the files which are
not listed in the write-through list don't get modified, if you don't
perform a commit among two reboots.

Sorry if I completely missed the point of FBWF, but I understood it
that way.

@KM:
EWF live commit may also be an option for you but please keep in mind all
the restrictions
applied to the files to be committed - no
change in location on the disk, no change in size, etc.

I didn't know of those restrictions.

Btw, I was under impression you're using EWF RAM mode, aren't you?

Yes, I'm using RAM Reg mode. But still, if I understand right what's
stated here http://msdn2.microsoft.com/en-us/library/ms940853.aspx, you
can do "ewfmgr c: -commitanddisable -live" which commits the data to
the CF without the need to reboot the system, but then the overlay
remains disabled (and the CF unprotected) from that point in time. Am
I wrong?


Thanks for your patience and help,
Jure



.

Relevant Pages

  • Questions about using EWF on CF
    ... system, make the desired changes, enable the overlay again and reboot ... been saved to an overlay. ... commit the changes - isn't it enough to call commit to apply the ... I don't know how to run the ewfmgr command at system shutdown. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Disabling EWF?
    ... Understood on the 'partition' issue -- I tend to use the wrong terms most ... referring to the RAM overlay... ... WILL be persisted to disk on the next reboot? ... > With commit option pending during the graceful reboot EWF will save all ...
    (microsoft.public.windowsxp.embedded)
  • Re: Prevent command prompt from popping up at system startup
    ... from repetitive writes to the same location/file and flush the overlay ... Commit is immediate and persists through reboots") ... with Selective commits, you commit only the files you want, but this ...
    (microsoft.public.windowsxp.embedded)
  • Re: Disabling EWF?
    ... If you want to disable overlay without committing data on reboot. ... You must use default EWF, ... >> With commit option pending during the graceful reboot EWF will save all ...
    (microsoft.public.windowsxp.embedded)
  • Re: Prevent command prompt from popping up at system startup
    ... you'll need to decide whether you want to do selective file commits or use the write-through list. ... If there are many writes to the file and you want to commit at the end, the using the selective file commit makes sense. ... commit on a reboot. ... The operating system areas that are constantly read & writen to are protected by FBWF's RAM overlay. ...
    (microsoft.public.windowsxp.embedded)