 |
 |
Articles / TULARC / Operating Systems / VCOMM / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
8.3: HyperTerminal Allocates No Buffers |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Operating Systems / VCOMM / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
8.3: HyperTerminal Allocates No Buffers |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the Programming VCOMM FAQ, by nelson@desktop.nsc.com (Taed Nelson) with numerous contributions by others.
[Contributed by Mike Melo and Michael Grabelkovsky (michael@slink.co.il).]
HyperTerm has problems when configured to use "Direct to COMx". The port
driver only receives a single PortSetup call, and TxQueue and cbTxQueue are
both zero.
It's undocumented, but SERIAL.VXD includes special support for this case. You
can look at the SERFUNC.ASM module, function PortWrite. The code is
understandable.
Continue to:
|
|
|
|
 |
|