Another EWF question

  • Thread starter Thread starter Maarten
  • Start date Start date
M

Maarten

I had this image with working EWF (EWF error 1 thread).
It protected partition 1 with RAM. Then I build a working
image with disk overlay (also on part 1). Then I build an
image with Ram on 1 and disk overlay on partition 2. Only
partition 2 was protected. I then copied the initial
working image (RAM on partition 1) back. It says that hal
dll is missing or corrupt.

From previous posts I assume that this might be due to
the EWF partition that was created. Am I right? Can I
delete that partition as easy as 'etprep /delete'?

Maarten
 
Maarten,

'etprep /delete' should work.
You can use diskpart also for this purpose. (Or to check if you have
successfully deleted it)

Also you can use my solution that will allow you to use RAM EWF configured
trough registry without the need for creation of EWF partition.

http://www.xpefiles.com/a_file.cfm?custid=Components&fileid=ramewf.zip&group
Name=Other

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Maarten,

Check out your boot.ini ARC path. Seems like it does not point to a proper windows directory (or use wrong partition number).

For fixing EWF RAM please follow Slobodan's suggestions.
 
Using etprep does the trick.
I would like to know why I had to delete the partition
manually before the third time, and not before the second
time I made an image. Can someone explain that?

Schedule was:
1 RAM on p1 (ok)
2 Dsk on p1 (ok)
3 RAM on p1 Dsk on p2 (only p2 protected)
4 RAM on p1 (X) (same image as 1)
5 etprep /delete
6 RAM on p1 (ok) (same image as 1)

Check out your boot.ini ARC path. Seems like it does not
Click to expand...
point to a proper windows directory (or use wrong
partition number).
 
Maarten,

Are you sure that you want to know the reason why this happens?

Sometimes during FBA EWF initialization partition is recreated or
initialized, sometimes it is not. Accept that and you should be fine.
If you need to switch from ram EWF to disk or vice versa be sure to delete
EWF partition so you won't have to worry why this happens.

This is not much, but I don't think that anyone bothered to determine why
this happens.

Regards,
Slobodan
 
Back
Top