Problem installing Sealevel driver

NTDEV
1

I am having problem with the Sealevel board. I have recently received it, and am using it to come up to speed with WDF code.

This is what I have done.

  1. Downloaded and installed WDF v1.7 from Microsoft.
  2. Downloaded the WDF package for the board from OSR.
  3. For debugging purposes, I put a call to DbgBreakPoint() at the beginning of the DriverEntry function.
  4. Built the driver with the command “build -cZ”, Windows XP checked environment (I’ve also tried a free build)
  5. I modified the supplied INF file as follows:
  6. Commented out the catalog file entry.
  7. Modified all instances of WdfCoinstaller01000 with WdfCoinstaller01007
  8. Set KmdfLibraryVersion = 1.7

I then moved the package containing WdfDio.sys, wdfDio.inf, and WdfCoinstaller01007.dll to my target machine running XP Home, fully updated (SP3, all current security updates).

I powered down, installed the hardware, and powered up with the kernel debugger attached. The PnP manager detected the board, but all attempts at installing the driver has failed (CM_PROB_DRIVER_FAILED_LOAD). The breakpoint in DriverEntry() is never hit.

I have gone through Chapter 20, How to Install WDF drivers, Developing Drivers with the Windows Driver Foundation. The major abnormality to me is that neither of the WDF drivers Wdfldr.sys, WdfMM000.sys) are resident in in %Windir%\System32\Drivers. WdfDio.sys is in place.

I’m sure I’ve overlooked something simple, but would appreciate a hint as to what it could be. To me it appears to be coinstaller related, but I can’t figure it out. The relevant portions of setupapi.log is below.

#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in C:\WINDOWS\inf\oem12.inf; Device: “OSR WDF DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to 0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective driver date: 04/17/2007.
#-019 Searching for hardware ID(s): pci\ven_135e&dev_8018&subsys_8018135e&rev_01,pci\ven_135e&dev_8018&subsys_8018135e,pci\ven_135e&dev_8018&cc_070002,pci\ven_135e&dev_8018&cc_0700
#-018 Searching for compatible ID(s): pci\ven_135e&dev_8018&rev_01,pci\ven_135e&dev_8018,pci\ven_135e&cc_070002,pci\ven_135e&cc_0700,pci\ven_135e,pci\cc_070002,pci\cc_0700
#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in d:\development\dio2431\objchk_wxp_x86\i386\wdfDio.inf; Device: “OSR WDF DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to 0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective driver date: 04/17/2007.
#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in d:\development\dio2431\objchk_wxp_x86\i386\wdfDio.inf; Device: “OSR WDF DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to 0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective driver date: 04/17/2007.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [WdfDio] in “c:\windows\inf\oem9.inf”.
#I320 Class GUID of device remains: {CFB15040-5BC7-11D3-B194-0060B0EFD4AA}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I063 Selected driver installs from section [WdfDio] in “c:\windows\inf\oem12.inf”.
#I320 Class GUID of device remains: {CFB15040-5BC7-11D3-B194-0060B0EFD4AA}.
#I060 Set selected driver.
#-124 Doing copy-only install of “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0”.
#W334 Failed to verify catalog when scanning file queue. Error 1168: Element not found.
#E360 An unsigned or incorrectly signed file “c:\windows\inf\oem12.inf” for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore). Error 1168: Element not found.
#W187 Install failed, attempting to restore original files.
#E360 An unsigned or incorrectly signed file “c:\windows\inf\oem12.inf” for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore). Error 1168: Element not found.
#-024 Copying file “d:\development\dio2431\objchk_wxp_x86\i386\WdfDio.sys” to “C:\WINDOWS\system32\DRIVERS\WdfDio.sys”.
#E360 An unsigned or incorrectly signed file “d:\development\dio2431\objchk_wxp_x86\i386\WdfDio.sys” for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore). Error 1168: Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [WdfDio.Interfaces] from “c:\windows\inf\oem12.inf”.
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0”.
#I163 Device not started: Device has problem: 0x27: CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0” finished successfully.

Thanks for any help.

2

I had similar problem like you couple days ago. Someone here helped me.

Can you look at the file %windir%\setupapi.log? In Windows
XP/2000/2003 this is the log file, where installation successes and
failures (+their reasons) are logged.

Hope this could help you to solved problem.

Bob Bao

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Thursday, October 09, 2008 3:42 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Problem installing Sealevel driver

I am having problem with the Sealevel board. I have recently received
it, and am using it to come up to speed with WDF code.

This is what I have done.

  1. Downloaded and installed WDF v1.7 from Microsoft.
  2. Downloaded the WDF package for the board from OSR.
  3. For debugging purposes, I put a call to DbgBreakPoint() at the
    beginning of the DriverEntry function.
  4. Built the driver with the command “build -cZ”, Windows XP checked
    environment (I’ve also tried a free build)
  5. I modified the supplied INF file as follows:
  6. Commented out the catalog file entry.
  7. Modified all instances of WdfCoinstaller01000 with
    WdfCoinstaller01007
  8. Set KmdfLibraryVersion = 1.7

I then moved the package containing WdfDio.sys, wdfDio.inf, and
WdfCoinstaller01007.dll to my target machine running XP Home, fully
updated (SP3, all current security updates).

I powered down, installed the hardware, and powered up with the kernel
debugger attached. The PnP manager detected the board, but all attempts
at installing the driver has failed (CM_PROB_DRIVER_FAILED_LOAD). The
breakpoint in DriverEntry() is never hit.

I have gone through Chapter 20, How to Install WDF drivers, Developing
Drivers with the Windows Driver Foundation. The major abnormality to me
is that neither of the WDF drivers Wdfldr.sys, WdfMM000.sys) are
resident in in %Windir%\System32\Drivers. WdfDio.sys is in place.

I’m sure I’ve overlooked something simple, but would appreciate a hint
as to what it could be. To me it appears to be coinstaller related, but
I can’t figure it out. The relevant portions of setupapi.log is below.

#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in
C:\WINDOWS\inf\oem12.inf; Device: “OSR WDF DIO Driver V2.0”; Driver:
“OSR WDF DIO Driver V2.0”; Provider: “OSR Open Systems Resources, Inc.”;
Mfg: “Open Systems Resources, Inc.”; Section name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to
0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective
driver date: 04/17/2007.
#-019 Searching for hardware ID(s):
pci\ven_135e&dev_8018&subsys_8018135e&rev_01,pci\ven_135e&dev_8018&subsy
s_8018135e,pci\ven_135e&dev_8018&cc_070002,pci\ven_135e&dev_8018&cc_0700
#-018 Searching for compatible ID(s):
pci\ven_135e&dev_8018&rev_01,pci\ven_135e&dev_8018,pci\ven_135e&cc_07000
2,pci\ven_135e&cc_0700,pci\ven_135e,pci\cc_070002,pci\cc_0700
#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in
d:\development\dio2431\objchk_wxp_x86\i386\wdfDio.inf; Device: “OSR WDF
DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open
Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section
name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to
0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective
driver date: 04/17/2007.
#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in
d:\development\dio2431\objchk_wxp_x86\i386\wdfDio.inf; Device: “OSR WDF
DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open
Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section
name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to
0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective
driver date: 04/17/2007.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [WdfDio] in
“c:\windows\inf\oem9.inf”.
#I320 Class GUID of device remains:
{CFB15040-5BC7-11D3-B194-0060B0EFD4AA}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I063 Selected driver installs from section [WdfDio] in
“c:\windows\inf\oem12.inf”.
#I320 Class GUID of device remains:
{CFB15040-5BC7-11D3-B194-0060B0EFD4AA}.
#I060 Set selected driver.
#-124 Doing copy-only install of
“PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0”.
#W334 Failed to verify catalog when scanning file queue. Error 1168:
Element not found.
#E360 An unsigned or incorrectly signed file “c:\windows\inf\oem12.inf”
for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore).
Error 1168: Element not found.
#W187 Install failed, attempting to restore original files.
#E360 An unsigned or incorrectly signed file “c:\windows\inf\oem12.inf”
for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore).
Error 1168: Element not found.
#-024 Copying file
“d:\development\dio2431\objchk_wxp_x86\i386\WdfDio.sys” to
“C:\WINDOWS\system32\DRIVERS\WdfDio.sys”.
#E360 An unsigned or incorrectly signed file
“d:\development\dio2431\objchk_wxp_x86\i386\WdfDio.sys” for driver “OSR
WDF DIO Driver V2.0” will be installed (Policy=Ignore). Error 1168:
Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [WdfDio.Interfaces] from
“c:\windows\inf\oem12.inf”.
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
“PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0”.
#I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of
“PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0”
finished successfully.

Thanks for any help.

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

3

You put the INF, SYS, and coinstaller in the same directory on your target machine (for example, C:\driver), and when the hardware wizard popped-up you pointed it to the INF/SYS in that directory??

Most common cause for error is not putting the coinstaller in the directory with the driver and INF.

Peter
OSR

4

From the output it appears that you don’t have the WDF 1.7 coinstaller setup for your device. Can you post your INF?

-p

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Thursday, October 09, 2008 1:42 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Problem installing Sealevel driver

I am having problem with the Sealevel board. I have recently received it, and am using it to come up to speed with WDF code.

This is what I have done.

  1. Downloaded and installed WDF v1.7 from Microsoft.
  2. Downloaded the WDF package for the board from OSR.
  3. For debugging purposes, I put a call to DbgBreakPoint() at the beginning of the DriverEntry function.
  4. Built the driver with the command “build -cZ”, Windows XP checked environment (I’ve also tried a free build)
  5. I modified the supplied INF file as follows:
  6. Commented out the catalog file entry.
  7. Modified all instances of WdfCoinstaller01000 with WdfCoinstaller01007
  8. Set KmdfLibraryVersion = 1.7

I then moved the package containing WdfDio.sys, wdfDio.inf, and WdfCoinstaller01007.dll to my target machine running XP Home, fully updated (SP3, all current security updates).

I powered down, installed the hardware, and powered up with the kernel debugger attached. The PnP manager detected the board, but all attempts at installing the driver has failed (CM_PROB_DRIVER_FAILED_LOAD). The breakpoint in DriverEntry() is never hit.

I have gone through Chapter 20, How to Install WDF drivers, Developing Drivers with the Windows Driver Foundation. The major abnormality to me is that neither of the WDF drivers Wdfldr.sys, WdfMM000.sys) are resident in in %Windir%\System32\Drivers. WdfDio.sys is in place.

I’m sure I’ve overlooked something simple, but would appreciate a hint as to what it could be. To me it appears to be coinstaller related, but I can’t figure it out. The relevant portions of setupapi.log is below.

#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in C:\WINDOWS\inf\oem12.inf; Device: “OSR WDF DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to 0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective driver date: 04/17/2007.
#-019 Searching for hardware ID(s): pci\ven_135e&dev_8018&subsys_8018135e&rev_01,pci\ven_135e&dev_8018&subsys_8018135e,pci\ven_135e&dev_8018&cc_070002,pci\ven_135e&dev_8018&cc_0700
#-018 Searching for compatible ID(s): pci\ven_135e&dev_8018&rev_01,pci\ven_135e&dev_8018,pci\ven_135e&cc_070002,pci\ven_135e&cc_0700,pci\ven_135e,pci\cc_070002,pci\cc_0700
#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in d:\development\dio2431\objchk_wxp_x86\i386\wdfDio.inf; Device: “OSR WDF DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to 0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective driver date: 04/17/2007.
#I022 Found “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01” in d:\development\dio2431\objchk_wxp_x86\i386\wdfDio.inf; Device: “OSR WDF DIO Driver V2.0”; Driver: “OSR WDF DIO Driver V2.0”; Provider: “OSR Open Systems Resources, Inc.”; Mfg: “Open Systems Resources, Inc.”; Section name: “WdfDio”.
#I087 Driver node not trusted, rank changed from 0x00000000 to 0x0000c000.
#I023 Actual install section: [WdfDio]. Rank: 0x0000c000. Effective driver date: 04/17/2007.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [WdfDio] in “c:\windows\inf\oem9.inf”.
#I320 Class GUID of device remains: {CFB15040-5BC7-11D3-B194-0060B0EFD4AA}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I063 Selected driver installs from section [WdfDio] in “c:\windows\inf\oem12.inf”.
#I320 Class GUID of device remains: {CFB15040-5BC7-11D3-B194-0060B0EFD4AA}.
#I060 Set selected driver.
#-124 Doing copy-only install of “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0”.
#W334 Failed to verify catalog when scanning file queue. Error 1168: Element not found.
#E360 An unsigned or incorrectly signed file “c:\windows\inf\oem12.inf” for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore). Error 1168: Element not found.
#W187 Install failed, attempting to restore original files.
#E360 An unsigned or incorrectly signed file “c:\windows\inf\oem12.inf” for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore). Error 1168: Element not found.
#-024 Copying file “d:\development\dio2431\objchk_wxp_x86\i386\WdfDio.sys” to “C:\WINDOWS\system32\DRIVERS\WdfDio.sys”.
#E360 An unsigned or incorrectly signed file “d:\development\dio2431\objchk_wxp_x86\i386\WdfDio.sys” for driver “OSR WDF DIO Driver V2.0” will be installed (Policy=Ignore). Error 1168: Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [WdfDio.Interfaces] from “c:\windows\inf\oem12.inf”.
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0”.
#I163 Device not started: Device has problem: 0x27: CM_PROB_DRIVER_FAILED_LOAD.
#I121 Device install of “PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01\4&19FD8D60&0&38F0” finished successfully.

Thanks for any help.

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

5

Peter V., yes the sys, inf, and dll file are all located together in the same directory. The setupapi.log implies that it found the co-installer.

Bob, setupapi.log entries were included in the posting. It gave me no clue.

Peter W. following is the entire INF. It is as supplied and posted by OSR with the modifications I stated in my original post:

;
; *** INF file for WDFDIO.SYS
; OSR’s WDF sample driver for the Sealevel DIO-24 (8008) card.
;
; Instructions:
; Stick this file in a directory with the .sys file, and install. It
; should work with either the AMD64 version or the x64 version of the driver.
; If you want an IA64 version of the driver, you’re on your own.
;
[Version]
Signature=“$WINDOWS NT$”
Class=OsrHardware
ClassGuid={cfb15040-5bc7-11d3-b194-0060b0efd4aa}
Provider=“OSR Open Systems Resources, Inc.”
DriverVer=04/17/2007,2.0.0
;;;catalogfile=wdfdio.cat

[SourceDisksNames]
1=%DiskId%

[SourceDisksFiles]
wdfdio.sys=1

[ClassInstall32]
Addreg=OsrHwClass

[OsrHwClass]
HKR,%ClassName%
HKR,Icon,“-5”

[DestinationDirs]
DefaultDestDir=12

[Manufacturer]
%Mfg%=MfgDeviceSection, NTAMD64
%Mfg%=MfgDeviceSection

[MfgDeviceSection]
%DeviceDesc% = WdfDio, PCI\VEN_135E&DEV_8008&SUBSYS_8008135E&REV_01
%DeviceDesc% = WdfDio, PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01

[MfgDeviceSection.NTAMD64]
%DeviceDesc% = WdfDio, PCI\VEN_135E&DEV_8008&SUBSYS_8008135E&REV_01
%DeviceDesc% = WdfDio, PCI\VEN_135E&DEV_8018&SUBSYS_8018135E&REV_01

[WdfDio]
CopyFiles=@WdfDio.sys

[WdfDio.Services]
AddService = WdfDio,%SPSVCINST_ASSOCSERVICE%,wdfDio_Service_Inst

[WdfDio_Service_Inst]
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_MANUAL_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\wdfdio.sys

;-------------- WDF Coinstaller installation

[DestinationDirs]
CoInstaller_CopyFiles = 11

[WdfDio.NT.CoInstallers]
AddReg=CoInstaller_AddReg
CopyFiles=CoInstaller_CopyFiles

[CoInstaller_CopyFiles]
WdfCoinstaller01007.dll

[SourceDisksFiles]
WdfCoinstaller01007.dll=1 ; make sure the number matches with SourceDisksNames

[CoInstaller_AddReg]
HKR,CoInstallers32,0x00010000, “WdfCoinstaller01007.dll,WdfCoInstaller”

[WdfDio.Wdf]
KmdfService = WdfDio, WdfDio_wdfsect
[WdfDio_wdfsect]
KmdfLibraryVersion = 1.7

;---------------------------------------------------------------;

[Strings]
ClassName =“OSR Sample Hardware Drivers”
DeviceDesc = “OSR WDF DIO Driver V2.0”
DiskId = “Install disk (1)”
Mfg = “Open Systems Resources, Inc.”
SPSVCINST_ASSOCSERVICE = 0x00000002
SERVICE_KERNEL_DRIVER = 1
SERVICE_MANUAL_START = 3
SERVICE_ERROR_NORMAL = 1

6

Hmmmm… I totally don’t see the problem.

This looks like a good INF to me.

Did you have to hack around with the INF file? Perhaps the new version of it isn’t being read? In this case you could change

DriverVer=04/17/2007,2.0.0

to something like:

DriverVer=10/09/2008,2.5.0

Maybe PeterWei will see something I don’t. I’m generally not very good at these INF problems.

Peter
OSR

7

ChkInf came up with a couple of things, but I don’t think they are the problem since it doesn’t do a very good job with WDF infs.

Errors:
Line 10: (E22.1.1081) Directive: CatalogFile required (and must not be blank) in section [Version] for WHQL digital signature.
Line 36: (E22.1.1317) Manufacturer-identifier is not unique in the [Manufacturer] section

Warnings:
Line 0: (W22.1.9998) NOTE: The ChkInf tool does not verify the WDF sections and directives of the INF file.
Line 0: (W22.1.2212) No Copyright information found.
Line 12: (W22.1.2215) Class OsrHardware (ClassGUID {cfb15040-5bc7-11d3-b194-0060b0efd4aa}) is unrecognized.
Line 63: (W22.1.2083) Section [WDFDIO.NT.COINSTALLERS] not referenced
Line 67: (W22.1.2083) Section [COINSTALLER_COPYFILES] not referenced
Line 73: (W22.1.2083) Section [COINSTALLER_ADDREG] not referenced
Line 76: (W22.1.2083) Section [WDFDIO.WDF] not referenced
Line 78: (W22.1.2083) Section [WDFDIO_WDFSECT] not referenced

8

xxxxx@gmail.com wrote:

I am having problem with the Sealevel board. I have recently received it, and am using it to come up to speed with WDF code.

This is what I have done.

  1. Downloaded and installed WDF v1.7 from Microsoft.
  2. Downloaded the WDF package for the board from OSR.
  3. For debugging purposes, I put a call to DbgBreakPoint() at the beginning of the DriverEntry function.
  4. Built the driver with the command “build -cZ”, Windows XP checked environment (I’ve also tried a free build)
  5. I modified the supplied INF file as follows:
  6. Commented out the catalog file entry.
  7. Modified all instances of WdfCoinstaller01000 with WdfCoinstaller01007
  8. Set KmdfLibraryVersion = 1.7

I then moved the package containing WdfDio.sys, wdfDio.inf, and WdfCoinstaller01007.dll to my target machine running XP Home, fully updated (SP3, all current security updates).

The log says it got the INF and SYS file from
d:\development\dio2431\objchk_wxp_x86\i386. Is that actually the
location on the target machine? It looks suspiciously like your build
directory.

The log also says there was a match in oem9.inf and oem12.inf, which may
be left over from earlier tests. You might want to clean your old INF
files out of C:\windows\inf\oemXX.inf.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

9

… and change the date/rev on the DriverVer line when you try it again to ensure the new version of the INF gets picked up in place of the old one. Setup can cache and use the old one if they appear to be “the same” based on DriverVer.

Peter
OSR

10

The error on line 63 should worry you - your [WDFDio.NT.CoInstallers] section isn’t being referenced.

IIRC The .NT decoration has to match your DDInstall section’s name. Since your DDInstall section is [WdfDio] & not [WdfDio.NT] the [WdfDio.NT.Coinstallers] section may be ignored.

-p

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Thursday, October 09, 2008 3:05 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Problem installing Sealevel driver

ChkInf came up with a couple of things, but I don’t think they are the problem since it doesn’t do a very good job with WDF infs.

Errors:
Line 10: (E22.1.1081) Directive: CatalogFile required (and must not be blank) in section [Version] for WHQL digital signature.
Line 36: (E22.1.1317) Manufacturer-identifier is not unique in the [Manufacturer] section

Warnings:
Line 0: (W22.1.9998) NOTE: The ChkInf tool does not verify the WDF sections and directives of the INF file.
Line 0: (W22.1.2212) No Copyright information found.
Line 12: (W22.1.2215) Class OsrHardware (ClassGUID {cfb15040-5bc7-11d3-b194-0060b0efd4aa}) is unrecognized.
Line 63: (W22.1.2083) Section [WDFDIO.NT.COINSTALLERS] not referenced
Line 67: (W22.1.2083) Section [COINSTALLER_COPYFILES] not referenced
Line 73: (W22.1.2083) Section [COINSTALLER_ADDREG] not referenced
Line 76: (W22.1.2083) Section [WDFDIO.WDF] not referenced
Line 78: (W22.1.2083) Section [WDFDIO_WDFSECT] not referenced

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

11

OK. I have reimaged my OS to start over. And, I changed the Section [WDFDIO.NT.COINSTALLERS] to [WDFDIO.COINSTALLERS]. I have now successfully installed the driver. Now, I can play.

thanks all.

12

NICE FIND, Peter. Well done!

I guess we’ll need to update that sample, huh?? Yeah…

Sorry, Dale. At least you got it fixed!

Peter
OSR