🚀 go-pugleaf

In article <1990Dec31.090454.13869@ecst.csuchico.edu> madams@ecst.csuchico.edu (Michael E. Adams) writes:
$  Good posting!  I liked what you had to say, but my DOS reference
$guide seems to think that int 0Fh should be AVOIDED!
[...int 0Fh may not come from the printer port...]

   Hmm, that sheds new light on the situation :-)  Well then, I suppose one
could still use an int 0Fh routine; you'd just have to make sure you checked
the printer port's status every time before trying to send a character (which
would be a Good Thing to do anyway).  And perhaps a clock tick hook would
also be useful in case an int 0Fh failed to get through.
-- 
 __            __  _  | ...!nexus.yorku.edu!xrtll!silver |  always
(__  | | |  | |_  |_) >----------------------------------< searching
 __) | |_ \/  |__ | \ | if you don't like my posts, type |    for
_____________________/  find / -print|xargs cat|compress |   SNTF