 |
 |
Articles / TULARC / Operating Systems / VCOMM / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
10.3: PortEscapeFunction |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Operating Systems / VCOMM / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
10.3: PortEscapeFunction |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the Programming VCOMM FAQ, by nelson@desktop.nsc.com (Taed Nelson) with numerous contributions by others.
VCOMM.H defines and Serial.vxd supports more extended functions than are
described in the DDK. But the list of function of EscapeCommFunction (see
SDK) is shorter then corresponding DDK's list.
In the newer "Comm.doc" document, the escape functions are very well
documented. There is a minor error in that Serial.vxd does NOT implement
GETPORTHANDLE.
Continue to:
|
|
|
|
 |
|