HP3000-L Archives

July 1997, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lee Gunter <[log in to unmask]>
Reply To:
Date:
Wed, 2 Jul 1997 11:30:31 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Jim,

Make sure that, in your Modes function key definitions, Block Mode is
not enabled as a startup default.  Having Block Mode enabled upon
connecting to the system can cause the behaviour your seeing.

Lee Gunter          [log in to unmask]
Regence HMO Oregon


______________________________ Reply Separator _________________________________
Subject: [HP3000-L] TypeAhead
Author:  Jim Phillips <[log in to unmask]> at ~INTERNET
Date:    7/2/97 2:13 PM


Okay, the networking saga is over, at least for now! :-)

Here's what's happening with Typeahead.  Occasionally (I can't seem
to pin down the exact sequence of events that make it occur), when
I make the network connection and get the "MPE XL:" prompt, I can
press return and have the prompt repeat, but if I press any other
key, the keyboard acts like it is locked; that is, the bell sounds
and no character is echoed to the screen.  At first, I thought it
was typeahead because if I went into Terminal Setup/Keyboard and
removed the Typeahead, everything worked okay.  But now, I see that
it (Reflection) really doesn't care if I change anything.  Just
going into Terminal Setup and clicking OK is enough to "unlock"
the keyboard and everything is ok.  Not a big deal, I've already
learned to live with it.

Item #439 on today's glitch list! :-)

Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]      Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231

ATOM RSS1 RSS2