M
Matt Kellner \(MS\)
Hi everyone. Since multiple people have reported this problem, I'm making a
new post regarding a possible solution.
Several of you have reported having difficulties getting EWF RAM REG
configurations working properly. In many of the cases, the problem is that
EWF does not appear to have been configured at all after FBA - if you type
"ewfmgr c:", you might get an error message that includes the words
"Incorrect Function".
A problem has been identified with the RAM REG instructions located at
http://msdn.microsoft.com/library/d...lp/html/xegrfconfiguringewframregoverlays.asp .
In Step 8, the instructions read as follows:
"8. Add the following registry keys to your configuration. You can add these
to your configuration as extra resources, you can create a component for
these registry keys, or you can update your run-time image post-FBA by using
regedit. For more information about how to add this registry key to your
configuration, see Adding Registry Data to a Configuration.
....
* Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
Name: UpperFilters
...."
The problem is in the Key Name - there is a period at the end of the key,
which is a typo. If you copy and paste this key from the MSDN page into
Target Designer, you should make sure you remove the period at the end of
the key when adding the UpperFilters value to your configuration.
Otherwise, the UpperFilters value will be stored in the wrong location and
will be inaccessible to the EWF component, and EWF will not be properly
initialized.
We apologize for this error and any inconvenience it has caused, and we will
take steps to have it corrected as soon as possible. Thanks for bringing
the matter to our attention! I would be interested to see if this helps
resolve your problems. =)
--
Matt Kellner ([email protected])
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
new post regarding a possible solution.
Several of you have reported having difficulties getting EWF RAM REG
configurations working properly. In many of the cases, the problem is that
EWF does not appear to have been configured at all after FBA - if you type
"ewfmgr c:", you might get an error message that includes the words
"Incorrect Function".
A problem has been identified with the RAM REG instructions located at
http://msdn.microsoft.com/library/d...lp/html/xegrfconfiguringewframregoverlays.asp .
In Step 8, the instructions read as follows:
"8. Add the following registry keys to your configuration. You can add these
to your configuration as extra resources, you can create a component for
these registry keys, or you can update your run-time image post-FBA by using
regedit. For more information about how to add this registry key to your
configuration, see Adding Registry Data to a Configuration.
....
* Key Name:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}.
Name: UpperFilters
...."
The problem is in the Key Name - there is a period at the end of the key,
which is a typo. If you copy and paste this key from the MSDN page into
Target Designer, you should make sure you remove the period at the end of
the key when adding the UpperFilters value to your configuration.
Otherwise, the UpperFilters value will be stored in the wrong location and
will be inaccessible to the EWF component, and EWF will not be properly
initialized.
We apologize for this error and any inconvenience it has caused, and we will
take steps to have it corrected as soon as possible. Thanks for bringing
the matter to our attention! I would be interested to see if this helps
resolve your problems. =)
--
Matt Kellner ([email protected])
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================