etprep failing

  • Thread starter Thread starter Kevin
  • Start date Start date
K

Kevin

Im running RAM overlay with CF and get the message "Failed to get
EwfSwapSpecifiedDriveLetter() proc Address" How do I interpret this and
avoid it. The EWF partition seems to be present because FBA loops over
and over.
thanks
kevin
 
Kevin,
Im running RAM overlay with CF and get the message "Failed to get
EwfSwapSpecifiedDriveLetter() proc Address"

This is unusual error message. I can only think the ewfmgr is failing to load the ewfdll.dll or the ewfdll.dll is too old or
damaged.
What version of ewfdll.dll you got in your image?
How do I interpret this and avoid it. The EWF partition seems to be present because FBA loops over and over.


Do you have EWF enabled during FBA? You should have it disabled there.
Also, you should be doing the FBA on HDD but not on CF.
 
KM said:
Kevin,




This is unusual error message. I can only think the ewfmgr is failing to load the ewfdll.dll or the ewfdll.dll is too old or
damaged.
What version of ewfdll.dll you got in your image?
don't know.....I've searched TD for it with visibility=100 and get no
results
Do you have EWF enabled during FBA? You should have it disabled there.
I did have it disabled but diabled it, built a new image with same result
Also, you should be doing the FBA on HDD but not on CF.
I am aware of this, but in developement with tools available HDD is not
very productive, so I stay with CF
 
Kevin,
don't know.....I've searched TD for it with visibility=100 and get no results

I meant the ewfdll.dll from your image. The dll belongs to "Enhanced Write Filter" component (visibility=1000) so you should see it.
I did have it disabled but diabled it, built a new image with same result
I am aware of this, but in developement with tools available HDD is not
very productive, so I stay with CF

Up to you but when you damage CF it may be worth and sometimes it is hard to analyze issues that happen because of the bad blocks on
media.
 
KM said:
Kevin,




I meant the ewfdll.dll from your image. The dll belongs to "Enhanced Write Filter" component (visibility=1000) so you should see it.

the EWF compontent version is 5.1.2600.1106
 
Kevin,

You seem to keep telling me the version of the EWF component. But I have asked about the ewfdll.dll binary version. Just tell us the
size (in bytes) and datetime stamp on that file from your runtime image.

Basically, for one of the version of the ewfdll.dll the EwfSwapSpecifiedDriveLetter was removed from the export (don't ask me why -
I don't know :-( ). This must be the binary from "Enhanced Write Filter [Version 5.1.2600.1106, R1507]".
So my suggestion for you would be to upgrade the component to the latest from SP2 (is your image based on SP2 Repository?).
 
KM said:
Kevin,

You seem to keep telling me the version of the EWF component. But I have asked about the ewfdll.dll binary version. Just tell us the
size (in bytes) and datetime stamp on that file from your runtime image.
o....you want the size and time stamp....I got that......been bustin my
head looking a version number....lol
any it's 28,672 bytes and it's dated 1/17/2003

Basically, for one of the version of the ewfdll.dll the EwfSwapSpecifiedDriveLetter was removed from the export (don't ask me why -
I don't know :-( ). This must be the binary from "Enhanced Write Filter [Version 5.1.2600.1106, R1507]".
So my suggestion for you would be to upgrade the component to the latest from SP2 (is your image based on SP2 Repository?).
I have 2 developement machines, one I no is upgraded, but can't be sure
of the other. Is there a quick way to check if its SP2?
kevin
 
Kevin,
o....you want the size and time stamp....I got that......been bustin my
head looking a version number....lol
any it's 28,672 bytes and it's dated 1/17/2003

This is wierd since that version did have the function exported. Could you check the Dll export and find that function from error
message there?

Basically, for one of the version of the ewfdll.dll the EwfSwapSpecifiedDriveLetter was removed from the export (don't ask me why -
I don't know :-( ). This must be the binary from "Enhanced Write Filter [Version 5.1.2600.1106, R1507]".
So my suggestion for you would be to upgrade the component to the latest from SP2 (is your image based on SP2 Repository?).
I have 2 developement machines, one I no is upgraded, but can't be sure
of the other. Is there a quick way to check if its SP2?


What exactly you want to check on SP2? I mean the right ewfdll.dll is definitely there.
 
KM said:
Kevin,




This is wierd since that version did have the function exported. Could you check the Dll export and find that function from error
message there?

I must appologize.....the version refered to does indeed work and it
does have the function... on my other machine, I have an ewfdll.dll with
byte count = 32,960 dated 11/5/2001, and it is the one which doesn't
work and it does not have the function. Sorry for the headache.
All done! :)
why -
I don't know :-( ). This must be the binary from "Enhanced Write Filter [Version 5.1.2600.1106, R1507]".
So my suggestion for you would be to upgrade the component to the latest from SP2 (is your image based on SP2 Repository?).

I have 2 developement machines, one I no is upgraded, but can't be sure
of the other. Is there a quick way to check if its SP2?



What exactly you want to check on SP2? I mean the right ewfdll.dll is definitely there.
 
Kevin,
I must appologize.....the version refered to does indeed work and it
does have the function... on my other machine, I have an ewfdll.dll with
byte count = 32,960 dated 11/5/2001, and it is the one which doesn't
work and it does not have the function. Sorry for the headache.
All done! :)

I am glad we figure that out. :-)

Although I must admit I am not sure why Microsoft has that function removed from the export from particular (intermediate) version
of the ewfdll.dll.
 
Back
Top