Discussion:
Virtual driver
(too old to reply)
d***@gmail.com
2008-08-27 11:33:27 UTC
Permalink
Hi

I want to load hidusbfx2 driver as virtual one. But when I load
*.inf , it shows "The specified location does not contain information
about your hardware". What are the changes I made when I use this
driver for virtual?

I attached my inf file. Here I change only USB\VID_0547&PID_1002 to
virtualname.

Is it correct?

--------------------------------------------------------------------------------------------------------------
[Version]
Signature="$CHICAGO$"
Class=HIDClass
ClassGuid={745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Provider=%VENDOR%
LayoutFile=layout.inf
DriverVer=08/27/2008,6.0.6001.18000
CatalogFile=kmdfsamples.cat

;
; Layout.inf (etc.) list all files shipped with the operating system
so the
; source description sections are only needed if other files are
needed.
;
; In order to use IHV drivers, the SourceDisksNames section must
list the
; disk(s) containing the drivers and the SourceDisksFiles section
must list
; which disk number each file to be copied is found on.
; Disk number 99 is used to avoid a conflict with the disk numbers
defined
; in layout.inf
;
; Files used in a driver installation need to be digitally signed
otherwise
; installation may fail. See documentation elsewhere in the DDK
regarding
; driver signing.

[SourceDisksFiles]
hidusbfx2.sys = 99
hidkmdf.sys = 99

[SourceDisksNames]
99 = %DISK_NAME%,,,""

[DestinationDirs]
CopyFilesSYS = 12
CopyFilesDLL = 11

[Manufacturer]
%VENDOR%=Vendor, NTx86

; For Win2K
[Vendor]
%hidusbfx2% = hidusbfx2.Inst, USB\VID_0547&PID_1002
%customCollection% = customCollection.Inst, HID_DEVICE_UP:FF00_U:
0001

; For XP and later
[Vendor.NTx86]
%hidusbfx2% = hidusbfx2.Inst, USB\VID_0547&PID_1002
%customCollection% = customCollection.Inst, HID_DEVICE_UP:FF00_U:
0001


;===============================================================
; hidusbfx2
;===============================================================
[hidusbfx2.Inst.NT]
CopyFiles = CopyFilesSYS, CopyFilesDLL

[hidusbfx2.Inst.NT.HW]
AddReg = hidusbfx2_Parameters.AddReg

;
; hidkmdf is the function driver and hidusbfx2 is the lower filter
;
[hidusbfx2.Inst.NT.Services]
AddService = hidkmdf,0x00000002,hidkmdf_Service_Inst,
AddService = hidusbfx2,, hidusbfx2_Service_Inst

[CopyFilesSYS]
hidusbfx2.sys
HidClass.sys,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for win2k)
HidParse.sys,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for win2k)
hidkmdf.sys

[CopyFilesDLL]
Hid.dll,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for win2k)

[hidusbfx2_Parameters.AddReg]
HKR,,"LowerFilters",0x00010000,"hidusbfx2"

[hidusbfx2_Service_Inst]
DisplayName = %hidusbfx2%
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_IGNORE%
ServiceBinary = %12%\hidusbfx2.sys
LoadOrderGroup = PNP Filter

[hidkmdf_Service_Inst]
DisplayName = %hidkmdf.SVCDESC%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\hidkmdf.sys


;===============================================================
; Custom Collection install section
; - Only a Null service is installed.
;===============================================================
[customCollection.Inst]

[customCollection.Inst.NT]

[customCollection.Inst.NT.HW]
AddReg = customCollection.Inst.AddReg.NT.HW

[customCollection.Inst.AddReg.NT.HW]
HKR,,"SelectiveSuspendEnabled",0x00000001,0x1

[customCollection.Inst.NT.Services]
AddService = ,0x00000002, ; NULL Service


;================================================================
;--- WDF Coinstaller installation ------
;
[DestinationDirs]
hidusbfx2.Inst_CoInstaller_CopyFiles = 11

[hidusbfx2.Inst.NT.CoInstallers]
AddReg=hidusbfx2.Inst_CoInstaller_AddReg
CopyFiles=hidusbfx2.Inst_CoInstaller_CopyFiles

[hidusbfx2.Inst_CoInstaller_AddReg]
HKR,,CoInstallers32,0x00010000,
"WdfCoInstaller01007.dll,WdfCoInstaller"

[hidusbfx2.Inst_CoInstaller_CopyFiles]
WdfCoInstaller01007.dll,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for
win2k)

[SourceDisksFiles]
WdfCoInstaller01007.dll=99 ; make sure the number matches with
SourceDisksNames

[hidusbfx2.Inst.NT.Wdf]
KmdfService = hidusbfx2, hidusbfx2_wdfsect
[hidusbfx2_wdfsect]
KmdfLibraryVersion = 1.7

[Strings]
; *******Localizable Strings*******
VENDOR = "Vendor Name"
hidusbfx2 = "KMDF HID Minidriver for OSR USB-FX2 Device"
customCollection = "HID Vendor-defined Collection for OSR USB-FX2"
DISK_NAME = "HID USB FX2 Device Sample Install Disk"
hidkmdf.SVCDESC= "Filter Driver Service for HID-KMDF Interface layer"

; *******Non Localizable Strings*******

SERVICE_BOOT_START = 0x0
SERVICE_SYSTEM_START = 0x1
SERVICE_AUTO_START = 0x2
SERVICE_DEMAND_START = 0x3
SERVICE_DISABLED = 0x4

SERVICE_KERNEL_DRIVER = 0x1
SERVICE_ERROR_IGNORE = 0x0
SERVICE_ERROR_NORMAL = 0x1
SERVICE_ERROR_SEVERE = 0x2
SERVICE_ERROR_CRITICAL = 0x3

REG_EXPAND_SZ = 0x00020000
REG_DWORD = 0x00010001
REG_MULTI_SZ = 0x00010000
REG_BINARY = 0x00000001
REG_SZ = 0x00000000


--------------------------------------------------------------------------------------------------------------

Thanks for Advance.

Regards - Dsrking.
Doron Holan [MSFT]
2008-08-27 17:44:27 UTC
Permalink
where did you change USB\VID_0547&PID_1002 to a different hw ID? i see the
following
Post by d***@gmail.com
; For Win2K
[Vendor]
%hidusbfx2% = hidusbfx2.Inst, USB\VID_0547&PID_1002
0001
; For XP and later
[Vendor.NTx86]
%hidusbfx2% = hidusbfx2.Inst, USB\VID_0547&PID_1002
0001
which still has the hardware ID. the customCollection ID's are HID
enumerated IDs which i hope is not what you are using as the new virtual hw
id. do something like this
Post by d***@gmail.com
[Vendor.NTx86]
%hidusbfx2% = hidusbfx2.Inst, root\myfakeid
and then use devcon to install it

devcon install <your inf name> root\myfakeid

d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi
I want to load hidusbfx2 driver as virtual one. But when I load
*.inf , it shows "The specified location does not contain information
about your hardware". What are the changes I made when I use this
driver for virtual?
I attached my inf file. Here I change only USB\VID_0547&PID_1002 to
virtualname.
Is it correct?
--------------------------------------------------------------------------------------------------------------
[Version]
Signature="$CHICAGO$"
Class=HIDClass
ClassGuid={745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Provider=%VENDOR%
LayoutFile=layout.inf
DriverVer=08/27/2008,6.0.6001.18000
CatalogFile=kmdfsamples.cat
;
; Layout.inf (etc.) list all files shipped with the operating system
so the
; source description sections are only needed if other files are
needed.
;
; In order to use IHV drivers, the SourceDisksNames section must
list the
; disk(s) containing the drivers and the SourceDisksFiles section
must list
; which disk number each file to be copied is found on.
; Disk number 99 is used to avoid a conflict with the disk numbers
defined
; in layout.inf
;
; Files used in a driver installation need to be digitally signed
otherwise
; installation may fail. See documentation elsewhere in the DDK
regarding
; driver signing.
[SourceDisksFiles]
hidusbfx2.sys = 99
hidkmdf.sys = 99
[SourceDisksNames]
99 = %DISK_NAME%,,,""
[DestinationDirs]
CopyFilesSYS = 12
CopyFilesDLL = 11
[Manufacturer]
%VENDOR%=Vendor, NTx86
; For Win2K
[Vendor]
%hidusbfx2% = hidusbfx2.Inst, USB\VID_0547&PID_1002
0001
; For XP and later
[Vendor.NTx86]
%hidusbfx2% = hidusbfx2.Inst, USB\VID_0547&PID_1002
0001
;===============================================================
; hidusbfx2
;===============================================================
[hidusbfx2.Inst.NT]
CopyFiles = CopyFilesSYS, CopyFilesDLL
[hidusbfx2.Inst.NT.HW]
AddReg = hidusbfx2_Parameters.AddReg
;
; hidkmdf is the function driver and hidusbfx2 is the lower filter
;
[hidusbfx2.Inst.NT.Services]
AddService = hidkmdf,0x00000002,hidkmdf_Service_Inst,
AddService = hidusbfx2,, hidusbfx2_Service_Inst
[CopyFilesSYS]
hidusbfx2.sys
HidClass.sys,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for win2k)
HidParse.sys,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for win2k)
hidkmdf.sys
[CopyFilesDLL]
Hid.dll,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for win2k)
[hidusbfx2_Parameters.AddReg]
HKR,,"LowerFilters",0x00010000,"hidusbfx2"
[hidusbfx2_Service_Inst]
DisplayName = %hidusbfx2%
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_IGNORE%
ServiceBinary = %12%\hidusbfx2.sys
LoadOrderGroup = PNP Filter
[hidkmdf_Service_Inst]
DisplayName = %hidkmdf.SVCDESC%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\hidkmdf.sys
;===============================================================
; Custom Collection install section
; - Only a Null service is installed.
;===============================================================
[customCollection.Inst]
[customCollection.Inst.NT]
[customCollection.Inst.NT.HW]
AddReg = customCollection.Inst.AddReg.NT.HW
[customCollection.Inst.AddReg.NT.HW]
HKR,,"SelectiveSuspendEnabled",0x00000001,0x1
[customCollection.Inst.NT.Services]
AddService = ,0x00000002, ; NULL Service
;================================================================
;--- WDF Coinstaller installation ------
;
[DestinationDirs]
hidusbfx2.Inst_CoInstaller_CopyFiles = 11
[hidusbfx2.Inst.NT.CoInstallers]
AddReg=hidusbfx2.Inst_CoInstaller_AddReg
CopyFiles=hidusbfx2.Inst_CoInstaller_CopyFiles
[hidusbfx2.Inst_CoInstaller_AddReg]
HKR,,CoInstallers32,0x00010000,
"WdfCoInstaller01007.dll,WdfCoInstaller"
[hidusbfx2.Inst_CoInstaller_CopyFiles]
WdfCoInstaller01007.dll,,,0x00000010 ;COPYFLG_NO_OVERWRITE (for
win2k)
[SourceDisksFiles]
WdfCoInstaller01007.dll=99 ; make sure the number matches with
SourceDisksNames
[hidusbfx2.Inst.NT.Wdf]
KmdfService = hidusbfx2, hidusbfx2_wdfsect
[hidusbfx2_wdfsect]
KmdfLibraryVersion = 1.7
[Strings]
; *******Localizable Strings*******
VENDOR = "Vendor Name"
hidusbfx2 = "KMDF HID Minidriver for OSR USB-FX2 Device"
customCollection = "HID Vendor-defined Collection for OSR USB-FX2"
DISK_NAME = "HID USB FX2 Device Sample Install Disk"
hidkmdf.SVCDESC= "Filter Driver Service for HID-KMDF Interface layer"
; *******Non Localizable Strings*******
SERVICE_BOOT_START = 0x0
SERVICE_SYSTEM_START = 0x1
SERVICE_AUTO_START = 0x2
SERVICE_DEMAND_START = 0x3
SERVICE_DISABLED = 0x4
SERVICE_KERNEL_DRIVER = 0x1
SERVICE_ERROR_IGNORE = 0x0
SERVICE_ERROR_NORMAL = 0x1
SERVICE_ERROR_SEVERE = 0x2
SERVICE_ERROR_CRITICAL = 0x3
REG_EXPAND_SZ = 0x00020000
REG_DWORD = 0x00010001
REG_MULTI_SZ = 0x00010000
REG_BINARY = 0x00000001
REG_SZ = 0x00000000
--------------------------------------------------------------------------------------------------------------
Thanks for Advance.
Regards - Dsrking.
d***@gmail.com
2008-08-28 10:42:37 UTC
Permalink
Hi Doron,

Thanks for Reply.

I changed and used inf as you mentioined. But System shows the same
msg "The specified location does not contain information about your
hardware". I think , the problem is in ClassGuid value. whenever I
change my ClassGuid value to some other value, .inf is accepted but
finally it shows "An error occurred during the installation of the
device" and
"The required section was not found in the INF". But ClassGUID values
are provided by System supplied Device setup for "class=HIDClass"
i.e., ClassGUID = {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.

Is my point correct ? If it is correct also, finally it shows error
msg.

Is there any changes in above inf.?

Regards - Dsrking.
d***@gmail.com
2008-08-28 11:32:06 UTC
Permalink
Hi Doron,

I also checked for CustomCollection, Here there is no .sys file
loaded. My requirement is sys is also loaded for virtual.

I copied the hidusbfx2.inst related blocks into CustomCollection.inst
respectively. Here also I seems the same error message.

I checked my inf in "ChkInf " tool, it shows warning message as,

[hidusbfx2.Inst.NT.Wdf]
; (W22.1.2083) Section [HIDUSBFX2.INST.NT.WDF] not referenced
--- Warning
KmdfService = hidusbfx2, hidusbfx2_wdfsect
[hidusbfx2_wdfsect]
; (W22.1.2083) Section [HIDUSBFX2_WDFSECT] not referenced
--- Warning
KmdfLibraryVersion = 1.7
Doron Holan [MSFT]
2008-08-28 18:33:09 UTC
Permalink
read http://blogs.msdn.com/doronh/archive/2006/08/31/734412.aspx to see
which logs you should use to debug a failed device install

d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi Doron,
Thanks for Reply.
I changed and used inf as you mentioined. But System shows the same
msg "The specified location does not contain information about your
hardware". I think , the problem is in ClassGuid value. whenever I
change my ClassGuid value to some other value, .inf is accepted but
finally it shows "An error occurred during the installation of the
device" and
"The required section was not found in the INF". But ClassGUID values
are provided by System supplied Device setup for "class=HIDClass"
i.e., ClassGUID = {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.
Is my point correct ? If it is correct also, finally it shows error
msg.
Is there any changes in above inf.?
Regards - Dsrking.
d***@gmail.com
2008-08-29 07:19:04 UTC
Permalink
Hi Doron,

Thanks for Reply.

I read the link as you mentioned above and follow the steps.

In my wdf1007.log file, the following error message displayed.
************************************************************************************************************
0.047:
================================================================================
0.047: 2008/08/29 12:24:25.250 (local)
0.047: f:\16c06cbf342c200edf87a8a8017806\update\update.exe (version
6.3.4.1)
0.078: Hotfix started with following command line: /quiet /o /ER
0.078: CheckSystem: GetCheckedFree
failed :STATUS_CHECKED_FREE_MISMATCH
0.078: DoInstallation: CheckSystem Failed: 0xf002
0.094: Wdf01007 Setup cannot update a checked (debug) system with a
free (retail) version of Wdf01007, or vice versa.
0.094: Update.exe extended error code = 0xf002

************************************************************************************************************

Here, I cant get clear idea about STATUS_CHECKED_FREE_MISMATCH error.

Can you explain this?

And also I changed the coinstaller version to 1.5 and and again load
it through devcon utility. Here the inf is accepted but finally it
shows yellow mark on device manager.

And also setupapi.log shows,

#-199 Executing "D:\TESTING\hidusbfx2\Install\devcon.exe" with command
line: devcon install hidusbfx2.inf "hidusbfx2"
#I060 Set selected driver.
#-019 Searching for hardware ID(s): hidusbfx2
#I022 Found "hidusbfx2" in d:\testing\hidusbfx2\install\hidusbfx2.inf;
Device: "KMDF HID Minidriver for OSR USB-FX2 Device"; Driver: "KMDF
HID Minidriver for OSR USB-FX2 Device"; Provider: "Vendor Name"; Mfg:
"Vendor Name"; Section name: "hidusbfx2.Inst".
#I087 Driver node not trusted, rank changed from 0x00000000 to
0x00008000.
#I023 Actual install section: [hidusbfx2.Inst.NT]. Rank: 0x00008000.
Effective driver date: 08/29/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [hidusbfx2.Inst] in "d:
\testing\hidusbfx2\install\hidusbfx2.inf".
#I320 Class GUID of device remains: {745A17A0-74D3-11D0-
B6FE-00A0C90F57DA}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ROOT\HIDCLASS\0000".
#E366 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn, user said ok).
Error 0xe000022f: The third-party INF does not contain digital
signature information.
#-024 Copying file "d:\testing\hidusbfx2\install\hidusbfx2.sys" to "C:
\WINDOWS\system32\DRIVERS\hidusbfx2.sys".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
The third-party INF does not contain digital signature information.
#-336 Copying file "d:\testing\hidusbfx2\install\hidkmdf.sys" to "C:
\WINDOWS\system32\DRIVERS\hidkmdf.sys" via temporary file "C:\WINDOWS
\system32\DRIVERS\SET5C.tmp".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
The third-party INF does not contain digital signature information.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [hidusbfx2.Inst.NT.Interfaces] from "d:
\testing\hidusbfx2\install\hidusbfx2.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\HIDCLASS\0000".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn). Error 0xe000022f:
The third-party INF does not contain digital signature information.
#I163 Device not started: Device has problem: 0x25:
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.


==================================

and also I cant clear idea about "CM_PROB_FAILED_DRIVER_ENTRY"?

Thanks in Advance.

Regards - Dsrking.
Doron Holan [MSFT]
2008-08-30 03:49:38 UTC
Permalink
STATUS_CHECKED_FREE_MISMATCH means you are either trying to
a) install a chk coinstaller on a fre install
b) isntall a fre coinstaller on a chk build

what build are you running on?

d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi Doron,
Thanks for Reply.
I read the link as you mentioned above and follow the steps.
In my wdf1007.log file, the following error message displayed.
************************************************************************************************************
================================================================================
0.047: 2008/08/29 12:24:25.250 (local)
0.047: f:\16c06cbf342c200edf87a8a8017806\update\update.exe (version
6.3.4.1)
0.078: Hotfix started with following command line: /quiet /o /ER
0.078: CheckSystem: GetCheckedFree
failed :STATUS_CHECKED_FREE_MISMATCH
0.078: DoInstallation: CheckSystem Failed: 0xf002
0.094: Wdf01007 Setup cannot update a checked (debug) system with a
free (retail) version of Wdf01007, or vice versa.
0.094: Update.exe extended error code = 0xf002
************************************************************************************************************
Here, I cant get clear idea about STATUS_CHECKED_FREE_MISMATCH error.
Can you explain this?
And also I changed the coinstaller version to 1.5 and and again load
it through devcon utility. Here the inf is accepted but finally it
shows yellow mark on device manager.
And also setupapi.log shows,
#-199 Executing "D:\TESTING\hidusbfx2\Install\devcon.exe" with command
line: devcon install hidusbfx2.inf "hidusbfx2"
#I060 Set selected driver.
#-019 Searching for hardware ID(s): hidusbfx2
#I022 Found "hidusbfx2" in d:\testing\hidusbfx2\install\hidusbfx2.inf;
Device: "KMDF HID Minidriver for OSR USB-FX2 Device"; Driver: "KMDF
"Vendor Name"; Section name: "hidusbfx2.Inst".
#I087 Driver node not trusted, rank changed from 0x00000000 to
0x00008000.
#I023 Actual install section: [hidusbfx2.Inst.NT]. Rank: 0x00008000.
Effective driver date: 08/29/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
\testing\hidusbfx2\install\hidusbfx2.inf".
#I320 Class GUID of device remains: {745A17A0-74D3-11D0-
B6FE-00A0C90F57DA}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ROOT\HIDCLASS\0000".
#E366 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
OSR USB-FX2 Device" will be installed (Policy=Warn, user said ok).
Error 0xe000022f: The third-party INF does not contain digital
signature information.
\WINDOWS\system32\DRIVERS\hidusbfx2.sys".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
The third-party INF does not contain digital signature information.
\WINDOWS\system32\DRIVERS\hidkmdf.sys" via temporary file "C:\WINDOWS
\system32\DRIVERS\SET5C.tmp".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
The third-party INF does not contain digital signature information.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
\testing\hidusbfx2\install\hidusbfx2.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\HIDCLASS\0000".
#E362 An unsigned or incorrectly signed file "d:\testing
\hidusbfx2\install\hidusbfx2.inf" for driver "KMDF HID Minidriver for
The third-party INF does not contain digital signature information.
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.
==================================
and also I cant clear idea about "CM_PROB_FAILED_DRIVER_ENTRY"?
Thanks in Advance.
Regards - Dsrking.
d***@gmail.com
2008-09-01 13:05:37 UTC
Permalink
Hi Doron,

Thanks for Reply,

ya fine . I corrected the "STATUS_CHECKED_FREE_MISMATCH" error as u
explained above. Now After loading sys file , it shows Error code 10
and the setupapi.log file shows as follows,
==================================================
The third-party INF does not contain digital signature information.
#I163 Device not started: Device has problem: 0x25:
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.
===================================================

I cant clear the "CM_PROB_FAILED_DRIVER_ENTRY" error.

Is any solution for this?

Thanks in Advance.

Regards - Dsrking.
Doron Holan [MSFT]
2008-09-01 16:53:54 UTC
Permalink
try disabling/enabling the device in device manager to try to reload the
driver. before you do this, break into windbg and set an unresolved
breakpoint to your driver's DriverEntry

bu <yourdriver>!DriverEntry

and see if it gets hit

d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi Doron,
Thanks for Reply,
ya fine . I corrected the "STATUS_CHECKED_FREE_MISMATCH" error as u
explained above. Now After loading sys file , it shows Error code 10
and the setupapi.log file shows as follows,
==================================================
The third-party INF does not contain digital signature information.
CM_PROB_FAILED_DRIVER_ENTRY.
#I121 Device install of "ROOT\HIDCLASS\0000" finished successfully.
===================================================
I cant clear the "CM_PROB_FAILED_DRIVER_ENTRY" error.
Is any solution for this?
Thanks in Advance.
Regards - Dsrking.
d***@gmail.com
2008-09-02 10:03:57 UTC
Permalink
Hi Doron,

Thank you so much.

I loaded successfully hidusbfx2 as virtual one.

bu command is very useful for this kind of errors.

Is there any user manual for windbg commands?

Once again Thanks.

Warm Regards - Dsrking.
Pavel A.
2008-09-02 16:41:45 UTC
Permalink
Post by d***@gmail.com
Is there any user manual for windbg commands?
No, but windbg has a help file.
Print it out, if you like.

--PA
David Craig
2008-09-02 18:25:32 UTC
Permalink
Also the book "Advanced Windows Debugging" from Addison Wesley. It should
be considered for a read after some basic competency has been gained with
windbg.
Post by Pavel A.
Post by d***@gmail.com
Is there any user manual for windbg commands?
No, but windbg has a help file.
Print it out, if you like.
--PA
Doron Holan [MSFT]
2008-09-02 19:38:50 UTC
Permalink
in the same directory as kd.exe/windbg.exe will be a help file,
debugger.chm. you can get to this file by running the .hh command in either
kd or windbg. you can even have it navigate to the right topic by using .hh
<command>

d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi Doron,
Thank you so much.
I loaded successfully hidusbfx2 as virtual one.
bu command is very useful for this kind of errors.
Is there any user manual for windbg commands?
Once again Thanks.
Warm Regards - Dsrking.
d***@gmail.com
2008-09-04 06:26:27 UTC
Permalink
Hi

Thanks for Reply.

I got one more issue during uninstall the driver. i.e., Debugger shows
msg "*** ERROR: Module load completed but symbols could not be loaded
for hidkmdf.sys" when uninstall the driver.

In my driver, hidusbfx2.sys and hidkmdf.sys are there.

During uninstall, HidFx2EvtDeviceD0Exit is called successfully but
cleanup function is not called and it shows the above error msg.

I also set the breakpoint in cleanup function, but it is not found.

Thanks in Advance.

Regards - Dsrking.
Doron Holan [MSFT]
2008-09-04 17:42:43 UTC
Permalink
what is the status of the devnode after this failure ? in the debugger you
can use !devnode 0 1 hidkmdf to find it (or maybe hidusbfx2 if that is the
FDO for the stack)

d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi
Thanks for Reply.
I got one more issue during uninstall the driver. i.e., Debugger shows
msg "*** ERROR: Module load completed but symbols could not be loaded
for hidkmdf.sys" when uninstall the driver.
In my driver, hidusbfx2.sys and hidkmdf.sys are there.
During uninstall, HidFx2EvtDeviceD0Exit is called successfully but
cleanup function is not called and it shows the above error msg.
I also set the breakpoint in cleanup function, but it is not found.
Thanks in Advance.
Regards - Dsrking.
d***@gmail.com
2008-09-05 06:58:22 UTC
Permalink
Hi Doron,

I used the above command , but the result seems like below,

================================================
0: kd> !DEVNODE 0 1
Error retrieving address of IopRootDeviceNode
0: kd> !symfix
No downstream store given, using C:\Program Files\Debugging Tools for
Windows\sym
0: kd> !devnode 0 1 hidkmdf
Error retrieving address of IopRootDeviceNode
0: kd> .reload /f @"\SystemRoot\system32\DRIVERS\hidkmdf.sys"
*** ERROR: Module load completed but symbols could not be loaded for
hidkmdf.sys
0: kd> .reload /f @"\SystemRoot\system32\DRIVERS\hidusbfx2.sys"
*** ERROR: Module load completed but symbols could not be loaded for
hidusbfx2.sys
0: kd> g
HIDUSBFX2: HidFx2EvtDeviceD0Exit Exit
==============================================================
This error msg will appear.
"Error retrieving address of IopRootDeviceNode".

I also used "!symfix" command but there is no sym path.

I tried to copy the .pdb file into that path , but again the result is
same.

Regards - Dsrking.
Doron Holan [MSFT]
2008-09-05 21:20:08 UTC
Permalink
you NToskrnl symbols are wrong. almost nothing will work until you get them
fixed
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi Doron,
I used the above command , but the result seems like below,
================================================
0: kd> !DEVNODE 0 1
Error retrieving address of IopRootDeviceNode
0: kd> !symfix
No downstream store given, using C:\Program Files\Debugging Tools for
Windows\sym
0: kd> !devnode 0 1 hidkmdf
Error retrieving address of IopRootDeviceNode
*** ERROR: Module load completed but symbols could not be loaded for
hidkmdf.sys
*** ERROR: Module load completed but symbols could not be loaded for
hidusbfx2.sys
0: kd> g
HIDUSBFX2: HidFx2EvtDeviceD0Exit Exit
==============================================================
This error msg will appear.
"Error retrieving address of IopRootDeviceNode".
I also used "!symfix" command but there is no sym path.
I tried to copy the .pdb file into that path , but again the result is
same.
Regards - Dsrking.
d***@gmail.com
2008-09-08 06:45:32 UTC
Permalink
Hi Doron,

I also try to load the Ntoskrnl symbols but it loads default
ntkrpamp.pdb symbols.

I follow the step described in windbg help document to load symbols as
follows,

(1) Create DebugSymbols folder in D:
(2) Set symbol path in command window by, ".sympath SRV*d:
\DebugSymbols*http://msdl.microsoft.com/download/symbols" and also "!
sym noisy" & "!lmi nt".

But it loads only ntkrpamp symbols only (by default).

Is this procedure correct to load ntoskrnl symbols?

Regards - Dsrking.
Doron Holan [MSFT]
2008-09-08 17:09:15 UTC
Permalink
that may be the right symbols. ntoskrnl.exe will always be the kernel
name,b ut the original binary name can be different based off of OS
featuers compiled into it

d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
Post by d***@gmail.com
Hi Doron,
I also try to load the Ntoskrnl symbols but it loads default
ntkrpamp.pdb symbols.
I follow the step described in windbg help document to load symbols as
follows,
\DebugSymbols*http://msdl.microsoft.com/download/symbols" and also "!
sym noisy" & "!lmi nt".
But it loads only ntkrpamp symbols only (by default).
Is this procedure correct to load ntoskrnl symbols?
Regards - Dsrking.
d***@gmail.com
2008-09-09 12:57:15 UTC
Permalink
Hi Doron,

I think my steps is correct.

But why the above error msg displayed, "Error retrieving address of
IopRootDeviceNode" while I use "0: kd> !DEVNODE 0 1 " command.

Thanks in Advance,

Regards - Dsrking.

Continue reading on narkive:
Loading...