EWF and SP2

  • Thread starter Thread starter Roberto Hofer
  • Start date Start date
R

Roberto Hofer

Hi Ng!

According to microsoft homepage there are a few advancements made to
EWF component, but there are no clues, which advancements there are.

Has anyone installed SP2 preview already and may drop me a line, which
EWF - advancements there are?

(I am dreaming of selective commit and freeing non used RAM, but I am
afraid I am waking up very soon. ;-)

Thands in advance and best regards

Roberto Hofer
 
Yes, wouldn't it be awesome to do this: Commit Filename or Commit
'c:\test\*'
After all, it's only code, Right?
 
Hi Roberto,
According to microsoft homepage there are a few advancements made to
EWF component, but there are no clues, which advancements there are.

Has anyone installed SP2 preview already and may drop me a line, which
EWF - advancements there are?
Click to expand...

1. Forced commitanddisable without the need for reboot.
(I am dreaming of selective commit and freeing non used RAM, but I am
afraid I am waking up very soon. ;-)
Click to expand...

There is EwfMgrCommitFile function but you should read about its limitation in help and how to use it safely.

Regards,
Slobodan
 
According to microsoft homepage there are a few advancements made to
Why not simply download the SP2 TP and install it?
http://www.microsoft.com/downloads/...05-b34f-457c-8013-59eeffd286e5&displaylang=en
1. Forced commitanddisable without the need for reboot.
Click to expand...

2. And, of course, EWF now supports hibernation :-). This is to allow for quicker boot times (hibernate once/resume many times
feature) and controlled state of a run-time image.

3. Protecting Multiple Volumes with RAM Reg Mode.
There is EwfMgrCommitFile function but you should read about its limitation in help and how to use it safely.
Click to expand...

A risky one.. If you change file size or location, you may corrupt underlying volume structure while commit.
Also, it is only RAM based overlay.
My guess was that it was implemented mostly for the purposes of commiting files like pagefile.sys and hiberfil.sys.

Regards,
Konstantin
 
Hi Richard,

You can do this :-)
But it is very dangerous, and you must fulfill some requirements prior to that.

Regards,
Slobodan
 
Richard,

Along the same lines, here's a couple of suggestions I passed along to
MS a while back:

1. Make EWF protection of the XP Embedded OS a painless default. Allow
all updates until Reseal, then automatically lock down whatever is in
place at that time, i.e. the file system contents, not the partition.

2. Eliminate all the distinctions and differences between hard drives,
flash memory, etc. by, for example, providing media virtualization
within EWF.

For what its worth, Roy
 
Hi Ng!

First of all thanks for the answers.

@KM: I do not install it, because I need TD to produce SP1 images and
I do not really trust uninstall procedures. And "I corrupted my
productive system!" isn´t my first choice sentence in front of my CEO.
;-)

@Slobodan: It is now able to commit on file-level? That would be the
solution for about a hundred problems concerning ewf. What exactly are
the limitations of this? When can it be done? Any restrictions?


Best regards

Roberto Hofer
 
Hi Roberto,

One an only restriction is:
File must exist and be allocated up to the max size that you will use on physical medium.
So when you commit it only file data block will be written to disk.
If file grow you will have problems since FS tables are not flushed so you will have data loss. (data will be on disk but file size
will revert to original after the reboot so you won't be able to access your data).

Regards,
Slobodan
 
Roberto,
Hi Ng!

First of all thanks for the answers.

@KM: I do not install it, because I need TD to produce SP1 images and
I do not really trust uninstall procedures. And "I corrupted my
productive system!" isn´t my first choice sentence in front of my CEO. ;-)
Click to expand...

Smart.
I must admit corruptions happen sometime with Microsoft products. The luck of sources and slow support make it worse.
It is not MS fault but rather the way how commercial software work

For me the only good exceptions for many year was Visual Studio (up to 6.0). Great product!
I wish TD/CD/CDM would follow the VS 6.0 simplicity and easiness in use.

KM
 
Back
Top