correct use of usbser.sys - Chkinf error test

NTDEV
1

Hi:

Does anybody know which is the right way to use usbser.sys as a service in the inf,
or what could be the problem?

I have this error in the “Chkinf test”:
ERROR: (E22.1.1110) File “usbser.sys” is not listed in the [SourceDisksFiles]

[Version]
Signature=“$Windows NT$”
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MANUFACTURER%
LayoutFile=layout.inf
CatalogFile=CDC_DEVICE.cat

DriverVer= 09/11/2010,5.1.0

[Manufacturer]
%MANUFACTURER%=DeviceList,ntx86,ntamd64,ntamd64.6.0

[DestinationDirs]
DefaultDestDir=12
MyDevice_CoInstaller_CopyFiles = 11

[Driver64WV.ntamd64]
include=mdmcpq.inf
CopyFiles=DriverCopyFilesWV.ntamd64

[DriverCopyFilesWV.ntamd64]
usbser.sys,0x20
low_usbV.sys
upp_usbV.sys

[Driver64WV.ntamd64.HW]
AddReg=Driver64WV.ntamd64.AddReg

[Driver64WV.ntamd64.CoInstallers]
AddReg=MyDevice_CoInstaller_AddReg
CopyFiles=MyDevice_CoInstaller_CopyFiles

[Driver64WV.ntamd64.Wdf]
KmdfService = %DRIVERFILENAME%, MyDevice_wdfsect

[Driver64WV.ntamd64.AddReg]
HKR,DevLoader,*ntkern
HKR,NTMPDriver,%DRIVERFILENAME%.sys
HKR,EnumPropPages32,“MsPorts.dll,SerialPortPropPageProvider”
HKR,“LowerFilters”,0x00010008,“low_usb”
HKR,“UpperFilters”,0x00010008,“upp_usb”

[Driver64WV.ntamd64.Services]
AddService=%DRIVERFILENAME%, 0x00000002, DriverService64WV.ntamd64
AddService = low_usb, , lowfilt_Service_InstWV
AddService = upp_usb, , uppfilt_Service_InstWV

[DriverService64WV.ntamd64]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%%DRIVERFILENAME%.sys

[lowfilt_Service_InstWV]
DisplayName = “Lower Class Filter Driver for FSL”
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\low_usbV.sys

[uppfilt_Service_InstWV]
DisplayName = “Upper Class Filter Driver for FSL”
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\upp_usbV.sys

[MyDevice_CoInstaller_AddReg]
HKR,CoInstallers32,0x00010000, “WdfCoInstaller01009.dll,WdfCoInstaller”

[MyDevice_CoInstaller_CopyFiles]
WdfCoInstaller01009.dll

[MyDevice_wdfsect]
KmdfLibraryVersion = 1.9

[Strings]

FILENAME=“CDC”
DRIVERFILENAME =“usbser”
MANUFACTURER=“Manufacturer”
INSTDISK=“USB2UART”
DESCRIPTION=“CDC Device”
SERVICE=“Virtual Com Driver”
SOURCE_DESCRIPTION=“CDC driver”

Thanks.

2

xxxxx@hotmail.com wrote:

Does anybody know which is the right way to use usbser.sys as a service in the inf,
or what could be the problem?

Did you do any Googling at all? There a knowledge base article about this:
http://support.microsoft.com/kb/837637

You can’t load usbser.sys, because you don’t control it’s location, just
as it said. You need to do is use the Include/Needs directives to pull
parts of the standard INF files into yours.

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

3

Thanks:

I checked the article and i made those changes as next:

[Driver32.ntx86]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.ntx86

[DriverCopyFiles.ntx86]
low_usb.sys
upp_usb.sys

[Driver32.ntx86.HW]
include=mdmcpq.inf
AddReg=Driver32.ntx86.AddReg

[Driver32.ntx86.Services]
include=mdmcpq.inf
AddService=%DRIVERFILENAME%, 0x00000002, DriverService32.ntx86
AddService = low_usb, , lowfilt_Service_Inst
AddService = upp_usb, , uppfilt_Service_Inst

[DriverService32.ntx86]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%%DRIVERFILENAME%.sys

[Strings]

DRIVERFILENAME =“usbser”

but i got this error in setup api:

dvi: {Install DEVICE}
inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\fsl_usb_pid.inf_amd64_neutral_c653f3e43e11a2c4\fsl_usb_pid.inf’ ([strings])
inf: Opened PNF: ‘C:\Windows\INF\mdmcpq.inf’ ([strings])
dvi: Processing Registry/Property directives…
inf: {Install Inf Section [Driver64WV.NTAMD64]}
inf: {Install Inf Section [Driver64WV.NTAMD64] exit (0x00000000)}
inf: {Install Inf Section [Driver64WV.NTAMD64.Hw]}
inf: AddReg=Driver64WV.ntamd64.AddReg (fsl_usb_pid.inf line 83)
inf: {Install Inf Section [Driver64WV.NTAMD64.Hw] exit (0x00000000)}
dvi: {Writing Device Properties}
dvi: Provider name=Freescale Semiconductor Inc
dvi: DriverDate 09/11/2010
dvi: DriverVersion=5.1.0.0
dvi: Class name=Ports
dvi: Manufacturer=Freescale Semiconductor Inc
dvi: Matching DeviceID=usb\vid_15a2&pid_005a&usb2ser
dvi: Strong Name=oem2.inf:DeviceList.ntamd64.6.0:Driver64WV:5.1.0.0:usb\vid_15a2&pid_005a&usb2ser
dvi: {Writing Device Properties - Complete}
inf: {Install Inf Section [Driver64WV.NTAMD64.Services]}
inf: AddService=usbser,0x00000002,DriverService64WV.ntamd64 (fsl_usb_pid.inf line 101)
inf: ServiceType=1 (fsl_usb_pid.inf line 107)
inf: StartType=3 (fsl_usb_pid.inf line 108)
inf: ErrorControl=1 (fsl_usb_pid.inf line 109)
inf: ServiceBinary=C:\Windows\system32\DRIVERS\usbser.sys (fsl_usb_pid.inf line 110)
!!! dvi: Add Service: Binary ‘C:\Windows\system32\DRIVERS\usbser.sys’ for service ‘usbser’ is not present.
!!! inf: {Install Inf Section [Driver64WV.NTAMD64.Services] exit(0xe0000217)}
!!! inf: Error 0xe0000217: A service installation section in this INF is invalid.
!!! dvi: Error while installing services.
!!! dvi: Error 0xe0000217: A service installation section in this INF is invalid.
!!! dvi: Cleaning up failed installation
!!! dvi: Error 0xe0000217: A service installation section in this INF is invalid.
dvi: {Install DEVICE exit (0xe0000217)}
!!! dvi: Cleaning up failed installation (e0000217)
!!! dvi: Class installer: failed(0xe0000217)!
!!! dvi: Error 0xe0000217: A service installation section in this INF is invalid.
dvi: CoInstaller 1: Enter (Post Processing) 18:00:02.598
! dvi: CoInstaller 1: modified status 0x00000057! (Post Processing)
! dvi: Error 87: The parameter is incorrect.
dvi: {DIF_INSTALLDEVICE - exit(0x00000057)} 18:00:02.879
!!! ndv: Error(00000057) installing device!
ndv: Device install status=0x00000057
ndv: Performing device install final cleanup…
! ndv: Queueing up error report since device installation failed…
ndv: {Core Device Install - exit(0x00000057)} 18:00:02.879
dvi: {DIF_DESTROYPRIVATEDATA} 18:00:02.879
dvi: CoInstaller 1: Enter 18:00:02.879
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 18:00:02.879
dvi: Class installer: Exit
dvi: Default installer: Enter 18:00:02.895
dvi: Default installer: Exit

Is there something more in the “Need” section that is not described in the article that i have to add??

Thanks.

4

Sorry for my little experience!!, I could solve it with the document, i was making a mistake.

I appreciative your attention.