Prev: problem with DbgPrint in storport miniport
Next: How to get 4K alignment DMA transfer for SCSI miniport and others.
From: Philip Ries [MSFT] on 16 Aug 2010 15:56
If WinUsb is failing start then you should take a trace across the
install to see where it is failing.

http://blogs.msdn.com/b/usbcoreblog/archive/2010/02/05/how-to-generate-and-view-a-winusb-debug-trace-log.aspx

mario_atallah wrote:
> I usually right-click on the device in "Device Manager" and use the "Update
> Driver Software" and browse to the inf file. But, also I have used Devcon.exe
> and still same result.
>
> "Doron Holan [MSFT]" wrote:
>
>> how did you apply the INF to the installed device? devcon (if so, what cmd
>> line?) or device manager?
>>
>> "mario_atallah" wrote in message
>> news:AF9CBE84-F34D-4C16-A75A-0ADECE389E13(a)microsoft.com...
>>
>> I am trying to use install a custom manufactured HID device on Windows 7
>> 64-bit using winusb.sys.
>>
>> The device installs perfectly using the windows supported HID driver
>> (hidclass.sys). However, I want to install the device using winusb.sys.
>>
>> I've created the driver package (including inf file, coinstallers for 32 and
>> 64-bit OS's, unsigned setup catalog file using inf2cat).
>>
>> The two main errors in setupapi.log are: "Verifying file against specific
>> (valid) catalog failed! (0x00000057) Error 87: The parameter is incorrect.
>> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}" and "Device not started: Device
>> has problem: 0x0a: CM_PROB_FAILED_START.".
>>
>> I can see the device in the device manager but it has the yellow exclamation
>> mark... The error is "The device cannot start (code 10)".
>>
>> Any idea what is going on wrong? Is it because I am trying to use winusb.sys
>> while hidclass.sys is already supported? or something else?
>>
>> .
>>
 | 
Pages: 1
Prev: problem with DbgPrint in storport miniport
Next: How to get 4K alignment DMA transfer for SCSI miniport and others.