 |
 |
Articles / TULARC / Operating Systems / VCOMM / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
7.6: Init Order |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Operating Systems / VCOMM / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
7.6: Init Order |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the Programming VCOMM FAQ, by nelson@desktop.nsc.com (Taed Nelson) with numerous contributions by others.
[Contributed by Taed Nelson (nelson@lan.nsc.com).]
What is the proper device init order for a VCOMM port driver? The
documentation says to use UNDEFINED_INIT_ORDER, but SERIAL.VXD uses
VCD_INIT_ORDER. And in VMM.H, there is a PORT_INIT_ORDER defined, which is
just slightly less than VCD. Which is right?
This is an issue for any static port driver under Windows 95, and maybe every
port driver for Windows for Workgroups.
Continue to:
|
|
|
|
 |
|