While everyone else is away at HP World, and because we're getting ready to
release a newer version of QCTerm, let me ask a question of those who had to
stay behind.

Up to now, we've been putting QCTerm together using Visual Basic 3.0. Doing
this allows us to create a single version that will run on both Windows 3.x
and 95/98/NT machines. There is some real benefit to this -- but the penalty
is that we can't natively compile QCTerm if we continue to use VB 3.0.

However, if we translate the code to VB 5.0 (or 6.0), we can compile QCTerm
and, in places, thus get a 20 times speed improvement in execution. The
overall effect is that compiling QCTerm under VB5 should make us completely
competitive in speed with Reflection -- and I hate not being fully
competitive.

The penalties associated with doing this however are: (i) QCTerm's deliverable
code will be larger (by how much, I don't know), and (ii) QCTerm will no
longer be able to be run on Windows 3.x machines. We will be constrained to
95/98/NT devices.

Thus the choices are:

     1. Compatible everywhere -- but slower everywhere.

     2. Run only on 95/98/NT -- but substantially faster.

I would greatly appreciate any comments that you might be moved to make.

Wirt Atmar