GRIPS 2: Government Rast…rocessing Software & Data/GRIPS_2.cdr/dos/ncsa_tel/digests/v2.25

Text File | 1990-12-29 | 16.4 KB | 399 lines

NCSA Telnet Digest          June 7, 1989         Volume 2 : Issue 25
--------------------------------------------------------------------
Subjects:
    CAN character (hex: 18, Ctrl-X, dec: 24) goes from Tek to VT102
    MS-DOS version of the tar program available
    Status on 3C503 drivers, packet-driver version and NCSA's test version
    mkdir and rmdir problem
    comments on the care and use of trailers
    version questions
    Connection Closed...  press a key should be omitted
    TSR and co-resident versions?
    checksum errors causing problems
    command keys and pageup/pagedown in Mac version
    BICC driver anyone?
    Using the Set Aside.... option in SADE's MultiFinder with telnet
    PD SMTP available?
    Norwegian keyboard with KCHR removed
    2.3b4 hangs sometimes?

--------------------------------------------------------------------
Date:     Sunday, 21 May 1989 1630-EST
From: [e-mail]
Subject:  Tektronix control codes

Here are the control codes that my terminal emulators (YTERM from Yale
and KERMIT) use to switch to and from Tektronix emulation:

Begin Emulation: 0x1B 0x5B 0x3C 0x31 0x68
Return to VT102: 0x1B 0x18

I noted that NCSA telnet for the PC switches to Tek mode but does not
switch back.  I did not alter the host parameters from what works with
YTERM and KERMIT (what's listed above).

-----------------------------------------------------------------
Glenn C. Slayden                        Telephone: [phone]
Social Science Computing                   Bitnet: SSWS2@PENNDRLS
University of Pennsylvania     Internet: [e-mail]
-----------------------------------------------------------------


--------------------------------------------------------------------
From: [e-mail] (Rick Cochran)
Subject: graphics/text mode
Date: Mon, 22 May 89 17:03:19 EDT

> Date: Thu, 27 Apr 89 16:37:53 EDT
> >From: David B. Leonard <[e-mail]>
> Subject: Tektronix emulation
>
> Is there a plan or would it be too much to ask that the Tektronix emulation
> included in the most recent NCSA Telnet software have an instruction (escape
> sequence) for host-initiated switching back from the TEK mode to ANSI (VT102)
> mode?  Most of the PC-based TEK emulation programs and the commercially
> available emulation terminals do include this feature.

> [No plans yet, which sequence is a de facto standard?
> Tim K]

Please add me to the (I'm sure) extensive list of people who require this
feature.  I have always been astonished that it wasn't there to begin with.
As for which of the many non-standards to use: use any of the common ones
or, better yet, provide another configuration option.  (I'm sure you wanted
to hear that).

The ones I'm familiar with are:
      to graphics      to text            terminal(s)
    \e1        \e2        GraphOn, Selanar
    \e\\5        \030        Pericom
    \035 (implied)    \e"0g        Retrographics


Rick Cochran
Cornell Materials Science Center, E20 Clark Hall, Ithaca, N.Y. 14853
[e-mail] [e-mail] cornell!msc2.tn.cornell.edu!rick


--------------------------------------------------------------------
From: [e-mail] (David J. Camp)
Subject: Graphics off Character
Date: Sat, 20 May 89 19:58:36 CDT

The character that Kermit uses to exit graphics mode is 0x18 (hex 18).
I recommend the same be used by NCSA_Telnet.
-David-

Bitnet:   [e-mail]                ^      Mr. David J. Camp
Internet: [e-mail]    < * >    Box 8067, Biostatistics
uucp:     uunet!wucs1!wubios!david          v      660 South Euclid
Washington University (314) 36-23635               Saint Louis, MO 63110


[By popular demand, CAN (0x18) will detach the Tek window.
I believe this was in v2.2 for the PC already.
Tim K.]

--------------------------------------------------------------------
From: [e-mail] (David J. Camp)
Subject: MS-Dos tar program
Date: Sat, 20 May 89 20:09:09 CDT

An MS-Dos tar program is available via anonymous ftp at

wuarchive.wustl.edu (128.252.135.4).  Get the files
usenet/volume03/att_getopt.Z and
usenet/volume12/pdtar/part0?.Z

You will need Unix compress and sh to decompose these files, and a C
compiler on your PC to compile them.  I could make the compiled
executable available if there is a demand.  One drawback is the MS-Dos
tar command does not understand wildcards.
-David-

Bitnet:   [e-mail]                ^      Mr. David J. Camp
Internet: [e-mail]    < * >    Box 8067, Biostatistics
uucp:     uunet!wucs1!wubios!david          v      660 South Euclid
Washington University (314) 36-23635               Saint Louis, MO 63110

--------------------------------------------------------------------
From: [e-mail] (David J. Camp)
Subject: 3c503 NCSA_Telnet NOW
Date: Sat, 20 May 89 20:32:54 CDT

I think there is a way you can run NCSA_Telnet on a 3C503 card now.
First do an anonymous ftp to sun.soe.clarkson.edu (128.153.12.3) and
'cd /pub/ka9q' and 'binary' and 'get drivers.arc'.  Next anonymous ftp
login to 'omnigate.clarkson.edu' (128.153.4.2) and 'binary' and 'cd
/pub/ncsa2.2tn' and 'get ncsabin.tar'.  Use tar and arc to extract the
contents, and you are set.  This version of NCSA_Telnet supports the
packet driver, and the 3C503 driver is in drivers.arc.  I have not
actually done it this way, since I do not have a 3C503.  Kudos to Brad
Clements at Clarkson University for developing this version of telnet,
which has a number of advanced features.  I think the screen colors are
a little weird, at least in the last version I tried.  I could not read
the dim yellow characters that I get under certain common conditions.
-David-

Bitnet:   [e-mail]                ^      Mr. David J. Camp
Internet: [e-mail]    < * >    Box 8067, Biostatistics
uucp:     uunet!wucs1!wubios!david          v      660 South Euclid
Washington University (314) 36-23635               Saint Louis, MO 63110

Date: Sat, 20 May 89 22:06:51 EDT
From: Russ Nelson <[e-mail]>
Subject: NCSA Telnet Digest V2.24 (long)

   [The beta version for the LocalTalk drivers is posted in the contributions
   directory.  We are working on the 503 driver, requests for it are reaching
   the level of ONE PER DAY.  The costs of being popular...
   Tim K.]

Why not just tell people to use the packet driver version?  We have a
3c503 driver.  The next release will have a 3c523 driver also, thanks
to ddl@harvard.*
-russ


[ Yes, there are two available versions of NCSA Telnet, one from
each of us.  We are working on incorporating many of Clarkson's
features into our next release (not tn3270 though).  This includes
the 3C503 driver which is now available for testing.

In the NCSA_Telnet/contributions directory, the 3C503 driver and a v2.2
binary which has the 503 driver in it, can be downloaded.  This is
a test version, our v2.3 release won't be out until later this summer.
If you help test it now, it will help ensure a reliable v2.3 release.
Tim K.]


--------------------------------------------------------------------
Date: Tue, 24 Jan 89 17:11:39 CST
From: [e-mail] (David J. Camp)
Subject: mkdir and rmdir broken

Bugs,
     I am connecting two PS/2's with NCSA_Telnet.  Both have UB cards.
One is a Model 70 acting as a server, and the other is a model 60.
When I run ftp and enter '?' I get a list of commands that includes
both mkdir and rmdir.  When I try to use these commands, it says:

          500 Command not understood
          Trying again...
          500 Command not understood

It seems like these commands should work.  It is strange that they
appear in the help when they do not actually work.  Is this because they
will work on systems that are not running NCSA?
-David-

Bitnet:   [e-mail]                ^      Mr. David J. Camp
Internet: [e-mail]    < * >    Box 8067, Biostatistics
uucp:     uunet!wucs1!wubios!david          v      660 South Euclid
Washington University Medical School               Saint Louis, MO 63110


[ Just because the ftp client supports them and prints them in ITS
help message doesn't mean that we support it in the server.  Try
> quote HELP
to see which FTP protocol commands the server supports.  Tim K]

--------------------------------------------------------------------
Subject: Trailers (NCSA Telnet Digest V2.17)
Date: Wed, 08 Feb 89 22:31:53 +1100
From: Robert Elz <munnari![e-mail]>

    From: timk (Tim Krauskopf) (in V2.17)
    Subject:  Ultrix uses trailers by default: warning

    NCSA Telnet can't deal with trailers and they have questionable
    benefits for the system, so let's all turn them off.

The benefits of trailers are not so much questionable, but
variable - for some systems they are a performance win, for
many, they cause performance losses.  It happens that VAXes
(with their 512 byte pages) are one system that can benefit
from trailers, so its not surprising that Ultrix has them on
by default (as does standard BSD on vaxes).

Turning trailers off everywhere is one solution to this problem,
you take a small performance loss on receiving packets on systems
where they are helpful (nb: only on receiving) and avoid problems
with lots of systems that don't handle them.

However, you then have to remember to disable trailers on each
new system that you add to the net, lest that one have trouble
communicating with systems that can't process trailers.

New versions of BSD do "trailer negotiation" and transmit trailers
only to consenting systems (so they only get sent to systems that
really do get the performance gain from them).  However its going
to be a while until systems with this capability are really
widespread.

In the meantime, I strongly suggest that NCSA Telnet adopt support
for incoming trailer packets - the code to do it is trivial (yes,
just half a dozen lines or so).  Adding this support is likely to
be much less effort than continually responding to queries from
users who are having the rather weird problems that failure to
receive trailer packets bring.  Also, remember that someone installing
NCSA telnet on a Mac or PC is not necessarily going to have any
ability to alter the configuraion the local Ultrix (or other)
large system that is exploiting trailers.

I have a standalone system that receives trailer packets, and does
it for just this purpose.  Its a performance loss, but I don't
mind that, at least it works (that is, I don't have to waste my
time sending "turn off trailers" messages to half of the universe).

I will be willing to send this to anyone with the ability to
install it in the NCSA telnet code (it will obviously require
modifications).

It doesn't send trailers (ever), and it doesn't do trailer negotiation
(so newer systems don't send trailers to it), however, if a trailer
packet is sent unannounced, it will process it correctly.  This is
the same strategy used by many systems that don't benefit from trailers
(eg: Sun workstations).

If you do decide to disable trailers then ...

    Change all machines at once, they must match in their
    settings for trailers.

is not necessary.  You need to disable trailers on all machines
that will be transmitting directly to NCSA Telnet, or to anything
else that can't handle trailers, however, hosts with trailers on,
and others with them disabled (probided they have trailer capability
at all) will interoperate quite nicely.

Robert Elz        [e-mail]


--------------------------------------------------------------------
From: [e-mail]

Date: 07 February 1989, 17:07:46 GMT
From: Darrell Skinner           69418200 ext 21-54   PMIDS    at FRPOLY11
Subject: NCSA_Telnet distribution, TN3270, GatorBox, etc.

All my questions concern NCSA_Telnet for the Macintosh.

1) Have you developed a distribution channel for NCSA software
outside ARPANET (mail server, BITNET file server, etc.)?

2) What is the current version of NCSA_Telnet?

3) It is evident from the recent NCSA Telnet Digests that there
is considerable interest in the TN3270 emulator (I managed to
live years and years in the U.S. without having to deal with
IBM machines, but there are environments--where I am now, for
example--where you can't avoid them ...).  In the announcement
for TN3270 (posted somewhere by Peter DiCamillo [e-mail]),
> The NCSA Telnet Digest will be used for discussing issues related
> to tn3270, as well as NCSA Telnet.  To subscribe ...
which is how I learned about this digest.  But in recent digests,
> NCSA does not plan to support tn3270 in any way.  We redistribute Brown's
> version ...
Perhaps you could permit discussion of tn3270?  It would be
especially nice if Brown could provide NCSA software on their
BITNET file server.

4) The GatorBox from Cayman is supposed to emulate the Kinetics
FastPath.  Has anyone used NCSA software across a GatorBox?
Does it work well?

Thanks ...  Darrell Skinner    [e-mail] (or .EARN)
            Labo PMI / Ecole Polytechnique / Paris (close enough) France

[NCSA Telnet for the PC
 NCSA Telnet for the Macintosh
 current releases are v2.2, July, 1988
 Version 2.3b4 for the Mac is in testing.
 Version 2.3 beta for the PC should start testing sometime in June.

 Cayman distributes NCSA Telnet v2.2 with the GatorBox - it works fine.

 I promise not to censor any Brown, BYU, tn3270 or Clarkson version (or
 other derivatives) messages from this list.  I'm not that great at getting
 the list out every week, but I'm trying.

 Tim K]

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

From: [e-mail] (David J. Camp)
Subject: Closed Connection
Date: Thu, 16 Feb 89 20:49:30 CDT

I suppose there may be other schools of thought about this, but I do not
like the "Connection closed, press a key . . ." prompt.  I suppose it
would be useful under circumstances where your connection was closed
inadvertantly, but for normal logouts it it bothersome.
-David-


[I like it a lot.  It could become a user option, I suppose.
Tim K]

--------------------------------------------------------------------
Date: Mon, 20 Feb 89 08:00:42 MST
Subject: Questions & development

Hi all, I have a question:

Is anyone working on a version of NCSA Telnet that will coexist with Network
Software like 3com or PC-NFS? It is my understanding that the current version
grabs control of the Ethernet Card and monopolizes it until it is finished.

BTW, I am working on a TSR version of Telnet.  I would appreciate any comments
suggestions, sympathetic remarks, help etc. Tim, please add me to the
developers mailing list in this regard.  (I am using MSC 4.0)

Patrick Gaughan        Programmer of Gor
[e-mail]    New Mexico State University



--------------------------------------------------------------------
Date: 22 May 89 13:59:00 EST
From: "GEG" <[e-mail]>
Subject: Suggestions for telnet

After using telnet for a short time, I find that I miss not being able
to use the page up and page down keys on my Mac II keyboard to look
through the scroll area.  I also miss the "hot-keys" for copy and
paste.  These are nice conviences that you might concider adding.


[The command keys are all available, if you want them, make sure you turn
command keys on in the preferences dialog.
Tim K]

--------------------------------------------------------------------
Date: Tue, 23 May 89 15:40:49 EDT
From: [e-mail] (Frank Terhaar-Yonkers)
Subject: bad checksums ...

Howdy,
    Just Installed 2.2 on a PC/XT clone using a WD8003.  I'm getting
extremely poor performance cause of (I think) lots of bad TCP (and a
few IP thrown in) checksums.  At times it appears the PC won't respond at all.
Any clues on where to start looking for the problem?  The local network people
say they'll get a monitor out here someday ...

thanks
Frank Yonkers   [e-mail]

[Check for a hardware interrupt or I/O address conflict and see if
you can check the integrity of your network.
Tim K]

--------------------------------------------------------------------
Date:     Tue, 23 May 89 10:13:51 BST
From: [e-mail]
Myname:   John Heaton (061 275-6011)
Address:  NRS Central Administrator, MCC Network Unit (G45)
          The University, Oxford Road, Manchester, M13 9PL.
Subject:  BICC driver re