Re: EWF Help
- From: "KM" <konstmor@xxxxxxxxxxxxxxxx>
- Date: Tue, 7 Feb 2006 22:01:51 -0800
Ed,
Let me see if I get the picture, if I were to get RAM Reg Mode on G:\.
1. I need to include the El Torito CD Support component to have the
etprep.exe on my F:\ (EWF RAM Mode) image.
2. Boot from F:\
3. Copy image of EWF RAM Reg Mode to G:\
4. Execute etprep -delete
5. Boot from G:\ to run FBA
6. Boot from G:\ again
Nope. Since you run the etprep tool under XP Pro you don't really need the El Torito CD Support component being added.
All you have to do is to make sure no EWF Config partition exists before you first boot (FBA)in to the XPe image with EWF RAM REG
mode set up.
Due to development time constraints, I have built an image according to
http://www.slobodanbrcin.com/xpe/ewf/regramewf.html and put it in F:\.
Ok. You can surely trust that source :-)
It seems to work. But I have noticed one thing that I am not sure if it is
the correct behavior. I created a file in c:\test.txt and issued the command below.
C:\Documents and Settings\Administrator>ewfmgr c: -commitanddisable
Protected Volume Configuration
Type RAM (REG)
State ENABLED
Boot Command DISABLE
Param1 0
Param2 0
Volume ID C1 50 C1 50 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume4" [C:]
Max Levels 1
Clump Size 512
Current Level 1
Memory used for data 0 bytes
Memory used for mapping 0 bytes
After reboot, the file c:\test.txt appears. I was expecting it to be
disappeared since EWF was enabled prior to reboot. If I now create a file
c:\hello.txt, it should then be retained after I reboot.
This is the expected behaviour.
You commited the changes (c:\text.txt is persistent now) and disabled the EWF (any changes will be persistent after that).
So the bigger question is, if the option "-commit" saves the data to the
protected volume, do I need to disable EWF in order to install my software?
Again, don't know anything about your software so it is hard for me to comment on that.
You don't really need to disable EWF to install your software but you obviously want to commit the changes.
You only want to disable the EWF if the software is really heavy and the overlay size grows too much to fit in RAM.
Use case A:
1. Boot with EWF enabled
2. Install my software
3. Issue ewfmgr c: -commit
4. Reboot
Yup. Should work as long as you sfotware is not big (depends on how much RAM you've got on your target machine).
Althgouh I don't se a point why you need to have EWF enabled why installing the software?
Use case B from MSDN
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xeconDesignConsiderationsForInstallingUpdatesOnEWF-ProtectedRun-TimeImage.asp:
1. Boot with EWF enabled
2. Issue ewfmgr c: -commitanddisable
With EWF on SP2 you can just issue "disable" command here.
3. Reboot
4. Install my software
5. Issue ewfmgr c: -enable
6. Reboot
Good.
Is use case A sufficient?
If so, why was use case B published in MSDN?
If not, please explain what's missing in A.
See the explanations above. In short, the RAM (or better, overlay storage) limittations. Remember, you redirect all the disk writes
to overlay with EWF enabled?
--
=========
Regards,
KM
.
- References:
- EWF Help
- From: Ed
- Re: EWF Help
- From: KM
- Re: EWF Help
- From: Ed
- Re: EWF Help
- From: KM
- Re: EWF Help
- From: KM
- Re: EWF Help
- From: Ed
- EWF Help
- Prev by Date: Re: EWF Help
- Next by Date: Re: PnP Manager Problem
- Previous by thread: Re: EWF Help
- Next by thread: Re: EWF Help
- Index(es):
Relevant Pages
|
