NCSA Telnet Digest	Thursday, 11 Feb 1988		Volume 2 : Issue 3

Today's Topics:
			GatorBox hardware
			Keyboard Problems
--------------------------------------------------------------------------

From: timk@ncsa.uiuc.edu (Tim Krauskopf)
Date: Thu, 11 Feb 88 16:43:13 CST
Subject: GatorBox hardware


Has anyone seen the GatorBox hardware from Cayman systems?

We gotta keep track of our competition . . .

 Tim Krauskopf                                        timk@ncsa.uiuc.edu (ARPA)
 National Center for Supercomputing Applications      14013@ncsavmsa (BITNET)


--------------------------------------

From: gaige@ncsa.uiuc.edu (Gaige Paulsen)
Date: Thu, 11 Feb 88 17:00:50 CST
Subject: Keyboard Problems

Some people have complained about "keyboard problems" with version 2.0 and
2.1 of NCSA Telnet.   There are three major incarnations of this problem:
    1) You are not from the US and are having trouble getting your 
        keyboard to work in Telnet.
    2) You have a US System/Keyboard and are running under MultiFinder, but
        you have trouble using the Option key in other programs.
    3) You are using a foreign Mac and your keyboard gets confused when you
        are in and after you exit telnet.

Here are a few suggestions for the above problems.

    1) This is caused by an oversight of mine.  I had not considered foreign
        keyboards when I remapped the KB in Telnet to add the Option keys as
        control.  If you would like to make minor modifications to (or replace
        entirely) the keyboard map used by NCSA Telnet, please send me a note
        and I will see about getting you a copy of KeyMapper (a program which
        allows you to play with the keyboard resources).

    2) This is caused by a misinterpretation of the original MF documentation.
        Unfortunately, the keyboard is not switched according to application 
        and therefore it must be done manually when changing from active
        to suspended.  What this means to users is that you cannot use the
        option keys in other applications while Telnet is active.  To fix this,
        you can either wait for the next version of Telnet (that will be a 
        little while), or you can delete the 'KCHR' resource in your copy of
        NCSA Telnet using ResEdit.  The latter is actually a reasonable way
        to get rid of either problem #1 or #2.

    3) This is caused by another oversight and a bad assumption.  I had assumed
        that the default script for every country was 0, it is not.  Therefore,
        when I reset the key script back to 0, you are set to US mode.  I
        cannot actually condone this practice, but if you copy your country's
        KCHR resource to KCHR resource 0 in your system file, it will work
        correctly.  Another solution is to reboot after every use of Telnet.
        Another solution is to patch out the script manager calls in telnet.
        Etc, etc, etc.....


  Please note that all of these problems will be fixed in the next version
of NCSA Telnet, unfortunately the release date has not, as of yet, been
decided upon.


Good Luck,
Gaige B. Paulsen
National Center for Supercomputing Applications
gaige@ncsa.uiuc.edu