forcing reboot in protocol driver installation

Is there a directive for a protocol driver inf file that I can use to force a reboot? This is for Windows NT/2000/XP. I know I have seen these types of drivers ask to reboot after they are installed but I can't find in the DDK help how to do this.
Thanks,
Dave

bburgin
Fri Oct 24 15:09:40 CDT 2003

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


Why would you want/have to do this?

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_13DDE292
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
\par Why would you want/have to do this?
\par
\par Bryan S. Burgin
\par bburgin@microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_13DDE292--

Tarundeep
Mon Oct 27 03:41:01 CST 2003

exactly , there is no need what i have implemented.
Can you be more clear of the problem.as to why you want a reboot.
REgards
Tarun

--
Tarundeep Singh Kalra
(tarundeep1976_nospam_at_yahoo_dot_nospam_dot_com)

""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:1ILPCrmmDHA.576@cpmsftngxa06.phx.gbl...
>
> Why would you want/have to do this?
>
> Bryan S. Burgin
> bburgin@microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.

anonymous
Tue Oct 28 09:06:10 CST 2003

Our protocol driver needs a reboot in order to work - is this a problem in itself? I always thought the driver needed a reboot to load in Windows.

Eliyas
Tue Oct 28 10:52:23 CST 2003

I guess the last OS you worked on was NT4.0 - even there I believe protocols
drivers can be dynamically loaded.

Tell us why your protocol driver needs a reboot.

Read this section
http://msdn.microsoft.com/library/en-us/install/hh/install/install-over_7lgn.asp

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

Tarundeep
Wed Oct 29 02:27:50 CST 2003

exactly,
it is not necesary to reboot , why you wanna do it.
just start the driver dynamically
i faced the same problem
do net start protocl name
and be sure that INF file contains entries for AutoStart

--
Tarundeep Singh Kalra
(tarundeep1976_nospam_at_yahoo_dot_nospam_dot_com)

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:OX7ZdPXnDHA.3504@TK2MSFTNGP11.phx.gbl...
> I guess the last OS you worked on was NT4.0 - even there I believe
protocols
> drivers can be dynamically loaded.
>
> Tell us why your protocol driver needs a reboot.
>
> Read this section
>
http://msdn.microsoft.com/library/en-us/install/hh/install/install-over_7lgn
.asp
>
> --
> -Eliyas
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
>
>

bburgin
Wed Oct 29 11:45:41 CST 2003

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

Or, instead of needing Net Start Xxx, change the startType in your INF from
3 to 2 ("StartType = 2 ) -- if this is a problem of his protocol not
starting up automatically.

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_E15FB253
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 Or, instead of needing Net Start Xxx, change the startType in your INF from 3 to 2 ("StartType = 2 ) -- if this is a problem of his protocol not starting up automatically.
\par
\par Bryan S. Burgin
\par bburgin@microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_E15FB253--