Hi,
I had set hardware key FailReasonString. Even then I get the default message for code 10. I had set the following key
HKR,FailReasonString,“Failed to start because …”
I have added this key in DDInstall.hw section and I see this in HKLM\System\CCS\ENUM\USB\VID_XXX&PID_XXXX\nnnnnnnnnnn\Device Parameters
Is there anything that I need to set?
Thanks
I’ll go out on a limb here and state that that stuff doesn’t work and most
likely never has on the pnp versions of Windows NT (W2K and later.)
On Jan 4, 2008 7:46 PM, wrote:
> Hi,
>
> I had set hardware key FailReasonString. Even then I get the default
> message for code 10. I had set the following key
>
> HKR,FailReasonString,“Failed to start because …”
>
> I have added this key in DDInstall.hw section and I see this in
> HKLM\System\CCS\ENUM\USB\VID_XXX&PID_XXXX\nnnnnnnnnnn\Device Parameters
>
> Is there anything that I need to set?
>
> Thanks
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Mark Roddy
xxxxx@acmet.com wrote:
I had set hardware key FailReasonString. Even then I get the default message for code 10. I had set the following key
HKR,FailReasonString,“Failed to start because …”
I have added this key in DDInstall.hw section and I see this in HKLM\System\CCS\ENUM\USB\VID_XXX&PID_XXXX\nnnnnnnnnnn\Device Parameters
Is there anything that I need to set?
The anecdotal evidence on the web suggests that FailReasonString was a
Win98/WinME feature that never made it to the NT systems. It is
certainly true that the string “FailReasonString” does not appear in the
Device Manager binary (devmgr.dll).
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.