From: Kim Latt on 2 Feb 2010 14:54 My company and I have developed a usb device, which is suitable for the kind stuff that can be done using Winusb.sys. While implementing the code using winusb.sys and installing the drivers on vista x86 -> Win 7 x64 has been a simple task. Writing and understanding the requirements to an inf-file suitable for win xp installs has been pretty complicated, in fact so complicated, that I'm about to give up. I just followed the numerous examples in win ddk on how the inf file is to be written. The first time I realized that something was wrong, was whilst DTM'ing the driver for whql submission. My question is: What should be done to the inf-file below, to satisfy xp, chkinf and WLK? ; ================== Class section ================== [ClassInstall32] Addreg=DeviceClassReg [DeviceClassReg] HKR,,,0,%ClassName% HKR,,Icon,,-1 ; ========== Manufacturer/Models sections =========== [Manufacturer] %ProviderName% = MyDev,NTx86,NTamd64 [MyDev] %USB\MyDev.DeviceDesc%=USB_Install, USB\VID_xxxx&PID_xxxx ; VID/PID removed [MyDev.NTx86] %USB\MyDev.DeviceDesc% =USB_Install, USB\VID_xxxx&PID_xxxx; VID/PID removed [MyDev.NTamd64] %USB\MyDev.DeviceDesc% =USB_Install, USB\VID_xxxx&PID_xxxx; VID/PID removed [USB_Install] Include=winusb.inf Needs=WINUSB.NT [USB_Install.Services] Include=winusb.inf AddService=WinUSB,0x00000002,WinUSB_ServiceInstall [WinUSB_ServiceInstall] DisplayName = %SvcDesc% ServiceType = 1 StartType = 3 ErrorControl = 1 ServiceBinary = %12%\WinUSB.sys [USB_Install.Wdf] KmdfService=WINUSB, WinUsb_Install [WinUSB_Install] KmdfLibraryVersion=1.9 [USB_Install.HW] AddReg=Dev_AddReg [Dev_AddReg] HKR,,DeviceInterfaceGUIDs,0x10000,"{366a8df7-c36a-4cfc-883f-26e291b571ad}" [USB_Install.CoInstallers] AddReg=CoInstallers_AddReg CopyFiles=CoInstallers_CopyFiles [CoInstallers_AddReg] HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll" [CoInstallers_CopyFiles] WinUSBCoInstaller2.dll WdfCoInstaller01009.dll [DestinationDirs] CoInstallers_CopyFiles=11 [SourceDisksNames] 1 = %DriversDisk%,,, [SourceDisksFiles.x86] WinUSBCoInstaller2.dll=1,i386 WdfCoInstaller01009.dll=1,i386 [SourceDisksFiles.amd64] WinUSBCoInstaller2.dll=1,amd64 WdfCoInstaller01009.dll=1,amd64
From: Tim Roberts on 3 Feb 2010 01:07 "Kim Latt" <kim(a)latt.dk> wrote: > >My company and I have developed a usb device, which is suitable for the kind >stuff that can be done using Winusb.sys. > >While implementing the code using winusb.sys and installing the drivers on >vista x86 -> Win 7 x64 has been a simple task. >Writing and understanding the requirements to an inf-file suitable for win >xp installs has been pretty complicated, in fact >so complicated, that I'm about to give up. > >I just followed the numerous examples in win ddk on how the inf file is to >be written. >The first time I realized that something was wrong, was whilst DTM'ing the >driver for whql submission. > >My question is: What should be done to the inf-file below, to satisfy xp, >chkinf and WLK? You cannot make a WinUSB-based INF file that passes chkinf for XP. To use WinUSB, you have to needs/include WinUSB.INF, and in XP that's not a standard INF file. I believe there is a DTM exception for this. You should contact WHQL about it. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: Kim Latt on 3 Feb 2010 02:15 This is what I have realized - But there aren't any exceptions in the filters for this. I have a hack that seems to fix it, but I dare not submit it to whql: Simply put a "dummy" winusb.inf into the windows\inf directory on the xp-machine and rerun the test. I've read Peter Wielands blog on the subject. An tried doing another inf-file that navigate "run-time" to another section of the inf-file for xp and fixes the coInstaller issues with the DDK samples. (http://blogs.msdn.com/peterwie/archive/2007/01/10/fixing-the-umdf-usb-samples-to-install-both-on-xp-vista.aspx) But the check that chkinf does is static or rather it tries all "Install-paths" and not just the one for xp. Anybody else in here who has a solution? Or nows howto persuade whql to ignore the chkinf problem?! Rgdz "Tim Roberts" <timr(a)probo.com> wrote in message news:5i4im55ecip0cmtot9v152ml4uq08e7d85(a)4ax.com... > "Kim Latt" <kim(a)latt.dk> wrote: >> >>My company and I have developed a usb device, which is suitable for the >>kind >>stuff that can be done using Winusb.sys. >> >>While implementing the code using winusb.sys and installing the drivers on >>vista x86 -> Win 7 x64 has been a simple task. >>Writing and understanding the requirements to an inf-file suitable for win >>xp installs has been pretty complicated, in fact >>so complicated, that I'm about to give up. >> >>I just followed the numerous examples in win ddk on how the inf file is to >>be written. >>The first time I realized that something was wrong, was whilst DTM'ing the >>driver for whql submission. >> >>My question is: What should be done to the inf-file below, to satisfy xp, >>chkinf and WLK? > > You cannot make a WinUSB-based INF file that passes chkinf for XP. To use > WinUSB, you have to needs/include WinUSB.INF, and in XP that's not a > standard INF file. > > I believe there is a DTM exception for this. You should contact WHQL > about > it. > -- > Tim Roberts, timr(a)probo.com > Providenza & Boekelheide, Inc.
From: Kim Latt on 7 Feb 2010 04:00 I'm happy to inform the group, that the exception is back in the DTM filters. Now WLK 1.5 allows winusb to be used in xp drivers Rgdz "Kim Latt" <kim(a)latt.dk> wrote in message news:A1CE8AB7-F0B6-4812-A440-84691C9F40FB(a)microsoft.com... > This is what I have realized - But there aren't any exceptions in the > filters for this. > > I have a hack that seems to fix it, but I dare not submit it to whql: > > Simply put a "dummy" winusb.inf into the windows\inf directory on the > xp-machine and rerun > the test. > > I've read Peter Wielands blog on the subject. An tried doing another > inf-file that navigate "run-time" to another > section of the inf-file for xp and fixes the coInstaller issues with the > DDK samples. > (http://blogs.msdn.com/peterwie/archive/2007/01/10/fixing-the-umdf-usb-samples-to-install-both-on-xp-vista.aspx) > > But the check that chkinf does is static or rather it tries all > "Install-paths" and not just the one for xp. > > Anybody else in here who has a solution? Or nows howto persuade whql to > ignore the chkinf problem?! > > Rgdz > > "Tim Roberts" <timr(a)probo.com> wrote in message > news:5i4im55ecip0cmtot9v152ml4uq08e7d85(a)4ax.com... >> "Kim Latt" <kim(a)latt.dk> wrote: >>> >>>My company and I have developed a usb device, which is suitable for the >>>kind >>>stuff that can be done using Winusb.sys. >>> >>>While implementing the code using winusb.sys and installing the drivers >>>on >>>vista x86 -> Win 7 x64 has been a simple task. >>>Writing and understanding the requirements to an inf-file suitable for >>>win >>>xp installs has been pretty complicated, in fact >>>so complicated, that I'm about to give up. >>> >>>I just followed the numerous examples in win ddk on how the inf file is >>>to >>>be written. >>>The first time I realized that something was wrong, was whilst DTM'ing >>>the >>>driver for whql submission. >>> >>>My question is: What should be done to the inf-file below, to satisfy xp, >>>chkinf and WLK? >> >> You cannot make a WinUSB-based INF file that passes chkinf for XP. To >> use >> WinUSB, you have to needs/include WinUSB.INF, and in XP that's not a >> standard INF file. >> >> I believe there is a DTM exception for this. You should contact WHQL >> about >> it. >> -- >> Tim Roberts, timr(a)probo.com >> Providenza & Boekelheide, Inc. >
|
Pages: 1 Prev: How to trigger copy of usbser.sys from CAB Next: cursor position |