Prev: Driver Verifier in a VM
Next: Debug version of Windows XP
From: Geoff on 4 May 2010 13:08
I have tried this question a couple of times now without a response.
Is this the right place to post this?
I thought Microsft engineers replied in "2 days"?

I am using the microsoft supplied usbser.sys driver for my product.

I am using the following to install it
BOOL bOK = SetupCopyOEMInf(
szSourceInfPath,NULL,SPOST_PATH,0,NULL,0,NULL,NULL);

This works on 99.999% of machines. A few customers fail with the following
in the setupapi.log

!!! flq: Unable to determine source information
for disk ID 100.
!!! inf: Error parsing section
[DriverInstall.NTAMD64]
!!! inf: Error 0xe0000102: The required line was
not found in the INF.
inf: {Install Inf Section [DriverInstall.NTAMD64]
exit (0xe0000102)}
!!! dvi: Failed copying driver files (e0000102)
!!! dvi: Error 0xe0000102: The required line was not
found in the INF.


When I check the usbser.sys file is not on the machine. I believe that it is
supposed to be extracted from a cab.

Any suggestions?
Anyone also experienced this?
How do I get support from Microsoft to answer this issue? [I have an MSDN
account but cannot find the way yo open the support incident {yes I tried
online and by phone}

Hoping someone has an answer

Geoff









From: Chris on 4 May 2010 16:18
On May 4, 12:08 pm, Geoff <Ge...(a)discussions.microsoft.com> wrote:

> When I check the usbser.sys file is not on the machine. I believe that it is
> supposed to be extracted from a cab.

Have you looked at this page?

http://support.microsoft.com/kb/837637

You didn't post your INF so it is hard to say if you have it set up
correctly to unpack the CAB if no one else has unpacked yet on that
installation of Windows.

> How do I get support from Microsoft to answer this issue? [I have an MSDN
> account but cannot find the way yo open the support incident {yes I tried
> online and by phone}

http://msdn.microsoft.com/en-us/subscriptions/bb266240.aspx ?
http://support.microsoft.com/oas/ ?
From: Tim Roberts on 5 May 2010 01:17
Geoff <Geoff(a)discussions.microsoft.com> wrote:
>
>I am using the microsoft supplied usbser.sys driver for my product.
>
>I am using the following to install it
> BOOL bOK = SetupCopyOEMInf(
>szSourceInfPath,NULL,SPOST_PATH,0,NULL,0,NULL,NULL);
>
>This works on 99.999% of machines. A few customers fail with the following
>in the setupapi.log
>
>!!! flq: Unable to determine source information
>for disk ID 100.
>!!! inf: Error parsing section
>[DriverInstall.NTAMD64]
>!!! inf: Error 0xe0000102: The required line was
>not found in the INF.
> inf: {Install Inf Section [DriverInstall.NTAMD64]
>exit (0xe0000102)}
>!!! dvi: Failed copying driver files (e0000102)
>!!! dvi: Error 0xe0000102: The required line was not
>found in the INF.
>
>When I check the usbser.sys file is not on the machine. I believe that it is
>supposed to be extracted from a cab.

Have you tested this on 64-bit machines? Do you have disk 100 in your
[SourceDisksNames] section?
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
 | 
Pages: 1
Prev: Driver Verifier in a VM
Next: Debug version of Windows XP