RAMEWF - failed to enable protection

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

Guest

hi
i am using RAMEWF provided by mr. Sloboda
i have to protect my removable C
also i have a hard disc
i tried all but i am unable to enable the protection at al
i am not getting what is the problem
what should be my disk no
what should be my arcname
i have defined the registry values in extra registry in TD giving each registry'
ComponentVSGUID a new value
is it the correct way
plz. help me out of this
Thanx
Regards
-Rohin
 
Hi Rohini,

You are booting from removable CF, right?

Use:
multi(0)disk(0)rdisk(0)partition(1)
Also this is default by my component.

1. Remove all EWF related components from your image.
2. Add my component.
3. Add component with ewfmgr.exe

What does ewfmgr C: says when you call it?
i have defined the registry values in extra registry in TD giving each registry's ComponentVSGUID a new value.
Click to expand...
Don't do that!


Regards,
Slobodan

PS:
There is a wave of EWF questions these days ;)
 
hello Mr. Slobodan
my problem get solve
i had given disk no. as 1 i changed it to
now my ewf is enabled and working finel
thank u very much for ur RAMEWF wihout which this was not possible

now i have few questions
1. as with RAM overlay the commit command is executed only after shutdow
so if in between there is powerfailure then all changes will be lost
is there ny solution for this

2. If overlay gets full then? Can we have any program for monitoring the overlay and as soon as it gets full it will commit

3.can we have such program (for shutdown) which will automatically commit the overlay at every shutdown

Thanks Once Agai
Regard
-Rohini
 
Please don't put that Mr. thing :)

1. No matter when you call commit operation it will be executed during the graceful shutdown phase. (Not before)
There is no solution for this since this is what stateless operation means. You must use disk overlay for behavior that you
describe. This will be hard to do if you can't mark CF as fixed.

2. Then XPe will report different types of errors because all new write requests will fail. Also you system will be low on memory.
Like I said if you call commit it will do nothing until you shutdown/or restart device.
If you design your system correctly you won't use more than few MB of ram for overlay purposes. Consider redirecting all
temp/log/config files to unprotected partition of HDD in your case.

3. Set ewfmgr c:-commit to run on each boot. This will do the trick.

Regards,
Slobodan
 
3. Set ewfmgr c:-commit to run on each boot. This will do the trick
how to set ewfmgr c: -commit to run on each boot

also -commit command commits overlay up to the level where the command is issued then what is the point giving this at the start(means at boot time

Regard
-Rrohini
 
Rohini,

Are we still talking about RAM EWF?
You have only one level of overlay. (And it is stored in RAM).
Call commit from any point in time from your application, or using run option from registry to call it during each start (depending
on shell).
Commit will do nothing except mark one boolean flag in driver telling driver that during the shutdown should save content of overlay
to disk.

Regards,
Slobodan
 
2. Then XPe will report different types of errors because all new write requests will fail. Also you system will be low on memory.
Like I said if you call commit it will do nothing until you shutdown/or restart device.
If you design your system correctly you won't use more than few MB of ram for overlay purposes. Consider redirecting all
Click to expand...
temp/log/config files to unprotected partition of HDD in your case.

Just to make it more clear:
http://msdn.microsoft.com/embedded/community/tips/xp/ramewf/default.aspx

KM
 
Back
Top