avoiding reboot after install

My usb composite usb device requires a reboot after installation of
drivers.This is on Win2K-SP4
What could be the issue ?
Portion from setupapi.log file with full logging :
An unsigned or incorrectly signed driver (d:\xv\xxx.inf) was installed for
XXX Camera Composite Device. Error 0xe000022f: The third-party INF does not
contain digital signature information.
@ 11:31:01.218 : Opened INF "C:\WINNT\INF\oem19.inf".
Device required reboot: Device has problem: 10. <----------------------
@ 11:31:26.687 : Executing RunOnce to process 5 RunOnce entries.
Device install finished successfully (USB\VID_xxxx&PID_yyyy\ABCDEFGHIJK).
From cfg.h ;
10 refers to CM_PROB_PARTIAL_LOG_CONF
or is the 10 here in decimal ? Then it means CM_PROB_FAILED_START

jeffm
Wed Dec 28 13:06:22 CST 2005

------=_NextPart_0001_13837ECD
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Michelle,

The problem is probably CM_PROB_FAILED_START. If you wrote the drivers,
then try debugging your DriverEntry and AddDevice routines. Otherwise, you
could collect verbose setupapi.log information, and confirm that Setup was
starting the driver. If this is a 3rd party driver, then contact the
vendor for assistance with troubleshooting why the driver won't start.

To enable verbose logging, set this registry value:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
"LogLevel"=dword:0000ffff

I can take a look at it, if you want to send me your INF and a complete
verbose setupapi.log for the failed install. Use the email address below
without the 'online.' portion.

Thanks,
[MSFT] Jeff McCashland
jeffm@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.


------=_NextPart_0001_13837ECD
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Michelle,
\par
\par The problem is probably CM_PROB_FAILED_START. If you wrote the drivers, then try debugging your DriverEntry and AddDevice routines. Otherwise, you could collect verbose setupapi.log information, and confirm that Setup was starting the driver. If this is a 3rd party driver, then contact the vendor for assistance with troubleshooting why the driver won't start.
\par
\par To enable verbose logging, set this registry value:
\par [HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Setup]
\par "LogLevel"=dword:0000ffff
\par
\par I can take a look at it, if you want to send me your INF and a complete verbose setupapi.log for the failed install. Use the email address below without the 'online.' portion.
\par
\par Thanks,
\par [MSFT] Jeff McCashland
\par jeffm@online.microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par
\par }
------=_NextPart_0001_13837ECD--

michelle
Wed Dec 28 22:27:02 CST 2005


Jeff thanks for the response
I later concluded that the problem is CM_PROB_FAILED_START.Yes this is my
own driver.I had enabled vervose logging with 0xff setting and I quoted from
the setupapi.log in my previous posting.
Note this happens only for the first time install ,after that the driver
works perfectly fine.

"Jeff McCashland [MSFT]" wrote:

> Michelle,
>
> The problem is probably CM_PROB_FAILED_START. If you wrote the drivers,
> then try debugging your DriverEntry and AddDevice routines. Otherwise, you
> could collect verbose setupapi.log information, and confirm that Setup was
> starting the driver. If this is a 3rd party driver, then contact the
> vendor for assistance with troubleshooting why the driver won't start.
>
> To enable verbose logging, set this registry value:
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
> "LogLevel"=dword:0000ffff
>
> I can take a look at it, if you want to send me your INF and a complete
> verbose setupapi.log for the failed install. Use the email address below
> without the 'online.' portion.
>
> Thanks,
> [MSFT] Jeff McCashland
> jeffm@online.microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no rights

jeffm
Thu Dec 29 09:21:36 CST 2005

------=_NextPart_0001_17DBDE32
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Michelle,

In that case, I would suggest performing kernel-mode debugging on a checked
build of your driver. You could step through your DriverEntry and
AddDevice routines, or print debug messages from the routines to see if
these complete successfully.

What are the functions of your composite USB device? Do you have multiple
INF files? Is it the parent device, or one of the child functions that
fails install? How is the device being installed? I may be able to
suggest more if I can look at your INF file(s) and a complete verbose
(setting 0xffff) setupapi.log.

Thanks,
[MSFT] Jeff McCashland
jeffm@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_17DBDE32
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Michelle,
\par
\par In that case, I would suggest performing kernel-mode debugging on a checked build of your driver. You could step through your DriverEntry and AddDevice routines, or print debug messages from the routines to see if these complete successfully.
\par
\par What are the functions of your composite USB device? Do you have multiple INF files? Is it the parent device, or one of the child functions that fails install? How is the device being installed? I may be able to suggest more if I can look at your INF file(s) and a complete verbose (setting 0xffff) setupapi.log.
\par
\par Thanks,
\par [MSFT] Jeff McCashland
\par jeffm@online.microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_17DBDE32--

chester
Thu Feb 09 19:31:19 CST 2006

Hi, We are having the same problem.
We have an application that is installing a File Driver through inf file.
The problem is that when we install the application, it installs the file
driver but does not start it.
After you do a reboot, the driver starts running and the application works
fine.

Is there anyway to start the driver without having to reboot?

I have beow the complete inf file we are using:

;;;
;;; CtxtFileMon
;;;
;;;
;;; Copyright (c) 2000, Microsoft Corporation
;;;

[Version]
signature = "$Windows NT$"
Class = "ActivityMonitor" ;This is determined by the work this filter
driver does
ClassGuid = {b86dff51-a31e-4bac-b3cf-e8cfe75c9fc2} ;This value is
determined by the Class
Provider = %Msft%
DriverVer = 08/28/2000,1.0.0.1
CatalogFile = CtxtFileMon.cat ; A
CatalogFile entry is required for a WHQL signature.
; The actual
catalog file will be provided by WHQL. The
; catalog
file for this sample is not provided for use.

[DestinationDirs]
DefaultDestDir = 12
CtxtFileMon.DriverFiles = 12 ;%windir%\system32\drivers
;;CtxtFileMon.UserFiles = 10,CtxtFileMon ;%windir%\CtxtFileMon

;;
;; Default install sections
;;

[DefaultInstall]
OptionDesc = %CtxtFileMonServiceDesc%
CopyFiles = CtxtFileMon.DriverFiles
;;CopyFiles = CtxtFileMon.DriverFiles, CtxtFileMon.UserFiles

[SourceDisksNames]
1 = %Disk1%

[SourceDisksFiles]
CtxtFileMon.exe = 1
CtxtFileMon.sys = 1

[DefaultInstall.Services]
AddService = %CtxtFileMonServiceName%,,CtxtFileMon.Service

;;
;; Default uninstall sections
;;

[DefaultUninstall]
;;DelFiles = CtxtFileMon.DriverFiles, CtxtFileMon.UserFiles
DelFiles = CtxtFileMon.DriverFiles
DelReg = CtxtFileMon.DelRegistry

[DefaultUninstall.Services]
DelService = CtxtFileMon,0x200 ; Flags note to stop service first

;
; Services Section
;

[CtxtFileMon.Service]
DisplayName = %CtxtFileMonServiceName%
Description = %CtxtFileMonServiceDesc%
ServiceBinary =
%12%\CtxtFileMon.sys ;%windir%\system32\drivers\CtxtFileMon.sys
ServiceType = 2 ;SERVICE_FILE_SYSTEM_DRIVER
StartType = 2
ErrorControl = 1 ;SERVICE_ERROR_NORMAL
LoadOrderGroup = "filter"
AddReg = CtxtFileMon.AddRegistry

;
; Registry Modifications
;

[CtxtFileMon.AddRegistry]
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonMaxRecords%,0x00010001 ,500
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonMaxNames%,0x00010001 ,500
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonDebugFlags%,0x00010001 ,0
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonAttachMode%,0x00010001 ,2

[CtxtFileMon.DelRegistry]
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonMaxRecords%
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonMaxNames%
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonDebugFlags%
HKLM,%CtxtFileMonRegistry%,%CtxtFileMonAttachMode%

;
; Copy Files
;

[CtxtFileMon.DriverFiles]
CtxtFileMon.sys

[CtxtFileMon.UserFiles]
CtxtFileMon.exe

;;
;; String Section
;;

[Strings]
Msft = "Siemens TTB"
CtxtFileMonServiceDesc = "CtxtFileMon Filter Driver"
CtxtFileMonServiceName = "CtxtFileMon"
CtxtFileMonRegistry = "system\currentcontrolset\services\CtxtFileMon"
CtxtFileMonMaxRecords = "MaxRecords"
CtxtFileMonMaxNames = "MaxNames"
CtxtFileMonDebugFlags = "DebugFlags"
CtxtFileMonAttachMode = "AttachMode"
Disk1 = "CtxtFileMon Source Media"

- Ashish


"Jeff McCashland [MSFT]" wrote:

> Michelle,
>
> In that case, I would suggest performing kernel-mode debugging on a checked
> build of your driver. You could step through your DriverEntry and
> AddDevice routines, or print debug messages from the routines to see if
> these complete successfully.
>
> What are the functions of your composite USB device? Do you have multiple
> INF files? Is it the parent device, or one of the child functions that
> fails install? How is the device being installed? I may be able to
> suggest more if I can look at your INF file(s) and a complete verbose
> (setting 0xffff) setupapi.log.
>
> Thanks,
> [MSFT] Jeff McCashland
> jeffm@online.microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no rights