I am trying to figure out why pre-installing our USB driver works a little
differently on a 32-bit WinXP than on a 64-bit WinXP. The only difference
is that after the install on the 64-bit system, when the device is plugged
in, instead of popping up the "Found New Hardware" wizard to allow the user
to complete installation, the installation silently quits, and the user has
to go back to Device Manager to ask it to install the driver. The
pre-install of the .inf logged a warning about the INF not containing a
digital signature(same on both systems). Yes, our driver is unsigned. The
policy on the computer is "Warn". The only error I see in setupapi.log is
1168 "Element not found". But this shows in the successful installation
anyway, so I am assuming it has something to do with our driver being
unsigned.

We have a 64-bit version of the driver, and the required NTia64 decorated
sections in the .inf file. Our application and install program are 32-bit.
We use SetupCopyOEMInf() to pre-install the .inf file.

The DDK says "Provide both 32-bit and 64-bit compilations of all kernel-mode
drivers, device installation applications, device installers, class
installers, and co-installers. " Does it have something to do with our
install program being 32-bit? We aren't using
UpdateDriverForPlugAndPlayDevices, and I don't see any other specific
instructions on what problems a 32-bit install would cause.

Any suggestions would be appreciated. The driver itself works fine, we just
have this one little installation glitch.

Thanks,
Diane

Re: 64-bit driver install by Eliyas

Eliyas
Fri Oct 24 12:34:08 CDT 2003

Can you post your INF and the setupapi.log?

--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx

"Diane Rose" <dianeroseemail@earthlink.net> wrote in message
news:NRbmb.246$Px2.101@newsread4.news.pas.earthlink.net...
> I am trying to figure out why pre-installing our USB driver works a little
> differently on a 32-bit WinXP than on a 64-bit WinXP. The only difference
> is that after the install on the 64-bit system, when the device is plugged
> in, instead of popping up the "Found New Hardware" wizard to allow the
user
> to complete installation, the installation silently quits, and the user
has
> to go back to Device Manager to ask it to install the driver. The
> pre-install of the .inf logged a warning about the INF not containing a
> digital signature(same on both systems). Yes, our driver is unsigned.
The
> policy on the computer is "Warn". The only error I see in setupapi.log is
> 1168 "Element not found". But this shows in the successful installation
> anyway, so I am assuming it has something to do with our driver being
> unsigned.
>
> We have a 64-bit version of the driver, and the required NTia64 decorated
> sections in the .inf file. Our application and install program are
32-bit.
> We use SetupCopyOEMInf() to pre-install the .inf file.
>
> The DDK says "Provide both 32-bit and 64-bit compilations of all
kernel-mode
> drivers, device installation applications, device installers, class
> installers, and co-installers. " Does it have something to do with our
> install program being 32-bit? We aren't using
> UpdateDriverForPlugAndPlayDevices, and I don't see any other specific
> instructions on what problems a 32-bit install would cause.
>
> Any suggestions would be appreciated. The driver itself works fine, we
just
> have this one little installation glitch.
>
> Thanks,
> Diane
>
>



Re: 64-bit driver install by Eliyas

Eliyas
Fri Oct 24 12:50:32 CDT 2003

Does the 64-bit install work if you don't prepopulate the INF but point the
Found new hardware wizard at it?


--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx



Re: 64-bit driver install by Diane

Diane
Fri Oct 24 13:31:17 CDT 2003

Yes - if the user plugs in the hardware before the install, and selects the
.inf and .sys path, all is well.

Diane

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:%231ktSdlmDHA.3688@TK2MSFTNGP11.phx.gbl...
> Does the 64-bit install work if you don't prepopulate the INF but point
the
> Found new hardware wizard at it?
>
>
> --
> -Eliyas
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
>
>



Re: 64-bit driver install by Diane

Diane
Fri Oct 24 14:14:05 CDT 2003

Here is the setupapi.log (the pertinent portion) and INF:

[2003/10/21 22:48:58 248.1]
#-199 Executing "C:\Program Files (x86)\FastLynx\FxNt.exe" with command
line: FxNt.exe /setup
#-037 Running 32-bit app in WOW64
#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file
"C:\Program Files (x86)\FastLynx\FxUsb.inf" will be installed
(Policy=Ignore). Error 0xe000022f: The third-party INF does not contain
digital signature information.
[2003/10/21 22:49:33 512.5]
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I140 Installing device class: "FASTLYNX"
{A5BC1D50-0511-4816-A776-890B581DF026}.
#I141 Class install completed with no errors.
[2003/10/21 22:49:31 512.3 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
"FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable"; Provider:
"Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
Section name: "DdInstall".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001. Driver
date: 09/29/2003. Version: 3.0.0.0.
#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [DdInstall] in
"c:\windows\inf\oem1.inf".
#I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
#-011 Installing section [DdInstall.NTIA64] from "c:\windows\inf\oem1.inf".
#E358 An unsigned, incorrectly signed, or Authenticode(tm) signed file
"c:\windows\inf\oem1.inf" for driver "FastLynx USB Bridge Cable" blocked
(server install). Error 1168: Element not found.
#E122 Device install failed. Error 1168: Element not found.
#E157 Default installer failed. Error 1168: Element not found.
[2003/10/21 22:49:35 1812.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{E4518B67-FA42-4B38-A9CA-346ED3A22760}
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
"FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable"; Provider:
"Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
Section name: "DdInstall".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001. Driver
date: 09/29/2003. Version: 3.0.0.0.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [DdInstall] in
"c:\windows\inf\oem1.inf".
#I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [DdInstall] in
"c:\windows\inf\oem1.inf".
#I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#-019 Searching for hardware ID(s):
usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
"FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable"; Provider:
"Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
Section name: "DdInstall".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001. Driver
date: 09/29/2003. Version: 3.0.0.0.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [DdInstall] in
"c:\windows\inf\oem1.inf".
#I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [DdInstall] in
"c:\windows\inf\oem1.inf".
#I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
#W334 Failed to verify catalog when scanning file queue. Error 1168: Element
not found.
#W366 An unsigned, incorrectly signed, or Authenticode(tm) signed file
"c:\windows\inf\oem1.inf" for driver "FastLynx USB Bridge Cable" will be
installed (Policy=Warn, user said ok). Error 1168: Element not found.
#-024 Copying file "C:\Program Files (x86)\FastLynx\FxUsb64.sys" to
"C:\WINDOWS\System32\Drivers\FxUsb64.sys".
#W362 An unsigned, incorrectly signed, or Authenticode(tm) signed file
"C:\Program Files (x86)\FastLynx\FxUsb64.sys" for driver "FastLynx USB
Bridge Cable" will be installed (Policy=Warn). Error 1168: Element not
found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [DdInstall.NTIA64.Interfaces] from
"c:\windows\inf\oem1.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
#I121 Device install of "USB\VID_067B&PID_0000\5&37E90124&0&2" finished
successfully.

; FastLynx USB 2.0 Bridge Cable device driver
; Copyright © 2001-2003, Sewell Development Corporation

[Version]
Signature="$CHICAGO$"
Class=FASTLYNX
ClassGUID={A5BC1D50-0511-4816-A776-890B581DF026}
provider=%Mfg%
DriverVer=08/21/2003,3.0

[ClassInstall32.NTia64]
Addreg=FastLynxClassReg

[ClassInstall32.NTx86]
Addreg=FastLynxClassReg

[ClassInstall32]
Addreg=FastLynxClassReg

[FastLynxClassReg]
HKR,,,0,%ClassName%
HKR,,SilentInstall,,1

[DestinationDirs]
DefaultDestDir=10,System32\Drivers

[SourceDisksNames]
1=%InstallDisk%,,

[SourceDisksFiles]
FxUsb.sys = 1,,
FxUsb98.sys = 1,,
FxUsb64.sys = 1,,

[Manufacturer]
%Mfg%=Sewell

[Sewell]
%DevDesc%=DdInstall, USB\VID_067B&PID_0000
%DevDesc2%=DdInstall, USB\VID_067B&PID_2501

[ControlFlags]
ExcludeFromSelect=USB\VID_067B&PID_0000
ExcludeFromSelect=USB\VID_067B&PID_2501

[DdInstall.NTia64]
DriverVer=09/29/2003,3.0
CopyFiles=@FxUsb64.sys
AddReg=AddReg.NTia64

[DdInstall.NTx86]
DriverVer=08/21/2003,3.0
CopyFiles=@FxUsb.sys
AddReg=AddReg.NTx86

[DdInstall]
DriverVer=08/21/2003,3.0
CopyFiles=@FxUsb98.sys
AddReg=AddReg

[DdInstall.NTx86.Services]
Addservice = FXUSB, 0x00000002, AddService

[DdInstall.NTia64.Services]
Addservice = FXUSB, 0x00000002, AddService.NTia64

[AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\FxUsb.sys
LoadOrderGroup = Base

[AddService.NTia64]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\FxUsb64.sys
LoadOrderGroup = Base

[AddReg.NTia64]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,FxUsb64.sys

[AddReg.NTx86]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,FxUsb.sys

[AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,FxUsb98.sys

[Strings]
Mfg="Sewell Development Corporation"
DevDesc="FastLynx USB Bridge Cable"
DevDesc2="FastLynx USB 2.0 Bridge Cable"
SvcDesc="FastLynx USB 2.0 Bridge Cable Driver"
InstallDisk="FastLynx Installation Diskette"
ClassName = "FastLynx"

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:u%23jSIUlmDHA.2364@TK2MSFTNGP11.phx.gbl...
> Can you post your INF and the setupapi.log?
>
> --
> -Eliyas
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
>
> "Diane Rose" <dianeroseemail@earthlink.net> wrote in message
> news:NRbmb.246$Px2.101@newsread4.news.pas.earthlink.net...
> > I am trying to figure out why pre-installing our USB driver works a
little
> > differently on a 32-bit WinXP than on a 64-bit WinXP. The only
difference
> > is that after the install on the 64-bit system, when the device is
plugged
> > in, instead of popping up the "Found New Hardware" wizard to allow the
> user
> > to complete installation, the installation silently quits, and the user
> has
> > to go back to Device Manager to ask it to install the driver. The
> > pre-install of the .inf logged a warning about the INF not containing a
> > digital signature(same on both systems). Yes, our driver is unsigned.
> The
> > policy on the computer is "Warn". The only error I see in setupapi.log
is
> > 1168 "Element not found". But this shows in the successful installation
> > anyway, so I am assuming it has something to do with our driver being
> > unsigned.
> >
> > We have a 64-bit version of the driver, and the required NTia64
decorated
> > sections in the .inf file. Our application and install program are
> 32-bit.
> > We use SetupCopyOEMInf() to pre-install the .inf file.
> >
> > The DDK says "Provide both 32-bit and 64-bit compilations of all
> kernel-mode
> > drivers, device installation applications, device installers, class
> > installers, and co-installers. " Does it have something to do with our
> > install program being 32-bit? We aren't using
> > UpdateDriverForPlugAndPlayDevices, and I don't see any other specific
> > instructions on what problems a 32-bit install would cause.
> >
> > Any suggestions would be appreciated. The driver itself works fine, we
> just
> > have this one little installation glitch.
> >
> > Thanks,
> > Diane
> >
> >
>
>



Re: 64-bit driver install by Eliyas

Eliyas
Fri Oct 24 14:14:49 CDT 2003

Would it be possible for you to recompile your install app as 64-bit and try
it out? We have a feeling that there is some weird thing going on in
generating the PNP from a 32 bit app.


--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx


"Diane Rose" <dianeroseemail@earthlink.net> wrote in message
news:Vdemb.365$Px2.325@newsread4.news.pas.earthlink.net...
> Yes - if the user plugs in the hardware before the install, and selects
the
> .inf and .sys path, all is well.
>
> Diane
>
> "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
> news:%231ktSdlmDHA.3688@TK2MSFTNGP11.phx.gbl...
> > Does the 64-bit install work if you don't prepopulate the INF but point
> the
> > Found new hardware wizard at it?
> >
> >
> > --
> > -Eliyas
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
> >
> >
>
>



Re: 64-bit driver install by Diane

Diane
Fri Oct 24 16:39:06 CDT 2003

We will take that little install piece and make it into a 64-bit app. (We
can't convert the entire application.) I will let you know what the results
are.

Diane

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:OKFOZMmmDHA.3316@tk2msftngp13.phx.gbl...
> Would it be possible for you to recompile your install app as 64-bit and
try
> it out? We have a feeling that there is some weird thing going on in
> generating the PNP from a 32 bit app.
>
>
> --
> -Eliyas
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
>
>
> "Diane Rose" <dianeroseemail@earthlink.net> wrote in message
> news:Vdemb.365$Px2.325@newsread4.news.pas.earthlink.net...
> > Yes - if the user plugs in the hardware before the install, and selects
> the
> > .inf and .sys path, all is well.
> >
> > Diane
> >
> > "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
> > news:%231ktSdlmDHA.3688@TK2MSFTNGP11.phx.gbl...
> > > Does the 64-bit install work if you don't prepopulate the INF but
point
> > the
> > > Found new hardware wizard at it?
> > >
> > >
> > > --
> > > -Eliyas
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
> > >
> > >
> >
> >
>
>



Re: 64-bit driver install by heinz_baer

heinz_baer
Sat Oct 25 23:05:23 CDT 2003

> We have a feeling that there is some weird thing going on...

Something weird indeed does go on:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win64/win64/file_system_redirector.asp

The %systemroot%\System32 directory is reserved for 64-bit
applications. Most DLL file names were not changed when porting to
64-bit, so 32-bit applications must use a different directory as their
System32 directory. WOW64 hides this difference using a file system
redirector. Whenever a 32-bit application attempts to access
%systemroot%\System32, the access is redirected to a new directory,
%systemroot%\SysWOW64. Certain subdirectories are exempt: for example,
the Spool subdirectory is exempt from redirection to better support
the print spooler. To retrieve the name of the 32-bit system
directory, 64-bit applications should use the GetSystemWow64Directory
function.

Re: 64-bit driver install by Ramboi2

Ramboi2
Tue Oct 28 15:50:30 CST 2003

Hi Diane,
Did you get your problem resolved? If not then email me, because I already
went through what you are going through now with success.

Ramboi2@attbi.com

"Diane Rose" <dianeroseemail@earthlink.net> wrote in message
news:1Semb.401$Px2.5@newsread4.news.pas.earthlink.net...
> Here is the setupapi.log (the pertinent portion) and INF:
>
> [2003/10/21 22:48:58 248.1]
> #-199 Executing "C:\Program Files (x86)\FastLynx\FxNt.exe" with command
> line: FxNt.exe /setup
> #-037 Running 32-bit app in WOW64
> #W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> "C:\Program Files (x86)\FastLynx\FxUsb.inf" will be installed
> (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain
> digital signature information.
> [2003/10/21 22:49:33 512.5]
> #-198 Command line processed: C:\WINDOWS\system32\services.exe
> #I140 Installing device class: "FASTLYNX"
> {A5BC1D50-0511-4816-A776-890B581DF026}.
> #I141 Class install completed with no errors.
> [2003/10/21 22:49:31 512.3 Driver Install]
> #-019 Searching for hardware ID(s):
> usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> #-018 Searching for compatible ID(s):
> usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> #-198 Command line processed: C:\WINDOWS\system32\services.exe
> #I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
> "FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable"; Provider:
> "Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
> Section name: "DdInstall".
> #I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
> #I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001. Driver
> date: 09/29/2003. Version: 3.0.0.0.
> #I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> #I063 Selected driver installs from section [DdInstall] in
> "c:\windows\inf\oem1.inf".
> #I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
> #I060 Set selected driver.
> #I058 Selected best compatible driver.
> #-166 Device install function: DIF_INSTALLDEVICEFILES.
> #I124 Doing copy-only install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
> #-011 Installing section [DdInstall.NTIA64] from "c:\windows\inf\oem1.inf".
> #E358 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> "c:\windows\inf\oem1.inf" for driver "FastLynx USB Bridge Cable" blocked
> (server install). Error 1168: Element not found.
> #E122 Device install failed. Error 1168: Element not found.
> #E157 Default installer failed. Error 1168: Element not found.
> [2003/10/21 22:49:35 1812.2]
> #-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
> rundll32.exe newdev.dll,ClientSideInstall
> \\.\pipe\PNP_Device_Install_Pipe_0.{E4518B67-FA42-4B38-A9CA-346ED3A22760}
> #I060 Set selected driver.
> #-019 Searching for hardware ID(s):
> usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> #-018 Searching for compatible ID(s):
> usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> #I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
> "FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable"; Provider:
> "Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
> Section name: "DdInstall".
> #I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
> #I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001. Driver
> date: 09/29/2003. Version: 3.0.0.0.
> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> #I063 Selected driver installs from section [DdInstall] in
> "c:\windows\inf\oem1.inf".
> #I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
> #I060 Set selected driver.
> #I058 Selected best compatible driver.
> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> #I063 Selected driver installs from section [DdInstall] in
> "c:\windows\inf\oem1.inf".
> #I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
> #I060 Set selected driver.
> #I058 Selected best compatible driver.
> #I060 Set selected driver.
> #-019 Searching for hardware ID(s):
> usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> #-018 Searching for compatible ID(s):
> usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> #-019 Searching for hardware ID(s):
> usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> #-018 Searching for compatible ID(s):
> usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> #I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
> "FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable"; Provider:
> "Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
> Section name: "DdInstall".
> #I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
> #I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001. Driver
> date: 09/29/2003. Version: 3.0.0.0.
> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> #I063 Selected driver installs from section [DdInstall] in
> "c:\windows\inf\oem1.inf".
> #I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
> #I060 Set selected driver.
> #I058 Selected best compatible driver.
> #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> #I063 Selected driver installs from section [DdInstall] in
> "c:\windows\inf\oem1.inf".
> #I320 Class GUID of device remains: {A5BC1D50-0511-4816-A776-890B581DF026}.
> #I060 Set selected driver.
> #I058 Selected best compatible driver.
> #-124 Doing copy-only install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
> #W334 Failed to verify catalog when scanning file queue. Error 1168: Element
> not found.
> #W366 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> "c:\windows\inf\oem1.inf" for driver "FastLynx USB Bridge Cable" will be
> installed (Policy=Warn, user said ok). Error 1168: Element not found.
> #-024 Copying file "C:\Program Files (x86)\FastLynx\FxUsb64.sys" to
> "C:\WINDOWS\System32\Drivers\FxUsb64.sys".
> #W362 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> "C:\Program Files (x86)\FastLynx\FxUsb64.sys" for driver "FastLynx USB
> Bridge Cable" will be installed (Policy=Warn). Error 1168: Element not
> found.
> #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> #I056 Coinstallers registered.
> #-166 Device install function: DIF_INSTALLINTERFACES.
> #-011 Installing section [DdInstall.NTIA64.Interfaces] from
> "c:\windows\inf\oem1.inf".
> #I054 Interfaces installed.
> #-166 Device install function: DIF_INSTALLDEVICE.
> #I123 Doing full install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
> #I121 Device install of "USB\VID_067B&PID_0000\5&37E90124&0&2" finished
> successfully.
>
> ; FastLynx USB 2.0 Bridge Cable device driver
> ; Copyright © 2001-2003, Sewell Development Corporation
>
> [Version]
> Signature="$CHICAGO$"
> Class=FASTLYNX
> ClassGUID={A5BC1D50-0511-4816-A776-890B581DF026}
> provider=%Mfg%
> DriverVer=08/21/2003,3.0
>
> [ClassInstall32.NTia64]
> Addreg=FastLynxClassReg
>
> [ClassInstall32.NTx86]
> Addreg=FastLynxClassReg
>
> [ClassInstall32]
> Addreg=FastLynxClassReg
>
> [FastLynxClassReg]
> HKR,,,0,%ClassName%
> HKR,,SilentInstall,,1
>
> [DestinationDirs]
> DefaultDestDir=10,System32\Drivers
>
> [SourceDisksNames]
> 1=%InstallDisk%,,
>
> [SourceDisksFiles]
> FxUsb.sys = 1,,
> FxUsb98.sys = 1,,
> FxUsb64.sys = 1,,
>
> [Manufacturer]
> %Mfg%=Sewell
>
> [Sewell]
> %DevDesc%=DdInstall, USB\VID_067B&PID_0000
> %DevDesc2%=DdInstall, USB\VID_067B&PID_2501
>
> [ControlFlags]
> ExcludeFromSelect=USB\VID_067B&PID_0000
> ExcludeFromSelect=USB\VID_067B&PID_2501
>
> [DdInstall.NTia64]
> DriverVer=09/29/2003,3.0
> CopyFiles=@FxUsb64.sys
> AddReg=AddReg.NTia64
>
> [DdInstall.NTx86]
> DriverVer=08/21/2003,3.0
> CopyFiles=@FxUsb.sys
> AddReg=AddReg.NTx86
>
> [DdInstall]
> DriverVer=08/21/2003,3.0
> CopyFiles=@FxUsb98.sys
> AddReg=AddReg
>
> [DdInstall.NTx86.Services]
> Addservice = FXUSB, 0x00000002, AddService
>
> [DdInstall.NTia64.Services]
> Addservice = FXUSB, 0x00000002, AddService.NTia64
>
> [AddService]
> DisplayName = %SvcDesc%
> ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> StartType = 3 ; SERVICE_DEMAND_START
> ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> ServiceBinary = %10%\System32\Drivers\FxUsb.sys
> LoadOrderGroup = Base
>
> [AddService.NTia64]
> DisplayName = %SvcDesc%
> ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> StartType = 3 ; SERVICE_DEMAND_START
> ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> ServiceBinary = %10%\System32\Drivers\FxUsb64.sys
> LoadOrderGroup = Base
>
> [AddReg.NTia64]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,FxUsb64.sys
>
> [AddReg.NTx86]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,FxUsb.sys
>
> [AddReg]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,FxUsb98.sys
>
> [Strings]
> Mfg="Sewell Development Corporation"
> DevDesc="FastLynx USB Bridge Cable"
> DevDesc2="FastLynx USB 2.0 Bridge Cable"
> SvcDesc="FastLynx USB 2.0 Bridge Cable Driver"
> InstallDisk="FastLynx Installation Diskette"
> ClassName = "FastLynx"
>
> "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
> news:u%23jSIUlmDHA.2364@TK2MSFTNGP11.phx.gbl...
> > Can you post your INF and the setupapi.log?
> >
> > --
> > -Eliyas
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
> >
> > "Diane Rose" <dianeroseemail@earthlink.net> wrote in message
> > news:NRbmb.246$Px2.101@newsread4.news.pas.earthlink.net...
> > > I am trying to figure out why pre-installing our USB driver works a
> little
> > > differently on a 32-bit WinXP than on a 64-bit WinXP. The only
> difference
> > > is that after the install on the 64-bit system, when the device is
> plugged
> > > in, instead of popping up the "Found New Hardware" wizard to allow the
> > user
> > > to complete installation, the installation silently quits, and the user
> > has
> > > to go back to Device Manager to ask it to install the driver. The
> > > pre-install of the .inf logged a warning about the INF not containing a
> > > digital signature(same on both systems). Yes, our driver is unsigned.
> > The
> > > policy on the computer is "Warn". The only error I see in setupapi.log
> is
> > > 1168 "Element not found". But this shows in the successful installation
> > > anyway, so I am assuming it has something to do with our driver being
> > > unsigned.
> > >
> > > We have a 64-bit version of the driver, and the required NTia64
> decorated
> > > sections in the .inf file. Our application and install program are
> > 32-bit.
> > > We use SetupCopyOEMInf() to pre-install the .inf file.
> > >
> > > The DDK says "Provide both 32-bit and 64-bit compilations of all
> > kernel-mode
> > > drivers, device installation applications, device installers, class
> > > installers, and co-installers. " Does it have something to do with our
> > > install program being 32-bit? We aren't using
> > > UpdateDriverForPlugAndPlayDevices, and I don't see any other specific
> > > instructions on what problems a 32-bit install would cause.
> > >
> > > Any suggestions would be appreciated. The driver itself works fine, we
> > just
> > > have this one little installation glitch.
> > >
> > > Thanks,
> > > Diane
> > >
> > >
> >
> >
>
>



Re: 64-bit driver install by Diane

Diane
Wed Oct 29 10:12:56 CST 2003

We have not solved it yet. We haven't tried the 64-bit install yet.

We would appreciate any information you might have on this. What did you do
to resolve this issue? (I tried to e-mail you but it didn't go through.)

Diane

"Ramboi2" <Ramboi2@nospam.com> wrote in message
news:GwBnb.51168$Fm2.25849@attbi_s04...
> Hi Diane,
> Did you get your problem resolved? If not then email me, because I
already
> went through what you are going through now with success.
>
> Ramboi2@attbi.com
>
> "Diane Rose" <dianeroseemail@earthlink.net> wrote in message
> news:1Semb.401$Px2.5@newsread4.news.pas.earthlink.net...
> > Here is the setupapi.log (the pertinent portion) and INF:
> >
> > [2003/10/21 22:48:58 248.1]
> > #-199 Executing "C:\Program Files (x86)\FastLynx\FxNt.exe" with command
> > line: FxNt.exe /setup
> > #-037 Running 32-bit app in WOW64
> > #W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> > "C:\Program Files (x86)\FastLynx\FxUsb.inf" will be installed
> > (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain
> > digital signature information.
> > [2003/10/21 22:49:33 512.5]
> > #-198 Command line processed: C:\WINDOWS\system32\services.exe
> > #I140 Installing device class: "FASTLYNX"
> > {A5BC1D50-0511-4816-A776-890B581DF026}.
> > #I141 Class install completed with no errors.
> > [2003/10/21 22:49:31 512.3 Driver Install]
> > #-019 Searching for hardware ID(s):
> > usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> > #-018 Searching for compatible ID(s):
> > usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> > #-198 Command line processed: C:\WINDOWS\system32\services.exe
> > #I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
> > "FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable";
Provider:
> > "Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
> > Section name: "DdInstall".
> > #I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
> > #I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001.
Driver
> > date: 09/29/2003. Version: 3.0.0.0.
> > #I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [DdInstall] in
> > "c:\windows\inf\oem1.inf".
> > #I320 Class GUID of device remains:
{A5BC1D50-0511-4816-A776-890B581DF026}.
> > #I060 Set selected driver.
> > #I058 Selected best compatible driver.
> > #-166 Device install function: DIF_INSTALLDEVICEFILES.
> > #I124 Doing copy-only install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
> > #-011 Installing section [DdInstall.NTIA64] from
"c:\windows\inf\oem1.inf".
> > #E358 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> > "c:\windows\inf\oem1.inf" for driver "FastLynx USB Bridge Cable" blocked
> > (server install). Error 1168: Element not found.
> > #E122 Device install failed. Error 1168: Element not found.
> > #E157 Default installer failed. Error 1168: Element not found.
> > [2003/10/21 22:49:35 1812.2]
> > #-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
> > rundll32.exe newdev.dll,ClientSideInstall
> >
\\.\pipe\PNP_Device_Install_Pipe_0.{E4518B67-FA42-4B38-A9CA-346ED3A22760}
> > #I060 Set selected driver.
> > #-019 Searching for hardware ID(s):
> > usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> > #-018 Searching for compatible ID(s):
> > usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> > #I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
> > "FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable";
Provider:
> > "Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
> > Section name: "DdInstall".
> > #I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
> > #I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001.
Driver
> > date: 09/29/2003. Version: 3.0.0.0.
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [DdInstall] in
> > "c:\windows\inf\oem1.inf".
> > #I320 Class GUID of device remains:
{A5BC1D50-0511-4816-A776-890B581DF026}.
> > #I060 Set selected driver.
> > #I058 Selected best compatible driver.
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [DdInstall] in
> > "c:\windows\inf\oem1.inf".
> > #I320 Class GUID of device remains:
{A5BC1D50-0511-4816-A776-890B581DF026}.
> > #I060 Set selected driver.
> > #I058 Selected best compatible driver.
> > #I060 Set selected driver.
> > #-019 Searching for hardware ID(s):
> > usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> > #-018 Searching for compatible ID(s):
> > usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> > #-019 Searching for hardware ID(s):
> > usb\vid_067b&pid_0000&rev_0000,usb\vid_067b&pid_0000
> > #-018 Searching for compatible ID(s):
> > usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
> > #I022 Found "USB\VID_067B&PID_0000" in C:\WINDOWS\inf\oem1.inf; Device:
> > "FastLynx USB Bridge Cable"; Driver: "FastLynx USB Bridge Cable";
Provider:
> > "Sewell Development Corporation"; Mfg: "Sewell Development Corporation";
> > Section name: "DdInstall".
> > #I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
> > #I023 Actual install section: [DdInstall.NTIA64]. Rank: 0x00008001.
Driver
> > date: 09/29/2003. Version: 3.0.0.0.
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [DdInstall] in
> > "c:\windows\inf\oem1.inf".
> > #I320 Class GUID of device remains:
{A5BC1D50-0511-4816-A776-890B581DF026}.
> > #I060 Set selected driver.
> > #I058 Selected best compatible driver.
> > #-166 Device install function: DIF_SELECTBESTCOMPATDRV.
> > #I063 Selected driver installs from section [DdInstall] in
> > "c:\windows\inf\oem1.inf".
> > #I320 Class GUID of device remains:
{A5BC1D50-0511-4816-A776-890B581DF026}.
> > #I060 Set selected driver.
> > #I058 Selected best compatible driver.
> > #-124 Doing copy-only install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
> > #W334 Failed to verify catalog when scanning file queue. Error 1168:
Element
> > not found.
> > #W366 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> > "c:\windows\inf\oem1.inf" for driver "FastLynx USB Bridge Cable" will be
> > installed (Policy=Warn, user said ok). Error 1168: Element not found.
> > #-024 Copying file "C:\Program Files (x86)\FastLynx\FxUsb64.sys" to
> > "C:\WINDOWS\System32\Drivers\FxUsb64.sys".
> > #W362 An unsigned, incorrectly signed, or Authenticode(tm) signed file
> > "C:\Program Files (x86)\FastLynx\FxUsb64.sys" for driver "FastLynx USB
> > Bridge Cable" will be installed (Policy=Warn). Error 1168: Element not
> > found.
> > #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> > #I056 Coinstallers registered.
> > #-166 Device install function: DIF_INSTALLINTERFACES.
> > #-011 Installing section [DdInstall.NTIA64.Interfaces] from
> > "c:\windows\inf\oem1.inf".
> > #I054 Interfaces installed.
> > #-166 Device install function: DIF_INSTALLDEVICE.
> > #I123 Doing full install of "USB\VID_067B&PID_0000\5&37E90124&0&2".
> > #I121 Device install of "USB\VID_067B&PID_0000\5&37E90124&0&2" finished
> > successfully.
> >
> > ; FastLynx USB 2.0 Bridge Cable device driver
> > ; Copyright © 2001-2003, Sewell Development Corporation
> >
> > [Version]
> > Signature="$CHICAGO$"
> > Class=FASTLYNX
> > ClassGUID={A5BC1D50-0511-4816-A776-890B581DF026}
> > provider=%Mfg%
> > DriverVer=08/21/2003,3.0
> >
> > [ClassInstall32.NTia64]
> > Addreg=FastLynxClassReg
> >
> > [ClassInstall32.NTx86]
> > Addreg=FastLynxClassReg
> >
> > [ClassInstall32]
> > Addreg=FastLynxClassReg
> >
> > [FastLynxClassReg]
> > HKR,,,0,%ClassName%
> > HKR,,SilentInstall,,1
> >
> > [DestinationDirs]
> > DefaultDestDir=10,System32\Drivers
> >
> > [SourceDisksNames]
> > 1=%InstallDisk%,,
> >
> > [SourceDisksFiles]
> > FxUsb.sys = 1,,
> > FxUsb98.sys = 1,,
> > FxUsb64.sys = 1,,
> >
> > [Manufacturer]
> > %Mfg%=Sewell
> >
> > [Sewell]
> > %DevDesc%=DdInstall, USB\VID_067B&PID_0000
> > %DevDesc2%=DdInstall, USB\VID_067B&PID_2501
> >
> > [ControlFlags]
> > ExcludeFromSelect=USB\VID_067B&PID_0000
> > ExcludeFromSelect=USB\VID_067B&PID_2501
> >
> > [DdInstall.NTia64]
> > DriverVer=09/29/2003,3.0
> > CopyFiles=@FxUsb64.sys
> > AddReg=AddReg.NTia64
> >
> > [DdInstall.NTx86]
> > DriverVer=08/21/2003,3.0
> > CopyFiles=@FxUsb.sys
> > AddReg=AddReg.NTx86
> >
> > [DdInstall]
> > DriverVer=08/21/2003,3.0
> > CopyFiles=@FxUsb98.sys
> > AddReg=AddReg
> >
> > [DdInstall.NTx86.Services]
> > Addservice = FXUSB, 0x00000002, AddService
> >
> > [DdInstall.NTia64.Services]
> > Addservice = FXUSB, 0x00000002, AddService.NTia64
> >
> > [AddService]
> > DisplayName = %SvcDesc%
> > ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> > StartType = 3 ; SERVICE_DEMAND_START
> > ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> > ServiceBinary = %10%\System32\Drivers\FxUsb.sys
> > LoadOrderGroup = Base
> >
> > [AddService.NTia64]
> > DisplayName = %SvcDesc%
> > ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> > StartType = 3 ; SERVICE_DEMAND_START
> > ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> > ServiceBinary = %10%\System32\Drivers\FxUsb64.sys
> > LoadOrderGroup = Base
> >
> > [AddReg.NTia64]
> > HKR,,DevLoader,,*ntkern
> > HKR,,NTMPDriver,,FxUsb64.sys
> >
> > [AddReg.NTx86]
> > HKR,,DevLoader,,*ntkern
> > HKR,,NTMPDriver,,FxUsb.sys
> >
> > [AddReg]
> > HKR,,DevLoader,,*ntkern
> > HKR,,NTMPDriver,,FxUsb98.sys
> >
> > [Strings]
> > Mfg="Sewell Development Corporation"
> > DevDesc="FastLynx USB Bridge Cable"
> > DevDesc2="FastLynx USB 2.0 Bridge Cable"
> > SvcDesc="FastLynx USB 2.0 Bridge Cable Driver"
> > InstallDisk="FastLynx Installation Diskette"
> > ClassName = "FastLynx"
> >
> > "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
> > news:u%23jSIUlmDHA.2364@TK2MSFTNGP11.phx.gbl...
> > > Can you post your INF and the setupapi.log?
> > >
> > > --
> > > -Eliyas
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
> > >
> > > "Diane Rose" <dianeroseemail@earthlink.net> wrote in message
> > > news:NRbmb.246$Px2.101@newsread4.news.pas.earthlink.net...
> > > > I am trying to figure out why pre-installing our USB driver works a
> > little
> > > > differently on a 32-bit WinXP than on a 64-bit WinXP. The only
> > difference
> > > > is that after the install on the 64-bit system, when the device is
> > plugged
> > > > in, instead of popping up the "Found New Hardware" wizard to allow
the
> > > user
> > > > to complete installation, the installation silently quits, and the
user
> > > has
> > > > to go back to Device Manager to ask it to install the driver. The
> > > > pre-install of the .inf logged a warning about the INF not
containing a
> > > > digital signature(same on both systems). Yes, our driver is
unsigned.
> > > The
> > > > policy on the computer is "Warn". The only error I see in
setupapi.log
> > is
> > > > 1168 "Element not found". But this shows in the successful
installation
> > > > anyway, so I am assuming it has something to do with our driver
being
> > > > unsigned.
> > > >
> > > > We have a 64-bit version of the driver, and the required NTia64
> > decorated
> > > > sections in the .inf file. Our application and install program are
> > > 32-bit.
> > > > We use SetupCopyOEMInf() to pre-install the .inf file.
> > > >
> > > > The DDK says "Provide both 32-bit and 64-bit compilations of all
> > > kernel-mode
> > > > drivers, device installation applications, device installers, class
> > > > installers, and co-installers. " Does it have something to do with
our
> > > > install program being 32-bit? We aren't using
> > > > UpdateDriverForPlugAndPlayDevices, and I don't see any other
specific
> > > > instructions on what problems a 32-bit install would cause.
> > > >
> > > > Any suggestions would be appreciated. The driver itself works fine,
we
> > > just
> > > > have this one little installation glitch.
> > > >
> > > > Thanks,
> > > > Diane
> > > >
> > > >
> > >
> > >
> >
> >
>
>