paul@aucs.UUCP (06/01/87)
I know this has been beat around the net before (I even saved a copy
which I now can't find), but I'll have to ask again. Is there anyway
to reliably turn off the cursor so that the controlling program doesn't
have to worry about it being off. I tried the tricks with setting the
cursor starting line to be greater than the ending line, which gives me
a double block cursor. I've also tried setting the starting the ending
lines to large values, which seems to have no effect at all. Even a bad
kludge will satisfy me, if one exists.
On an unrelated topic, I am writing a terminal emulator (I know, I know,
aren't enough out there already -- but this one is different) and I am
having trouble with handling com port interrupts reliably. I have tried
the talk program from MS-DOS Internals and have discovered an apparent
bug. While the interrupt program seems to work when its just reading
the com port and displaying on the screen, if I type on the keyboard
while the program is receiving a steady stream of characters, it seems
to loose an occasional character coming from the com port. This to me
is totally unacceptable. In interrupt mode the com port should never
loose characters, even when its a steady stream coming in at 9600 baud
while I'm typing 80 words per minute. Is this just another defect in
the PC's serial ports, or am I overlooking something?
Please send replies to me direct, and I'll post a summary if I get enough
responses. Thanks.
UUCP: {seismo|watmath|utai|garfield}!dalcs!aucs!Paul
BITNET: {Paul|phs}@Acadia
Internet: {Paul|phs}%Acadia.BITNET@WISCVM.WISC.EDU
PHONEnet: (902) 542-2201x587