Hello

It is puzzling me as to why I need to restart the system after
installing the driver. My INF File listed below is modeled on the
lines of toaster example.

Appreciate any insights...


Thanks,
Puneet

[Version]
Signature=$Windows NT$
Class=D510M
ClassGuid={04F0FE74-4510-4024-BB58-4F36AD818607}
Provider=%MFGNAME%
DriverVer=10/14/2003,1.0.0.5
; Copyright 2003 by Multigon Industries, Inc.

;------------------------------------------------------------------------------
; D510M class definition
;------------------------------------------------------------------------------

[ClassInstall32.ntx86]
AddReg=d510m_class_addreg
CopyFiles=prop_copyfiles

[d510m_class_addreg]
HKR,,,,%D510MCLASSNAME%
HKR,,Icon,,"101"
HKR,,Installer32,,"d510mclass.dll,D510MClassInstal ler"
;HKR,,EnumPropPages32,,"d510mclass.dll,D510MEnumPr opPages"

[prop_copyfiles]
d510mclass.dll

[d510m_copyfiles]
d510m.sys

;------------------------------------------------------------------------------
; Standard INF sections
;------------------------------------------------------------------------------

[Manufacturer]
%MFGNAME%=d510m_device

[DestinationDirs]
d510m_copyfiles=10,System32\Drivers
prop_copyfiles=11

[SourceDisksNames]
1=%INSTDISK%,,,""

[SourceDisksFiles]
d510m.sys=1,,
d510mclass.dll=1,,

[d510m_device]
%DESCRIPTION%=d510m_install,PCI\VEN_10EE&DEV_0300

;------------------------------------------------------------------------------
; Windows 2000 Sections
;------------------------------------------------------------------------------

[d510m_install.ntx86]
CopyFiles=d510m_copyfiles,prop_copyfiles
AddReg=d510m_prop_provider_AddReg

[d510m_install.ntx86.Services]
AddService=d510m,0x00000002,d510m_ServiceInstallSe ction

[d510m_install.ntx86.hw]
AddReg=d510m_HwAddReg

[d510m_HwAddReg]
HKR,,FriendlyName,,"510M Input Card"

[d510m_prop_provider_AddReg]
HKR,,EnumPropPages32,,"d510mclass.dll,D510MEnumPro pPages"
HKR,,Icon,,"101"

[d510m_ServiceInstallSection]
DisplayName=%D510M_SERVICENAME%
Description=%D510M_SERVICEDESC%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%10%\system32\drivers\d510m.sys

;------------------------------------------------------------------------------
; String Definitions
;------------------------------------------------------------------------------

[Strings]
MFGNAME="Multigon Industries, Inc"
INSTDISK="510M Installation Disk"
DESCRIPTION="510M Input Card"
D510MCLASSNAME="D510M Input Card"
D510M_SERVICENAME="D510M Input Card Driver"
D510M_SERVICEDESC="D510M Kernel Mode Driver for D510M Input Card"

What is the device? What is the error code you see in the device manager
when you bring up the property page of the device? Did you check 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
"Puneet Jain" <pjain@datatekcorp.com> wrote in message
news:691b8e39.0310300957.b7a74f6@posting.google.co m...
---
---
---
---
---
---
---
---

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message news:<#RMNUO0nDHA.2512@TK2MSFTNGP09.phx.gbl>...
Eliyas

Device is a PCI Input card which collects data from the probes and
writes to the system memory that is mapped to the PCI space by the
driver.
I do not see any errors in the device manager property page for the
device. Interestingly, my application that talks to the device thru
win32 calls also seems to be working fine after the driver
update/install and before the suggested reboot.

The setupapi log is below. At one point it says 'Device required
reboot: files in use, or treated as in use.' I am not sure what files
it is talking about and/or who might be using them, because no
application is accessing the device/driver during installation/update.

Thanks in advance for pointers,
Puneet

[2003/10/31 09:49:51 300.162]
Set selected driver.
Searching for hardware ID(s):
pci\ven_10ee&dev_0300&subsys_00000000&rev_01,pci\v en_10ee&dev_0300&subsys_00000000,pci\ven_10ee&dev_ 0300&rev_01,pci\ven_10ee&dev_0300,pci\ven_10ee&dev _0300&cc_0b4000,pci\ven_10ee&dev_0300&cc_0b40
Searching for compatible ID(s):
pci\ven_10ee&cc_0b4000,pci\ven_10ee&cc_0b40,pci\ve n_10ee,pci\cc_0b4000,pci\cc_0b40
Enumerating files D:\WINNT\inf\*.inf
The file (D:\WINNT\inf\oem2.inf) is not digitally signed, ignoring
driver date.
Found PCI\VEN_10EE&DEV_0300 in D:\WINNT\inf\oem2.inf; Device: 510M
Input Card; Driver: 510M Input Card; Provider: Multigon Industries,
Inc; Mfg: Multigon Industries, Inc; Section: d510m_install
Decorated section name: d510m_install.NTx86
Searching for hardware ID(s):
pci\ven_10ee&dev_0300&subsys_00000000&rev_01,pci\v en_10ee&dev_0300&subsys_00000000,pci\ven_10ee&dev_ 0300&rev_01,pci\ven_10ee&dev_0300,pci\ven_10ee&dev _0300&cc_0b4000,pci\ven_10ee&dev_0300&cc_0b40
Searching for compatible ID(s):
pci\ven_10ee&cc_0b4000,pci\ven_10ee&cc_0b40,pci\ve n_10ee,pci\cc_0b4000,pci\cc_0b40
Enumerating files q:\pci_driver\dpci\sys\*.inf
The file (q:\pci_driver\dpci\sys\d510m.inf) is not digitally signed,
ignoring driver date.
Found PCI\VEN_10EE&DEV_0300 in q:\pci_driver\dpci\sys\d510m.inf;
Device: 510M Input Card; Driver: 510M Input Card; Provider: Multigon
Industries, Inc; Mfg: Multigon Industries, Inc; Section: d510m_install
Decorated section name: d510m_install.NTx86
Loading class-installer module for 510M Input Card.
An unsigned or incorrectly signed driver
(D:\WINNT\System32\d510mclass.dll) was installed for 510M Input Card.
Error 0x800b0100: No signature was present in the subject.
Device install function: DIF_SELECTBESTCOMPATDRV.
Selected driver installs from section d510m_install in
d:\winnt\inf\oem2.inf.
Changed class GUID of device to
{04F0FE74-4510-4024-BB58-4F36AD818607}.
Set selected driver.
Selected best compatible driver.
Device install function: DIF_INSTALLDEVICEFILES.
Doing copy-only install of
PCI\VEN_10EE&DEV_0300&SUBSYS_00000000&REV_01\3&61A AA01&0&88.
Installing section d510m_install.NTx86 from d:\winnt\inf\oem2.inf.
An unsigned or incorrectly signed driver (d:\winnt\inf\oem2.inf) was
installed for 510M Input Card. Error 0x800b0003: The form specified
for the subject is not one supported or known by the specified trust
provider.
Copying file q:\pci_driver\dpci\sys\objfre_w2k_x86\i386\d510m.s ys to
D:\WINNT\System32\Drivers\d510m.sys.
An unsigned or incorrectly signed driver
(q:\pci_driver\dpci\sys\objfre_w2k_x86\i386\d510m. sys) was installed
for 510M Input Card. Error 0x800b0003: The form specified for the
subject is not one supported or known by the specified trust provider.
SPFILENOTIFY_COPYERROR:
Source="q:\pci_driver\dpci\sys\objfre_w2k_x86\i386 \d510mclass.dll"
Target="D:\WINNT\System32\d510mclass.dll" Flags=0x00000000
Win32Error=0x00000002.
SPFILENOTIFY_COPYERROR: returned 1 (is, or is treated as
FILEOP_NEWPATH) ReturnBuffer="Q:\pci_driver\d510mclass\Release".
Copying file Q:\pci_driver\d510mclass\Release\d510mclass.dll to
D:\WINNT\System32\d510mclass.dll.
An unsigned or incorrectly signed driver
(Q:\pci_driver\d510mclass\Release\d510mclass.dll) was installed for
510M Input Card. Error 0x800b0003: The form specified for the subject
is not one supported or known by the specified trust provider.
Device required reboot: files in use, or treated as in use.
Device install function: DIF_REGISTER_COINSTALLERS.
Co-Installers Registered.
Device install function: DIF_INSTALLINTERFACES.
Installing section d510m_install.NTx86.Interfaces from
d:\winnt\inf\oem2.inf.
Interfaces installed.
Device install function: DIF_INSTALLDEVICE.
Doing full install of
PCI\VEN_10EE&DEV_0300&SUBSYS_00000000&REV_01\3&61A AA01&0&88.
Device install finished successfully
(PCI\VEN_10EE&DEV_0300&SUBSYS_00000000&REV_01\3&61 AAA01&0&88).
[2003/10/31 09:49:42 300.34]
Munged cmdline: "D:\WINNT\System32\mmc.exe"
D:\WINNT\system32\devmgmt.msc /s
EXE name: D:\WINNT\System32\mmc.exe
Loading class-installer module for 510M Input Card.
An unsigned or incorrectly signed driver
(D:\WINNT\System32\d510mclass.dll) was installed for 510M Input Card.
Error 0x800b0100: No signature was present in the subject.
The file (D:\WINNT\INF\oem2.inf) is not digitally signed, ignoring
driver date.
Selected driver installs from section d510m_install in
d:\winnt\inf\oem2.inf.
Changed class GUID of device to
{04F0FE74-4510-4024-BB58-4F36AD818607}.
Set selected driver.
Doing copy-only install of
PCI\VEN_10EE&DEV_0300&SUBSYS_00000000&REV_01\3&61A AA01&0&88.
The file (D:\WINNT\INF\oem2.inf) is not digitally signed, ignoring
driver date.
Selected driver installs from section d510m_install in
d:\winnt\inf\oem2.inf.
Changed class GUID of device to
{04F0FE74-4510-4024-BB58-4F36AD818607}.
Set selected driver.

Okay I see the problem. While updating the driver, if your are copying class
and coinstaller DLLs, you should make sure that new DLLs have different
names. When you update the driver, the existing DLLs are already loaded and
the file are locked, because they also participate in the update process.

Exactly for this reason, the toaster coinstaller DLL was called
tostrco1.dll, and DLL that's used by the toastpkg for update is called
tostrco2.dll.

If there is no change in the DLLs then don't specify them in the new INF
file that you are using to update the driver.

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


"Puneet Jain" <pjain@datatekcorp.com> wrote in message
news:691b8e39.0310310701.268ebff8@posting.google.c om...
000000,pci\ven_10ee&dev_0300&rev_01,pci\ven_10ee&d ev_0300,pci\ven_10ee&dev_0
300&cc_0b4000,pci\ven_10ee&dev_0300&cc_0b40
c_0b40
000000,pci\ven_10ee&dev_0300&rev_01,pci\ven_10ee&d ev_0300,pci\ven_10ee&dev_0
300&cc_0b4000,pci\ven_10ee&dev_0300&cc_0b40
c_0b40