As the developer of MiniSoft 92, I'd like to respond to some of the points
raised recently.

In the first place, MiniSoft 92 was designed to be an HP terminal emulator,
not a Reflection emulator.  Software that was designed to run on an HP
terminal runs perfectly on MiniSoft, but there have sometimes been problems
when vendors have written software specifically to run on Reflection.  We
have gotten around most of these problems by supporting certain Reflection
escape sequences, and in  many cases vendors (sometimes under pressure from
their customers) have modified their code so that it works equally well on
MiniSoft.  There are very few cases indeed now of software that has been so
specifically written for Reflection that it will not run on MiniSoft.
There are still some hold-outs, and if I were a customer of a vendor  who
had locked me into using a high-priced terminal emulator with no
alternative, I would not be a happy customer.

As far as local printing is concerned, these problems have  only arisen
when host software sends embedded printer control sequences as part of a
print stream.  Microsoft Windows strips out these escape sequences because
it was designed to handle many different printers and wants to be told when
to start a new page etc. so that it can send the  specific control sequence
for the selected printer.  To get around this "feature" of Windows required
going through some extraordinary hoops, and then some additional  hoops
since this was one of the areas where Windows 95 was not "upwardly
compatible" with Windows 3.1.  However, we have solved the problems and can
happily pass through print streams with embedded graphics, font changes and
so on.

As I am sure our customers will confirm, we do our best to  "try harder"
and to provide a terminal emulator that is efficient, attractive and easy
to use and we work hard to ensure that we handle promptly any questions
that arise.

Peter W Gofton