Prev: Yes - Checked on other 64 bit machines
Next: What WDK to use for WDF 1.7 ?
From: Geoff on 11 May 2010 18:10

Yes I have tried is on other 64 bit machines in our QA lab - they worked fine.

I do NOT have a disk100 in my [SourceDisksNames]

What should the section look like?

Thanks

Geoff


"Tim Roberts" wrote:

> 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.
> .
>
From: Geoff on 11 May 2010 18:28

Thanks for responding Chris, Sorry I took so long to get back, I thought I
would get email when someone posted and only just checked.

"Chris" wrote:

> 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
Yes - and the WinHEC document. Tried these on the customers machine without
success .
>
> 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.

This is my full inf

; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation
; Copyright (C) 2007 Microchip Technology Inc.
; Edited PlantSense INC

[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
LayoutFile=layout.inf
CatalogFile=%INFFILENAME%.cat
DriverVer=11/15/2007,5.1.2600.0

[Manufacturer]
%MFGNAME%=DeviceList, NTamd64

[DestinationDirs]
DefaultDestDir=12


;------------------------------------------------------------------------------
; Windows 2000/XP/Vista-32bit Sections
;------------------------------------------------------------------------------

[DriverInstall.nt]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.nt
AddReg=DriverInstall.nt.AddReg

[DriverCopyFiles.nt]
usbser.sys,,,0x20

[DriverInstall.nt.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.nt.Services]
AddService=usbser, 0x00000002, DriverService.nt

[DriverService.nt]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys

;------------------------------------------------------------------------------
; Vista-64bit Sections
;------------------------------------------------------------------------------

[DriverInstall.NTamd64]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.NTamd64
AddReg=DriverInstall.NTamd64.AddReg

[DriverCopyFiles.NTamd64]
usbser.sys,,,0x20

[DriverInstall.NTamd64.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.NTamd64.Services]
AddService=usbser, 0x00000002, DriverService.NTamd64

[DriverService.NTamd64]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys


;------------------------------------------------------------------------------
; Vendor and Product ID Definitions
;------------------------------------------------------------------------------
; When developing your USB device, the VID and PID used in the PC side
; application program and the firmware on the microcontroller must match.
; Modify the below line to use your VID and PID. Use the format as shown
below.
; Note: One INF file can be used for multiple devices with different VID and
PIDs.
; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of
the line.
;------------------------------------------------------------------------------
[SourceDisksFiles]
[SourceDisksNames]

[DeviceList]
%DESCRIPTION%=DriverInstall, USB\VID_1CC0&PID_8000

[DeviceList.NTamd64]
%DESCRIPTION%=DriverInstall, USB\VID_1CC0&PID_8000


;------------------------------------------------------------------------------
; String Definitions
;------------------------------------------------------------------------------
;Modify these strings to customize your device
;------------------------------------------------------------------------------
[Strings]
MFGFILENAME="EasyBloom"
INFFILENAME="plntsns"
DRIVERFILENAME ="usbser"
MFGNAME="PlantSense, INC"
INSTDISK="Installation Disc"
DESCRIPTION="EasyBloom Plant Sensor"
SERVICE="EasyBloom Plant Sensor Driver"



>
> > 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/ ?
Yeah tried those, after 40 mins on the phone trying to get the person to
understand the issue, then my phone lost connection and they did not call
back.
> .
>
 | 
Pages: 1
Prev: Yes - Checked on other 64 bit machines
Next: What WDK to use for WDF 1.7 ?