Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!HNYKUN51.BITNET!TOXI_CE
From: TOXI_CE@HNYKUN51.BITNET
Newsgroups: comp.sys.atari.st
Subject: problems with uniterm
Message-ID: <8904151026.AA10402@ucbvax.Berkeley.EDU>
Date: 14 Apr 89 17:06:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 52

Distribution-File:
        "info-atari16@score.stanford.edu"

I tried to send this message directly to Simon Poole, but probably
did not succeed. (Is that your real BITNET address, Simon?).


1) I am using UniTerm (V2.0e-010)at 9600 baud on a 1040 STf with TOS 1.2. I
like UniTerms feature to position the cursor with the mouse. However this
feature does not allways work. I tried to chance the mouse respons with the
control panel, but that does not seem to make a lot of difference. What does
make a difference is entering UniTerms help menu (you must choose one of the
menu options actually). When you do that double clicking suddenly starts to
work.

2) We did find a small problem in the XON/XOFF protocol. When we use
the XON/XOFF protocol (because we use the connected printer) problem occur
when the computer is turned off or reset after an XOFF has been send. When
UniTerm is restarted, no XON will be send. And the host will keep waiting
for it. It is possible to overcome this problem by using hold screen. When
hold screen is released, UniTerm does seem to send an  XON. Maybe it would
be a good idea to have UniTerm send an XON after a reset.

3) I tried to use the write to VDI device option (and succeeded). However, I
have a few questions remaining. Why does UniTerm need device 00 as screen,
other applications use either 01 (the default screen; Timeworks does this) or
look for the actual resolution and use the corresponding sreen-driver (Eazy
draw does this). UniTerm will not work when device 00 is not known (it will
even say that GDOS is not loaded, while it is and while both EAZY DRAW and
Timeworks work correctly). After I put 00 in the assign.sys file it worked
allright. However, text (written with the Tektronics font, not as vectors)
was not printed. I did put the Timeworks fonts in the assign.sys file,
both with the printer driver (LQ800.sys from timeworks for a NEC P6 printer),
and with the three screen drivers. Am I doing something wrong? Or does the
write to VDI device function ignore text.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

                             Chris Evelo

                             TOXI_CE@HNYKUN51 (BITNET/EARN)
                                 |
                                 an underscore _ not -.

                Mail adress: Department of Toxicology
                             University of Nijmegen
                             Kapittelweg 54
                             6525 EP Nijmegen
                             The Netherlands
                             tel. 080-517184/514206

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++