Please help with Response Time and Screen Views

0 views
Skip to first unread message

Kyu Rhee

unread,
Dec 12, 1999, 3:00:00 AM12/12/99
to
Hi there

We have a SCO UNIX application in which we use the [Esc] key to view the
previous screen. For some reason, it takes consistently up to half a second
before the previous screen shows up. Server connection is via a 57800
serial line.

Furthermore, each screen does not appear all at once but scrolls down.

Thanks for your help.


Kyu Rhee
http://www.infouser.com
Email: rh...@ozemail.com.au

Unknown

unread,
Dec 12, 1999, 3:00:00 AM12/12/99
to

Kyu Rhee <rh...@ozemail.com.au> wrote in message
news:zUZ44.1531$Dh3....@ozemail.com.au...
Kyu R

Does the problem ONLY occur when you use the ESC key, or does it occur
during other "screen refresh" functions. The reason I ask? I experienced a
overall proformance problem when a client had a conflict between the serial
controller and scsi controller.... Also check your tthog settings.

Joe H.

David M. Fenske

unread,
Dec 13, 1999, 3:00:00 AM12/13/99
to
In article <zUZ44.1531$Dh3....@ozemail.com.au>,

"Kyu Rhee" <rh...@ozemail.com.au> wrote:
> Hi there
>
> We have a SCO UNIX application in which we use the [Esc] key to view
the
> previous screen. For some reason, it takes consistently up to half a
second
> before the previous screen shows up. Server connection is via a 57800
> serial line.
>

It depends on how the escape key is read and processed. In Unix, the
escape key sends a single character. Functions keys (on some terminals)
send three characters, the first of which is an escape. I have seen
some applications which take a fair amount of time to differentiate
between a single character escape and a three character fucntion key.
1-2-3 for Unix was a prime example. This may be normal behavior for
your application. What type(s) of terminals are you using?

As for the other delays, not all serial boards are good for continuous
high speeds. Additional memory and/or kernel tuning may be in order.


Sent via Deja.com http://www.deja.com/
Before you buy.

Tony Lawrence

unread,
Dec 13, 1999, 3:00:00 AM12/13/99
to
Kyu Rhee wrote:
>
> Hi there
>
> We have a SCO UNIX application in which we use the [Esc] key to view the
> previous screen. For some reason, it takes consistently up to half a second
> before the previous screen shows up. Server connection is via a 57800
> serial line.

You've given very little informmation here, and that's
foolish, because it's quite possible that you could get an
immediate fix if we knew what this mysterious application
is.

For example, there are several common applications that use
"ESC", but will also work (and will work instantly) with
another key: sometimes TAB or F12. Sometimes the app can be
specifically told to recognize another key- but how would we
know, since you just say it's a "SCO Unix application".

I'm sorry, maybe I'm just extra grumpy this morning, but I'd
really suggest that you identify the app- I bet it's
RealWorld or Mas90?

The reason for the ESC problem is that most terminals use
ESC as the "lead in" sequence for other keys. For example,
F1 actually sends ESC-[-M on an ansi terminal. Because of
this, when an application sees ESC, it has to wait to see
what follows to determine whether or not this is just RSC or
a function key. Many, many apps handle that wait poorly,
and no doubt that's the source of your problem.


>
> Furthermore, each screen does not appear all at once but scrolls down.

And again you haven't given enough information. Slow
scrolling can be as simple as having your terminal set to
"smooth scroll" rather than "jump scroll". But we don't
know if you have terminals, telnet connections, or what, so
we can only guess. You also don't indicate whether or not
this occurs only in this app, which is a rather important
omission.


--
Tony Lawrence (to...@aplawrence.com)
SCO articles, help, book reviews, tests,
job listings and more : http://www.ApLawrence.com

Roberto Zini

unread,
Dec 14, 1999, 3:00:00 AM12/14/99
to

This could be noticed while using cursor keys while in a vi(C)
session 'trhu a telnet connection to another machine; in fact,
while some commands get recognized, very often you could hear
a "beep" tone which is the way used by vi(C) to inform you that
it's been unable to process the command (for the reasons given
above). In vi(C) there's a simple solution; hit the ESC key,
press ":" and type "set noto" (no double quotes) + ENTER.

I'm not sure about your problem; I seem to remember that a long
time ago I was being told by a cobol programmer you could do
the same trick accordingly to the cobol you were using but
presently I'm unable to provide you with additional info :-(

Best,
Roberto
--
---------------------------------------------------------------------
Roberto Zini email : fr...@strhold.it
Technical Support Manager -- Strhold Sistemi EDP Reggio Emilia(ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)

Reply all
Reply to author
Forward
0 new messages