Wyse 60/VPIX Problem

[Mark J. Bailey]

In article <115 at ubbs-nh.MV.COM>, noel at ubbs-nh.MV.COM (N. Del More) writes:
> I am experiancing a problem with running VPIX (Update A) from a remote
> terminal that I did not have under the previous release.
> 
> Everything seems to work nicely on the console, however, when attempting
> to run the same program from a remote console attached to either the
> standard serial port or the Digiboard Com/8i I experiance a problem that
> manifests itself as a failure to update and/or clear the screen.  The
> program (Quicken version 2) is not configured for graphics etc.
> 
> If I enter a command nothing appears to happen, but if I call up the vpix
> menu and then escape the screen is updated.  
> 

Hi,

I have experienced the very same pheonomina you are describing.  I noticed
it with the small modem PD vi clone that come across comp.binaries.ibm.pc
a while back.  In the past, it has worked like a charm.  But now, when I 
go into it (also same effect with QEDIT), the cursor just sits at the top
and goes NOWHERE!  Then something causes it to update the screen (a timer
alarm possibly?) and the cursor jolts across the screen to the possition
it should have been at according to the keystrokes I have typed in between.
Believe me, this WILL NOT DO!!!  I am wondering what other applications
will be affected by this.  It behaves like the screen is locked up.  And
what is really interesting is that while the cursos is stuck, I can hit the
':' to go into the sub-command mode and it pops up almost immediately.
So the problem has to do with when the editor is in its "full screen" mode,
ie, when the cursor tracks anywhere across the screen using the arrow
keys.  Again, this very same behavior with QEDIT.  It does not happen with
XTPRO's builtin editor.  I might add that my serial terminal is also
a Wyse 60, and I am running VP/ix on both a standard serial port and a
Wyse 995 8 port smart board.

It has to be something with respect to a particular mode that both the 
vi and QEDIT enter at the points they get stuck.  I wonder how after so
many long months of delays and testing, that SCO would let a bug like 
this out?!!?!?!?!  >:^()  Well, all I know is that it could cause some
MAJOR problems, say, if an important application fouls up.  

Anyway, you are not alone.

Mark.


-- 
Mark J. Bailey                                    "Ya'll com bak naw, ya hear!"
USMAIL: 511 Memorial Blvd., Murfreesboro, TN 37129 ___________________________
VOICE:  +1 615 893 0098                            |         JobSoft
UUCP:   ...!{ames,mit-eddie}!attctc!mjbtn!mjb      | Design & Development Co.
DOMAIN: mjb at mjbtn.MFEE.TN.US                       |  Murfreesboro, TN  USA