| Author |
Message |
YaronM
Guest
|
 Posted:
Sun Feb 13, 2005 9:36 am Post subject:
Re: EWF in SP2 Not Working |
|
|
Hi Nigel,
I've also been strugelling with the new SP2-EWF (check my thread "EWF gives
BSOD").
I've managed to use the original scheme of Slobodan in SP1 for the
EWF-RAM-Registry mode, instead of the SP2-EWF.
it works great without any errors or blue-screens (that I suffered from in
my build).
I removed the SP2-EWF component and added my own component in which I've put
the original ewf.sys/inf from sp1 (the one with the QFE) and the related
registry values as described by Slobodan in the readme file.
I'm using the EWFMGR and the EWF-API from SP2 without any problem.
if you need any assistance - feel free to ask.
Best regards,
YaronM
"Nigel Walker" <nigel@nawX.eclipse.co.uk> wrote in message
news:g5SdnXBAmumok5LfRVnyig@eclipse.net.uk...
| Quote: | Hi Slobodan,
Could you tell me the significance of the "volsnap" registry entry? Is it
required for EWF?
Is there a way I can try your original scheme that worked with SP1? It
relied on a QFE which I would imagine are now integrated into SP2. Would
the registry entries on your scheme work on SP2 or are they tied to the
QFE? I really am in the dark with these registry entries as I can't find
any documentation on their usage other than "use this".
Any suggestions on what I could try would be most welcome!
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OendMsXEFHA.624@TK2MSFTNGP15.phx.gbl...
Hi Nigel,
I have not tried it on final SP2 version, but it worked in Tech Preview.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376rgkF58a0v8U1@individual.net...
Hi Slobodan,
I don't know where to look to proceed with this problem. When I check
the
registry it shows exactly what should be there according to the
Microsoft
documentation, i.e:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf
Name: ErrorControl
Type: REG_DWORD
Value: 0x00000001 (1)
Name: Group
Type: REG_SZ
Value: System Bus Extender
Name: Start
Type: REG_DWORD
Value: 0x00000000 (0)
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
The other stuff I had already set up in TD is also as per Microsoft
instructions:
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
Name: ArcName
Type: REG_SZ
Value: multi(0)disk(0)rdisk(0)partition(1)
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
Name: UpperFilters
Type: REG_MULTI_SZ
Value: EWF
I didn't have a volsnap entry so just added the EWF one.
Do you have EWF RAM REG on SP2 running yourself? If so are there any
differences to how you're doing it?
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:%231p0XOSEFHA.3924@TK2MSFTNGP09.phx.gbl...
Hi Nigel,
There is only one disk.sys driver and it is provided by MS for all
disk
types.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376o8lF5ajpejU1@individual.net...
Ah yes that is true of course.
The thing that worries me is that in the Microsoft notes it says it
MAY
not
work if using a generic disk driver. Well I'm just using the default
driver
which I guess is the generic one. Do you think this may have a
bearing on
the problem? If so, where can I get an alternative driver? I find it
a
bit
weird, especially as I made it work with SP1 - using with your
component.
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OZPqoxREFHA.3732@TK2MSFTNGP14.phx.gbl...
Nigel,
For Reg RAM EWF it is normal that you do not see log in fba.log
file
sice
you have disabled it as par of process to make it work.
It apears that EWF problems begin to sound as an epidemy outbreak
again
:-(
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376marF5auo2uU1@individual.net...
I have EXACTLY the same problems and symptoms as Kilarny. I have
configured
my ssystem the same and I too do not have anything relating to EWF
in
my
FBA
log. This is my brand new build with SP2 and I have only ever
tried
REG
RAM
EWF.
So I would be very interested in any more hints or news!
Regards,
Nigel.
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:1531D08E-A72D-4524-9341-F06577E622DF@microsoft.com...
Doesn't seem to be that either. I readded the component,
dependancy
checked,
ran it - no dice. *ponders*
Thanks for the help. Slobodan...I'll look into that, try from
scratch,
etc.
I appreciate the assistance, I may beg for more help on Monday.
I'll
review
my .SLX again and see if I overlooked something.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
If you don't have anything in the FBA log then it might be that
you
have
used reg ram ewf aproach and then tried to switch to disk
overlay, if so then you should remove EWF component and add it
again
to
image so that call that tell FBA to initialize EWF is
executed .
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:E72255E3-37D3-4E2D-9200-17160DDA1283@microsoft.com...
Running with the corrected volsnap EWF entries (on separate
lines)
didn't
help. I still get the same error state.
I did previously check the FBALOG.TXT and there was no EWF
configuration at
all. The FBA is not even trying to look up the EWF
configuration.
I
did
a
build with 'Start EWF Enabled' checked just to see if that
would
happen.
There were no EWF messages in the log, very strange.
I'm probably missing something REALLY obvious, but it has
yet to
slap
me in
the face like a dead fish.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
You can try just to reboot computer, but if there is no EWF
overlay
partition it won't work.
BTW:
Also check fba.log for info about EWF overlay creation.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:5CBE7FC2-5B44-4964-877A-B793A6F37D2D@microsoft.com...
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
"Slobodan Brcin (eMVP)" wrote:
Kilarny,
This represent two separate filter drivers so you
should
add
them
as separate lines.
volsnap
EWF
Do you have it?
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:469E7557-281A-49A5-AF5A-357E7EF64291@microsoft.com...
Yep, got that one too. I was not clear on whether the
'volsnap'
entry, if
found, should be a separate String value or should be
concatenated with the
'EWF' - in other words should that be 'volsnap EWF'
or:
volsnap
EWF
Thanks for the quick reply...
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Make sure that you have "EWF" value mentioned under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.\Upperfilters
Use regedit fro that purpose.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote
in
message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
I've gotten EWF to work before (in SP1 and
original
XPE).
My previous
method, basically the same as what other topics
cover,
worked fine. Now,
using SP2, it does not work. My first pass I did
nothing
aside from adding a
few components we needed and Upgrading the entire
config -
all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF
components
as described in
the new improved help files (0 Kbytes size, don't
start
enabled, disable
DLL/COM Registration, etc). I've got only a
single
partition on the target
drive I'm building on. I have tried various
timings
and
methods for adding
the registry settings required, and variants on
the
same.
In other words, I THOUGHT I had everything
correct.
However, I get the
'Failed to find EWF Volume' and 'Failed getting
protected
volume
configuration with error 1. Incorrect function.'
error
messages when I try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting
section
caught
my attention, but
I'm not sure what it is I can DO about it. I'm
not
certain
it applies to RAM
EWF type anyway. There are no specific drivers
for my
Disk
Drive type - do I
need to MAKE a component for this?
"Verify that you are using a specific disk
driver in
your
run-time image,
and not a generic disk driver. If you use EWF
with a
generic disk driver, the
EWF volume may not always be created."
Besides that, the drive I'm making this work on
isn't
going to be the final
device used. I'm creating the image on a Hard
Drive
then
moving to Compact
Flash afterwards.
Much gratitude for any assistance that might be
rendered,
O Community.
|
|
|
| Back to top |
|
 |
Nigel Walker
Guest
|
| Posted:
Sun Feb 13, 2005 9:36 am Post subject:
Re: EWF in SP2 Not Working |
|
|
Hi Slobodan,
Could you tell me the significance of the "volsnap" registry entry? Is it
required for EWF?
Is there a way I can try your original scheme that worked with SP1? It
relied on a QFE which I would imagine are now integrated into SP2. Would the
registry entries on your scheme work on SP2 or are they tied to the QFE? I
really am in the dark with these registry entries as I can't find any
documentation on their usage other than "use this".
Any suggestions on what I could try would be most welcome!
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OendMsXEFHA.624@TK2MSFTNGP15.phx.gbl...
| Quote: | Hi Nigel,
I have not tried it on final SP2 version, but it worked in Tech Preview.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376rgkF58a0v8U1@individual.net...
Hi Slobodan,
I don't know where to look to proceed with this problem. When I check the
registry it shows exactly what should be there according to the Microsoft
documentation, i.e:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf
Name: ErrorControl
Type: REG_DWORD
Value: 0x00000001 (1)
Name: Group
Type: REG_SZ
Value: System Bus Extender
Name: Start
Type: REG_DWORD
Value: 0x00000000 (0)
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
The other stuff I had already set up in TD is also as per Microsoft
instructions:
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
Name: ArcName
Type: REG_SZ
Value: multi(0)disk(0)rdisk(0)partition(1)
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
Name: UpperFilters
Type: REG_MULTI_SZ
Value: EWF
I didn't have a volsnap entry so just added the EWF one.
Do you have EWF RAM REG on SP2 running yourself? If so are there any
differences to how you're doing it?
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:%231p0XOSEFHA.3924@TK2MSFTNGP09.phx.gbl...
Hi Nigel,
There is only one disk.sys driver and it is provided by MS for all disk
types.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376o8lF5ajpejU1@individual.net...
Ah yes that is true of course.
The thing that worries me is that in the Microsoft notes it says it
MAY
not
work if using a generic disk driver. Well I'm just using the default
driver
which I guess is the generic one. Do you think this may have a bearing
on
the problem? If so, where can I get an alternative driver? I find it a
bit
weird, especially as I made it work with SP1 - using with your
component.
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OZPqoxREFHA.3732@TK2MSFTNGP14.phx.gbl...
Nigel,
For Reg RAM EWF it is normal that you do not see log in fba.log file
sice
you have disabled it as par of process to make it work.
It apears that EWF problems begin to sound as an epidemy outbreak
again
:-(
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376marF5auo2uU1@individual.net...
I have EXACTLY the same problems and symptoms as Kilarny. I have
configured
my ssystem the same and I too do not have anything relating to EWF
in
my
FBA
log. This is my brand new build with SP2 and I have only ever tried
REG
RAM
EWF.
So I would be very interested in any more hints or news!
Regards,
Nigel.
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:1531D08E-A72D-4524-9341-F06577E622DF@microsoft.com...
Doesn't seem to be that either. I readded the component,
dependancy
checked,
ran it - no dice. *ponders*
Thanks for the help. Slobodan...I'll look into that, try from
scratch,
etc.
I appreciate the assistance, I may beg for more help on Monday.
I'll
review
my .SLX again and see if I overlooked something.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
If you don't have anything in the FBA log then it might be that
you
have
used reg ram ewf aproach and then tried to switch to disk
overlay, if so then you should remove EWF component and add it
again
to
image so that call that tell FBA to initialize EWF is
executed .
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:E72255E3-37D3-4E2D-9200-17160DDA1283@microsoft.com...
Running with the corrected volsnap EWF entries (on separate
lines)
didn't
help. I still get the same error state.
I did previously check the FBALOG.TXT and there was no EWF
configuration at
all. The FBA is not even trying to look up the EWF
configuration.
I
did
a
build with 'Start EWF Enabled' checked just to see if that
would
happen.
There were no EWF messages in the log, very strange.
I'm probably missing something REALLY obvious, but it has yet
to
slap
me in
the face like a dead fish.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
You can try just to reboot computer, but if there is no EWF
overlay
partition it won't work.
BTW:
Also check fba.log for info about EWF overlay creation.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:5CBE7FC2-5B44-4964-877A-B793A6F37D2D@microsoft.com...
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
"Slobodan Brcin (eMVP)" wrote:
Kilarny,
This represent two separate filter drivers so you should
add
them
as separate lines.
volsnap
EWF
Do you have it?
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:469E7557-281A-49A5-AF5A-357E7EF64291@microsoft.com...
Yep, got that one too. I was not clear on whether the
'volsnap'
entry, if
found, should be a separate String value or should be
concatenated with the
'EWF' - in other words should that be 'volsnap EWF'
or:
volsnap
EWF
Thanks for the quick reply...
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Make sure that you have "EWF" value mentioned under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.\Upperfilters
Use regedit fro that purpose.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote
in
message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
I've gotten EWF to work before (in SP1 and
original
XPE).
My previous
method, basically the same as what other topics
cover,
worked fine. Now,
using SP2, it does not work. My first pass I did
nothing
aside from adding a
few components we needed and Upgrading the entire
config -
all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF
components
as described in
the new improved help files (0 Kbytes size, don't
start
enabled, disable
DLL/COM Registration, etc). I've got only a single
partition on the target
drive I'm building on. I have tried various
timings
and
methods for adding
the registry settings required, and variants on
the
same.
In other words, I THOUGHT I had everything
correct.
However, I get the
'Failed to find EWF Volume' and 'Failed getting
protected
volume
configuration with error 1. Incorrect function.'
error
messages when I try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting
section
caught
my attention, but
I'm not sure what it is I can DO about it. I'm not
certain
it applies to RAM
EWF type anyway. There are no specific drivers for
my
Disk
Drive type - do I
need to MAKE a component for this?
"Verify that you are using a specific disk driver
in
your
run-time image,
and not a generic disk driver. If you use EWF with
a
generic disk driver, the
EWF volume may not always be created."
Besides that, the drive I'm making this work on
isn't
going to be the final
device used. I'm creating the image on a Hard
Drive
then
moving to Compact
Flash afterwards.
Much gratitude for any assistance that might be
rendered,
O Community.
|
|
|
| Back to top |
|
|
Nigel Walker
Guest
|
| Posted:
Sun Feb 13, 2005 2:45 pm Post subject:
Re: EWF in SP2 Not Working |
|
|
Hi YaronM,
Thanks for your comments. I have removed all my SP1 stuff so I don't have
the files any more.
Would there be any chance that you could send me your component and files?
My email is nigel at deephaven.co.uk
Regards,
Nigel.
"YaronM" <nospam> wrote in message
news:%23clfqwaEFHA.1564@TK2MSFTNGP09.phx.gbl...
| Quote: | Hi Nigel,
I've also been strugelling with the new SP2-EWF (check my thread "EWF
gives BSOD").
I've managed to use the original scheme of Slobodan in SP1 for the
EWF-RAM-Registry mode, instead of the SP2-EWF.
it works great without any errors or blue-screens (that I suffered from in
my build).
I removed the SP2-EWF component and added my own component in which I've
put the original ewf.sys/inf from sp1 (the one with the QFE) and the
related registry values as described by Slobodan in the readme file.
I'm using the EWFMGR and the EWF-API from SP2 without any problem.
if you need any assistance - feel free to ask.
Best regards,
YaronM
"Nigel Walker" <nigel@nawX.eclipse.co.uk> wrote in message
news:g5SdnXBAmumok5LfRVnyig@eclipse.net.uk...
Hi Slobodan,
Could you tell me the significance of the "volsnap" registry entry? Is it
required for EWF?
Is there a way I can try your original scheme that worked with SP1? It
relied on a QFE which I would imagine are now integrated into SP2. Would
the registry entries on your scheme work on SP2 or are they tied to the
QFE? I really am in the dark with these registry entries as I can't find
any documentation on their usage other than "use this".
Any suggestions on what I could try would be most welcome!
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OendMsXEFHA.624@TK2MSFTNGP15.phx.gbl...
Hi Nigel,
I have not tried it on final SP2 version, but it worked in Tech Preview.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376rgkF58a0v8U1@individual.net...
Hi Slobodan,
I don't know where to look to proceed with this problem. When I check
the
registry it shows exactly what should be there according to the
Microsoft
documentation, i.e:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf
Name: ErrorControl
Type: REG_DWORD
Value: 0x00000001 (1)
Name: Group
Type: REG_SZ
Value: System Bus Extender
Name: Start
Type: REG_DWORD
Value: 0x00000000 (0)
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
The other stuff I had already set up in TD is also as per Microsoft
instructions:
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
Name: ArcName
Type: REG_SZ
Value: multi(0)disk(0)rdisk(0)partition(1)
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
Name: UpperFilters
Type: REG_MULTI_SZ
Value: EWF
I didn't have a volsnap entry so just added the EWF one.
Do you have EWF RAM REG on SP2 running yourself? If so are there any
differences to how you're doing it?
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:%231p0XOSEFHA.3924@TK2MSFTNGP09.phx.gbl...
Hi Nigel,
There is only one disk.sys driver and it is provided by MS for all
disk
types.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376o8lF5ajpejU1@individual.net...
Ah yes that is true of course.
The thing that worries me is that in the Microsoft notes it says it
MAY
not
work if using a generic disk driver. Well I'm just using the default
driver
which I guess is the generic one. Do you think this may have a
bearing on
the problem? If so, where can I get an alternative driver? I find it
a
bit
weird, especially as I made it work with SP1 - using with your
component.
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OZPqoxREFHA.3732@TK2MSFTNGP14.phx.gbl...
Nigel,
For Reg RAM EWF it is normal that you do not see log in fba.log
file
sice
you have disabled it as par of process to make it work.
It apears that EWF problems begin to sound as an epidemy outbreak
again
:-(
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376marF5auo2uU1@individual.net...
I have EXACTLY the same problems and symptoms as Kilarny. I have
configured
my ssystem the same and I too do not have anything relating to
EWF in
my
FBA
log. This is my brand new build with SP2 and I have only ever
tried
REG
RAM
EWF.
So I would be very interested in any more hints or news!
Regards,
Nigel.
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:1531D08E-A72D-4524-9341-F06577E622DF@microsoft.com...
Doesn't seem to be that either. I readded the component,
dependancy
checked,
ran it - no dice. *ponders*
Thanks for the help. Slobodan...I'll look into that, try from
scratch,
etc.
I appreciate the assistance, I may beg for more help on Monday.
I'll
review
my .SLX again and see if I overlooked something.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
If you don't have anything in the FBA log then it might be
that you
have
used reg ram ewf aproach and then tried to switch to disk
overlay, if so then you should remove EWF component and add it
again
to
image so that call that tell FBA to initialize EWF is
executed .
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:E72255E3-37D3-4E2D-9200-17160DDA1283@microsoft.com...
Running with the corrected volsnap EWF entries (on separate
lines)
didn't
help. I still get the same error state.
I did previously check the FBALOG.TXT and there was no EWF
configuration at
all. The FBA is not even trying to look up the EWF
configuration.
I
did
a
build with 'Start EWF Enabled' checked just to see if that
would
happen.
There were no EWF messages in the log, very strange.
I'm probably missing something REALLY obvious, but it has
yet to
slap
me in
the face like a dead fish.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
You can try just to reboot computer, but if there is no
EWF
overlay
partition it won't work.
BTW:
Also check fba.log for info about EWF overlay creation.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:5CBE7FC2-5B44-4964-877A-B793A6F37D2D@microsoft.com...
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
"Slobodan Brcin (eMVP)" wrote:
Kilarny,
This represent two separate filter drivers so you
should
add
them
as separate lines.
volsnap
EWF
Do you have it?
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:469E7557-281A-49A5-AF5A-357E7EF64291@microsoft.com...
Yep, got that one too. I was not clear on whether
the
'volsnap'
entry, if
found, should be a separate String value or should
be
concatenated with the
'EWF' - in other words should that be 'volsnap EWF'
or:
volsnap
EWF
Thanks for the quick reply...
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Make sure that you have "EWF" value mentioned
under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.\Upperfilters
Use regedit fro that purpose.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com
wrote in
message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
I've gotten EWF to work before (in SP1 and
original
XPE).
My previous
method, basically the same as what other topics
cover,
worked fine. Now,
using SP2, it does not work. My first pass I did
nothing
aside from adding a
few components we needed and Upgrading the
entire
config -
all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF
components
as described in
the new improved help files (0 Kbytes size,
don't
start
enabled, disable
DLL/COM Registration, etc). I've got only a
single
partition on the target
drive I'm building on. I have tried various
timings
and
methods for adding
the registry settings required, and variants on
the
same.
In other words, I THOUGHT I had everything
correct.
However, I get the
'Failed to find EWF Volume' and 'Failed getting
protected
volume
configuration with error 1. Incorrect function.'
error
messages when I try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting
section
caught
my attention, but
I'm not sure what it is I can DO about it. I'm
not
certain
it applies to RAM
EWF type anyway. There are no specific drivers
for my
Disk
Drive type - do I
need to MAKE a component for this?
"Verify that you are using a specific disk
driver in
your
run-time image,
and not a generic disk driver. If you use EWF
with a
generic disk driver, the
EWF volume may not always be created."
Besides that, the drive I'm making this work on
isn't
going to be the final
device used. I'm creating the image on a Hard
Drive
then
moving to Compact
Flash afterwards.
Much gratitude for any assistance that might be
rendered,
O Community.
|
|
|
| Back to top |
|
|
Slobodan Brcin (eMVP)
Guest
|
| Posted:
Sun Feb 13, 2005 11:03 pm Post subject:
Re: EWF in SP2 Not Working |
|
|
Hi Nigel,
Search trough repositories folder for file named 823025_ewf.sys it should be there is you installed this QFE.
My component should use that file anyway so it should work.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message news:378lt4F52vd1iU1@individual.net...
| Quote: | Hi YaronM,
Thanks for your comments. I have removed all my SP1 stuff so I don't have
the files any more.
Would there be any chance that you could send me your component and files?
My email is nigel at deephaven.co.uk
Regards,
Nigel.
"YaronM" <nospam> wrote in message
news:%23clfqwaEFHA.1564@TK2MSFTNGP09.phx.gbl...
Hi Nigel,
I've also been strugelling with the new SP2-EWF (check my thread "EWF
gives BSOD").
I've managed to use the original scheme of Slobodan in SP1 for the
EWF-RAM-Registry mode, instead of the SP2-EWF.
it works great without any errors or blue-screens (that I suffered from in
my build).
I removed the SP2-EWF component and added my own component in which I've
put the original ewf.sys/inf from sp1 (the one with the QFE) and the
related registry values as described by Slobodan in the readme file.
I'm using the EWFMGR and the EWF-API from SP2 without any problem.
if you need any assistance - feel free to ask.
Best regards,
YaronM
"Nigel Walker" <nigel@nawX.eclipse.co.uk> wrote in message
news:g5SdnXBAmumok5LfRVnyig@eclipse.net.uk...
Hi Slobodan,
Could you tell me the significance of the "volsnap" registry entry? Is it
required for EWF?
Is there a way I can try your original scheme that worked with SP1? It
relied on a QFE which I would imagine are now integrated into SP2. Would
the registry entries on your scheme work on SP2 or are they tied to the
QFE? I really am in the dark with these registry entries as I can't find
any documentation on their usage other than "use this".
Any suggestions on what I could try would be most welcome!
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OendMsXEFHA.624@TK2MSFTNGP15.phx.gbl...
Hi Nigel,
I have not tried it on final SP2 version, but it worked in Tech Preview.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376rgkF58a0v8U1@individual.net...
Hi Slobodan,
I don't know where to look to proceed with this problem. When I check
the
registry it shows exactly what should be there according to the
Microsoft
documentation, i.e:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf
Name: ErrorControl
Type: REG_DWORD
Value: 0x00000001 (1)
Name: Group
Type: REG_SZ
Value: System Bus Extender
Name: Start
Type: REG_DWORD
Value: 0x00000000 (0)
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
The other stuff I had already set up in TD is also as per Microsoft
instructions:
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0
Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)
Name: ArcName
Type: REG_SZ
Value: multi(0)disk(0)rdisk(0)partition(1)
Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
Name: UpperFilters
Type: REG_MULTI_SZ
Value: EWF
I didn't have a volsnap entry so just added the EWF one.
Do you have EWF RAM REG on SP2 running yourself? If so are there any
differences to how you're doing it?
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:%231p0XOSEFHA.3924@TK2MSFTNGP09.phx.gbl...
Hi Nigel,
There is only one disk.sys driver and it is provided by MS for all
disk
types.
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376o8lF5ajpejU1@individual.net...
Ah yes that is true of course.
The thing that worries me is that in the Microsoft notes it says it
MAY
not
work if using a generic disk driver. Well I'm just using the default
driver
which I guess is the generic one. Do you think this may have a
bearing on
the problem? If so, where can I get an alternative driver? I find it
a
bit
weird, especially as I made it work with SP1 - using with your
component.
Regards,
Nigel.
"Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
news:OZPqoxREFHA.3732@TK2MSFTNGP14.phx.gbl...
Nigel,
For Reg RAM EWF it is normal that you do not see log in fba.log
file
sice
you have disabled it as par of process to make it work.
It apears that EWF problems begin to sound as an epidemy outbreak
again
:-(
Regards,
Slobodan
"Nigel Walker" <nawalkerX@softhome.net> wrote in message
news:376marF5auo2uU1@individual.net...
I have EXACTLY the same problems and symptoms as Kilarny. I have
configured
my ssystem the same and I too do not have anything relating to
EWF in
my
FBA
log. This is my brand new build with SP2 and I have only ever
tried
REG
RAM
EWF.
So I would be very interested in any more hints or news!
Regards,
Nigel.
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:1531D08E-A72D-4524-9341-F06577E622DF@microsoft.com...
Doesn't seem to be that either. I readded the component,
dependancy
checked,
ran it - no dice. *ponders*
Thanks for the help. Slobodan...I'll look into that, try from
scratch,
etc.
I appreciate the assistance, I may beg for more help on Monday.
I'll
review
my .SLX again and see if I overlooked something.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
If you don't have anything in the FBA log then it might be
that you
have
used reg ram ewf aproach and then tried to switch to disk
overlay, if so then you should remove EWF component and add it
again
to
image so that call that tell FBA to initialize EWF is
executed .
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:E72255E3-37D3-4E2D-9200-17160DDA1283@microsoft.com...
Running with the corrected volsnap EWF entries (on separate
lines)
didn't
help. I still get the same error state.
I did previously check the FBALOG.TXT and there was no EWF
configuration at
all. The FBA is not even trying to look up the EWF
configuration.
I
did
a
build with 'Start EWF Enabled' checked just to see if that
would
happen.
There were no EWF messages in the log, very strange.
I'm probably missing something REALLY obvious, but it has
yet to
slap
me in
the face like a dead fish.
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
You can try just to reboot computer, but if there is no
EWF
overlay
partition it won't work.
BTW:
Also check fba.log for info about EWF overlay creation.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:5CBE7FC2-5B44-4964-877A-B793A6F37D2D@microsoft.com...
Nope, didn't have them separate. Now, I guess I need to
have
FBA
run again
with the proper entries there?
"Slobodan Brcin (eMVP)" wrote:
Kilarny,
This represent two separate filter drivers so you
should
add
them
as separate lines.
volsnap
EWF
Do you have it?
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in
message
news:469E7557-281A-49A5-AF5A-357E7EF64291@microsoft.com...
Yep, got that one too. I was not clear on whether
the
'volsnap'
entry, if
found, should be a separate String value or should
be
concatenated with the
'EWF' - in other words should that be 'volsnap EWF'
or:
volsnap
EWF
Thanks for the quick reply...
"Slobodan Brcin (eMVP)" wrote:
Hi Kilarny,
Make sure that you have "EWF" value mentioned
under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.\Upperfilters
Use regedit fro that purpose.
Regards,
Slobodan
"Kilarny" <Kilarny@discussions.microsoft.com
wrote in
message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
I've gotten EWF to work before (in SP1 and
original
XPE).
My previous
method, basically the same as what other topics
cover,
worked fine. Now,
using SP2, it does not work. My first pass I did
nothing
aside from adding a
few components we needed and Upgrading the
entire
config -
all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF
components
as described in
the new improved help files (0 Kbytes size,
don't
start
enabled, disable
DLL/COM Registration, etc). I've got only a
single
partition on the target
drive I'm building on. I have tried various
timings
and
methods for adding
the registry settings required, and variants on
the
same.
In other words, I THOUGHT I had everything
correct.
However, I get the
'Failed to find EWF Volume' and 'Failed getting
protected
volume
configuration with error 1. Incorrect function.'
error
messages when I try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting
section
caught
my attention, but
I'm not sure what it is I can DO about it. I'm
not
certain
it applies to RAM
EWF type anyway. There are no specific drivers
for my
Disk
Drive type - do I
need to MAKE a component for this?
"Verify that you are using a specific disk
driver in
your
run-time image,
and not a generic disk driver. If you use EWF
with a
generic disk driver, the
EWF volume may not always be created."
Besides that, the drive I'm making this work on
isn't
going to be the final
device used. I'm creating the image on a Hard
Drive
then
moving to Compact
Flash afterwards.
Much gratitude for any assistance that might be
rendered,
O Community.
|
|
|
| Back to top |
|
|
Matt Kellner (MS)
Guest
|
| Posted:
Tue Feb 15, 2005 1:57 am Post subject:
Re: EWF in SP2 Not Working |
|
|
Hi Kilarny and Nigel. Thanks for posting about this issue. We're
investigating issues related to EWF, and we will post a reply to the
newsgroup when we have a solution. To help us investigate this, please
submit a bug report at the following page:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx -
please include as complete a description of your hardware and software
configurations as possible.
Thanks!
--
Matt Kellner (mattkell@online.microsoft.com)
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
| Quote: | I've gotten EWF to work before (in SP1 and original XPE). My previous
method, basically the same as what other topics cover, worked fine. Now,
using SP2, it does not work. My first pass I did nothing aside from adding
a
few components we needed and Upgrading the entire config - all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF components as described in
the new improved help files (0 Kbytes size, don't start enabled, disable
DLL/COM Registration, etc). I've got only a single partition on the target
drive I'm building on. I have tried various timings and methods for adding
the registry settings required, and variants on the same.
In other words, I THOUGHT I had everything correct. However, I get the
'Failed to find EWF Volume' and 'Failed getting protected volume
configuration with error 1. Incorrect function.' error messages when I try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting section caught my attention,
but
I'm not sure what it is I can DO about it. I'm not certain it applies to
RAM
EWF type anyway. There are no specific drivers for my Disk Drive type - do
I
need to MAKE a component for this?
"Verify that you are using a specific disk driver in your run-time image,
and not a generic disk driver. If you use EWF with a generic disk driver,
the
EWF volume may not always be created."
Besides that, the drive I'm making this work on isn't going to be the
final
device used. I'm creating the image on a Hard Drive then moving to Compact
Flash afterwards.
Much gratitude for any assistance that might be rendered, O Community. |
|
|
| Back to top |
|
|
Kilarny
Guest
|
| Posted:
Thu Feb 17, 2005 2:11 am Post subject:
Re: EWF in SP2 Not Working |
|
|
I posted a bug. I also *trumpet fanfare* got it WORKING!
Here's what seems to make the difference:
Follow all directions for RAM Reg mode EWF except these:
DON'T Disable the DLL/COM registration as specified. I get the old-style
extra type 45 or whatever partition on the disk, but EWF comes up disabled as
it should.
DON'T add ANY reg settings until such time as you want it enabled, then you
can use the old-school method of changing the registry, or can use the EWFMGR
command-line or the API.
"Of course, there are still a few bugs in the system." -B.D.
"Matt Kellner (MS)" wrote:
| Quote: | Hi Kilarny and Nigel. Thanks for posting about this issue. We're
investigating issues related to EWF, and we will post a reply to the
newsgroup when we have a solution. To help us investigate this, please
submit a bug report at the following page:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx -
please include as complete a description of your hardware and software
configurations as possible.
Thanks!
--
Matt Kellner (mattkell@online.microsoft.com)
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
I've gotten EWF to work before (in SP1 and original XPE). My previous
method, basically the same as what other topics cover, worked fine. Now,
using SP2, it does not work. My first pass I did nothing aside from adding
a
few components we needed and Upgrading the entire config - all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF components as described in
the new improved help files (0 Kbytes size, don't start enabled, disable
DLL/COM Registration, etc). I've got only a single partition on the target
drive I'm building on. I have tried various timings and methods for adding
the registry settings required, and variants on the same.
In other words, I THOUGHT I had everything correct. However, I get the
'Failed to find EWF Volume' and 'Failed getting protected volume
configuration with error 1. Incorrect function.' error messages when I try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting section caught my attention,
but
I'm not sure what it is I can DO about it. I'm not certain it applies to
RAM
EWF type anyway. There are no specific drivers for my Disk Drive type - do
I
need to MAKE a component for this?
"Verify that you are using a specific disk driver in your run-time image,
and not a generic disk driver. If you use EWF with a generic disk driver,
the
EWF volume may not always be created."
Besides that, the drive I'm making this work on isn't going to be the
final
device used. I'm creating the image on a Hard Drive then moving to Compact
Flash afterwards.
Much gratitude for any assistance that might be rendered, O Community.
|
|
|
| Back to top |
|
|
Matt Kellner (MS)
Guest
|
| Posted:
Thu Feb 17, 2005 3:45 am Post subject:
Re: EWF in SP2 Not Working |
|
|
That's interesting. Basically, if I'm reading you right, all you're doing
at this point is setting up a basic RAM overlay, and then going and making
the required modifications manually. That is, as I understand it, the old
process, and it requires that there be a blank, unpartitioned area on the
target hard drive where EWF can set up a partition.
The purpose of the MSDN article is to circumvent the need for a separate EWF
partition, and to have EWF configured for RAM Reg operation when it finishes
FBA. This should simplify the process.
I did identify a typo in our instructions that may have been causing some
problems, however - please see my new thread titled "Resolution for EWF RAM
REG 'Incorrect Function' issue" for more information.
In Step 8 of the instuctions, a reg key is called out that has a period at
the end:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
This key should not have a period at the end - this will cause the data
underneath it to be stored at the wrong location, and thus the system will
never pick up the EWF component. Simply remove the period when entering
this information into Target Designer, and this should resolve the problem.
We're taking steps to correct this error as well, and we apologize for the
confusion.
--
Matt Kellner (mattkell@online.microsoft.com)
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:70E06AE7-8DF9-455B-B9A4-4AAAF5E77F06@microsoft.com...
| Quote: | I posted a bug. I also *trumpet fanfare* got it WORKING!
Here's what seems to make the difference:
Follow all directions for RAM Reg mode EWF except these:
DON'T Disable the DLL/COM registration as specified. I get the old-style
extra type 45 or whatever partition on the disk, but EWF comes up disabled
as
it should.
DON'T add ANY reg settings until such time as you want it enabled, then
you
can use the old-school method of changing the registry, or can use the
EWFMGR
command-line or the API.
"Of course, there are still a few bugs in the system." -B.D.
"Matt Kellner (MS)" wrote:
Hi Kilarny and Nigel. Thanks for posting about this issue. We're
investigating issues related to EWF, and we will post a reply to the
newsgroup when we have a solution. To help us investigate this, please
submit a bug report at the following page:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx -
please include as complete a description of your hardware and software
configurations as possible.
Thanks!
--
Matt Kellner (mattkell@online.microsoft.com)
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no
rights.
===============================
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
I've gotten EWF to work before (in SP1 and original XPE). My previous
method, basically the same as what other topics cover, worked fine.
Now,
using SP2, it does not work. My first pass I did nothing aside from
adding
a
few components we needed and Upgrading the entire config - all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF components as described
in
the new improved help files (0 Kbytes size, don't start enabled,
disable
DLL/COM Registration, etc). I've got only a single partition on the
target
drive I'm building on. I have tried various timings and methods for
adding
the registry settings required, and variants on the same.
In other words, I THOUGHT I had everything correct. However, I get the
'Failed to find EWF Volume' and 'Failed getting protected volume
configuration with error 1. Incorrect function.' error messages when I
try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting section caught my attention,
but
I'm not sure what it is I can DO about it. I'm not certain it applies
to
RAM
EWF type anyway. There are no specific drivers for my Disk Drive type -
do
I
need to MAKE a component for this?
"Verify that you are using a specific disk driver in your run-time
image,
and not a generic disk driver. If you use EWF with a generic disk
driver,
the
EWF volume may not always be created."
Besides that, the drive I'm making this work on isn't going to be the
final
device used. I'm creating the image on a Hard Drive then moving to
Compact
Flash afterwards.
Much gratitude for any assistance that might be rendered, O Community.
|
|
|
| Back to top |
|
|
Slobodan Brcin (eMVP)
Guest
|
| Posted:
Thu Feb 17, 2005 4:32 am Post subject:
Re: EWF in SP2 Not Working |
|
|
Kilarny,
ewf.sys driver is filter based driver which is extremely simple and do not need any dependencies on other drivers and files.
Registry based EWF is solely configured trough registry, and all issues that you and other are experiencing is that you do not add
all registry entries correctly. Please note that MS documentation is uncomplete regarding the needed registry entries.
You can verify this by simple test.
From your current working Reg RAM EWF XPe use regedit to export two reg files with:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf
Then do this from your XPe image made according to the MS documentation.
Compare them and you will see the differences. Also you can port them here.
Regards,
Slobodan
"Matt Kellner (MS)" <mattkell@microsoft.com> wrote in message news:OTxELlHFFHA.1576@TK2MSFTNGP10.phx.gbl...
| Quote: | That's interesting. Basically, if I'm reading you right, all you're doing
at this point is setting up a basic RAM overlay, and then going and making
the required modifications manually. That is, as I understand it, the old
process, and it requires that there be a blank, unpartitioned area on the
target hard drive where EWF can set up a partition.
The purpose of the MSDN article is to circumvent the need for a separate EWF
partition, and to have EWF configured for RAM Reg operation when it finishes
FBA. This should simplify the process.
I did identify a typo in our instructions that may have been causing some
problems, however - please see my new thread titled "Resolution for EWF RAM
REG 'Incorrect Function' issue" for more information.
In Step 8 of the instuctions, a reg key is called out that has a period at
the end:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
This key should not have a period at the end - this will cause the data
underneath it to be stored at the wrong location, and thus the system will
never pick up the EWF component. Simply remove the period when entering
this information into Target Designer, and this should resolve the problem.
We're taking steps to correct this error as well, and we apologize for the
confusion.
--
Matt Kellner (mattkell@online.microsoft.com)
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:70E06AE7-8DF9-455B-B9A4-4AAAF5E77F06@microsoft.com...
I posted a bug. I also *trumpet fanfare* got it WORKING!
Here's what seems to make the difference:
Follow all directions for RAM Reg mode EWF except these:
DON'T Disable the DLL/COM registration as specified. I get the old-style
extra type 45 or whatever partition on the disk, but EWF comes up disabled
as
it should.
DON'T add ANY reg settings until such time as you want it enabled, then
you
can use the old-school method of changing the registry, or can use the
EWFMGR
command-line or the API.
"Of course, there are still a few bugs in the system." -B.D.
"Matt Kellner (MS)" wrote:
Hi Kilarny and Nigel. Thanks for posting about this issue. We're
investigating issues related to EWF, and we will post a reply to the
newsgroup when we have a solution. To help us investigate this, please
submit a bug report at the following page:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx -
please include as complete a description of your hardware and software
configurations as possible.
Thanks!
--
Matt Kellner (mattkell@online.microsoft.com)
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no
rights.
===============================
"Kilarny" <Kilarny@discussions.microsoft.com> wrote in message
news:00A9F204-21A1-44A6-88EE-A65EF83452F9@microsoft.com...
I've gotten EWF to work before (in SP1 and original XPE). My previous
method, basically the same as what other topics cover, worked fine.
Now,
using SP2, it does not work. My first pass I did nothing aside from
adding
a
few components we needed and Upgrading the entire config - all using a
previous .SLX that ran EWF just fine.
I've got the PnP component, I've set up the EWF components as described
in
the new improved help files (0 Kbytes size, don't start enabled,
disable
DLL/COM Registration, etc). I've got only a single partition on the
target
drive I'm building on. I have tried various timings and methods for
adding
the registry settings required, and variants on the same.
In other words, I THOUGHT I had everything correct. However, I get the
'Failed to find EWF Volume' and 'Failed getting protected volume
configuration with error 1. Incorrect function.' error messages when I
try
EWFMGR and EWFMGR C:.
This note in the Help file Troubleshooting section caught my attention,
but
I'm not sure what it is I can DO about it. I'm not certain it applies
to
RAM
EWF type anyway. There are no specific drivers for my Disk Drive type -
do
I
need to MAKE a component for this?
"Verify that you are using a specific disk driver in your run-time
image,
and not a generic disk driver. If you use EWF with a generic disk
driver,
the
EWF volume may not always be created."
Besides that, the drive I'm making this work on isn't going to be the
final
device used. I'm creating the image on a Hard Drive then moving to
Compact
Flash afterwards.
Much gratitude for any assistance that might be rendered, O Community.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in