ewf

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

after fba runs I cannot disable the ewf. I type the command ewfmgr c:
-disable. I recieve acknowledgement *****Disabling EWF, but upon shutdown
and restarting the partition is still write protected. Have you seen this
before. Any resolutions?
 
Hi Eric,

I have seen this very long time, ago. I have tried to catch this problem with debugger and custom filter driver but I was not able
to. Later problem went away on it's own and I had no chance and will to investigate it further.

Can you tell us:
1. What EWF version do you use?
2. What is protected medium type, HDD, CF ,... ?
3. Controller type, IDE, SCSI, ....
4. MS or third party storage drivers?
Any other info that we should be aware.

Best regards,
Slobodan
 
Eric:

Does this happen all the time or just every once in a while?

Just curious... are you building with QFE 823025 (EWF Commands not working
properly)? If not, I would add it to your image. Last year, I would very
rarely see the EWF commit say it was going to commit but after a reboot it
in fact did not. Check out:

http://groups.google.com/[email protected]&rnum=2

HTH... Doug
 
I tried several times to get it to work:
1.reformated destination drive and reloaded image
2.changed settings in enhanced write filter compoent and rebuilt
3.removed the 3 ewf components and rebuilt
Now I am going to roll back to an older version of my image and see if it
works.
 
Which EWF QFE are you using? Which type of overlay, RAM or disk based? If
it is a RAM overlay, is it configured from the registry (RAM REG) or is
configured with an EWF partition?
 
I am not using any gfe. It is a ram overlay. I am not sure how it is
configured. Here is this setting?
 
I ran the qfe and added it to my image and when I tried to disable the
overlay I go the following error.

"Failed setting protected volume configuration with error 87"
what is error 87?
hope this helps.
 
Thanks for the help.
commitanddisable works and allows the ram overlay to get out of readonly mode.
I also found that by removing FBA: Driver signing component that I was able
to use disable. However it might be a coincidence.
Eric
 
Back
Top