Initializing Virtual Devices and Hooking Interrupts

Last reviewed: March 16, 1995
Article ID: Q74472

The information in this article applies to:

Microsoft Windows Device Driver Kit (DDK) for Windows versions 3.0 3.1

When initializing a device driver in the Microsoft Windows graphical environment, perform as much of the initialization as possible in the Device_Init phase. Code in the Sys_Critical_Init and Init_Complete sections should be minimal.

When the driver processes hooked interrupts, regardless of the initialization order value, all devices are called with Sys_Critical_Init before any are called for Device_Init. Therefore, regardless of the initialization order, all hooks done during Device_Init will occur after all hooks done during Sys_Critical_Init.

Additional reference words: 3.00 3.10 DDKVXD VxD hook interrupt
KBCategory: kbprg
KBSubcategory: D3MiscCoding

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 16, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.