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

Text File | 1990-12-29 | 13.1 KB | 311 lines

Subject: NCSA Telnet Digest V.II-I.9
--------------------------------------------------

NCSA Telnet Digest    Tuesday, 16 August 1988    Volume 2 : Issue 9
-------------------------------------------------------------------
          NCSA Telnet 2.2 Thanks and suggestions
               Telnet 2.2 vs. Brown tn3270
                  Ftp from VM to Mac
             Problems w/Mac 2.2
           telnet for a 512K Mac
             tn3270 for the Macintosh
            NCSA Telnet under MSC 5.0 (or 5.1)

-------------------------------------------------------------------
From: John Silva <[e-mail]>
Subject: NCSA Telnet 2.2 Thanks and suggestions
Date: Wed, 13 Jul 88 14:36:11 EDT

To NCSA gurus :

   Thanks for the Version 2.2 of Telnet !!!  This addressed a problem I had
with running the Version 2.1 of Telnet [using domain lookup] with our
nameserver, Bind version 4.8.  When I initially setup Telnet, I was running
version 4.7 of Bind and it worked fine, but as soon as I upgraded to Ver 4.8
it stopped working (just the domain lookup part, I could still connect if
I used IP address or an entry in the CONFIG.TEL file).


Now for my wish list of features to add (if your'e looking for some 8-) :

  Would it be possible to pass a socket number to the Telnet program ??
  (e.g.  'telnet nsca.uiuc.edu 25'  to connect to the SMTP socket)

  Do you have any plans to implement BOOTP ??

  Could a higher tracing level be provided for the domain lookup sequence so
  that the fully-qualified domain that is being queried is shown, along with
  the nameserver that it is querying ??


  Thanks Again for a fine program  (that fills a niche !!),

    John Silva
    Network Administrator
    Hewlett-Packard
    Waltham, MA

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

From: "Collins, Herman" <[e-mail]>
Subject:      Telnet 2.2 vs. Brown tn3270
Date:         Thu, 14 Jul 88 16:40:15 EDT

I picked up the Mac version of the Telnet 2.2 (thanks!), and it seems to
have some neat features, but at least some of the new "config.tel" parms
are not compatible with the Brown tn3270, either the 1.75 version that I
had, or the 1.83 version that I got from your archives.

Are you (or is somebody) going to integrate the tn3270 stuff with the
regular Telnet stuff?  Will it become part of the PC version, too?
(Please?)  Since I do much work on an IBM 3090, I use the tn3270 most
of the time, but I like the multiple sessions and other features of
the NCSA Telnet.  So, I have to keep both around, and switch back and
forth...

One small additional note:  Page 1.4 of the documentation says that the
diamond meZJs that Telnet is checking the nameserver, and the circle
means Telnet is trying to open the session.  The figure 1.5 on the next
pages says exactly the opposite.

                                    Herman Collins

128 McVey Hall                      Bitnet: SYSHERM@UKCC
University of Kentucky              Internet: [e-mail]
Lexington, Ky.  40506-0045          Phone: [phone]

"Cats will be cats, and cats eat birds."

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

From: Benzi mizrahi <[e-mail]>
Subject:      Ftp from VM to Mac
Date:         Wed, 20 Jul 88 08:00:31 +0300

Hello,

  I hope somebody will read this, because I don't know if
  I am subscribed to this list.
  As you can see from the subject line, we have problem
  FTPing from VM mainframe to Mac, using WISCNET tcpip package
  ( I think it's also true for FAL), I think mainly because
  VM FTP does not have the UNIX like option 'FTP -n ...'.
  Needless to say that we gain accsess to VM from Mac Se,
  with NCSA Telnet .
  Is there anything that can be done to solve this problem,
  I mean WISCNET FTP client ( in the VM ) wants a username
  when we ftp to the Mac, now I know nothing about Mac's ,
  but can such username be supplied in the Mac software or
  in the NCSA Telnet.

  Thanx in advance, Benzi
                    VM System Programmer
                    VMS System Manager & Programmer :-)
[ - Ed. Note -
[ NCSA Telnet version 2.2 has an undocumented feature in that
[ the insertion of the \i sequence within any macro will cause
[ the IP number of the current machine to be sent.  This is edited
[ and maintained as the \i and therefore should work regardless of
[ whether you move to another mac or not, as long as you load the macro
[ My suggestion would be to set up a macro key as "ftp \i" and save the
[ set.
[    - Gaige ]

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

From: David Lassner <[e-mail]>
Subject: Problems w/Mac 2.2
Date:     Mon, 1 Aug 88 00:54:00 HST

I'm having a couple of problems with Telnet that I hope someone can
help me with:
1) I have a password file and the config parameter points to it.  It
works fine the first time I connect back to my Mac and login with a
name and password.  However usually the second time I try to start an
FTP session between my host and my Mac the login is rejected.  If I
restart Telnet it seems to be fine.  Quitting ftp on the host (Vax/
Ultrix2.2) doesn't help any.  Any ideas?
2) I like the Monaco 12 pt font, but when I connect to our IBM host
through a protocol converter (Series/1) all the enhanced text (almost
everything the host sends) is mapped to bold.  And Telnet doesn't
display it properly on receipt.  Letters overstrike as if there were
a kerning problem of some kind.  But if I change fonts and then change
back to Monaco12 the display looks fine.  Any ideas?
Thanks, David
UH Computing Center
[ - Ed Note -
[ Problem 1 is caused because you do not have a full pathspec for the
[ password file (or perhaps I should say that it can be remedied with
[ the addition of a full pathspec.  If your password file is in the
[ NCSA Telnet folder on the disk HD20 and is named passwd, you should
[ set up your password file to be "HD20:NCSA Telnet:passwd" (quotes are
[ necessary because of the space between NCSA and Telnet.
[ Problem 2 is one of those Aesthetic problems which we described in
[ the manual.  The best way to remedy it is to define a font which is
[ 12 points and maps directly to the Monoco 12 font except that it is
[ bold.  This, in turn, can be added to the FOND resource in NCSA Telnet
[ so that the system will always use the special font for bold Monaco
[ when it is in Telnet.
[  - Gaige ]

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

From: [e-mail] (David Ragozin)
Subject: telnet for a 512K Mac
Date: Thu, 4 Aug 88 19:46:09 PDT

One user on our phonet has a 512K Mac. Until this is upgraded to a Plus,
is there any interim solution to "How can I telnet to other machines?".
We have a FastPath box and all our other phonet users are making excellent
use of Version 2.1 of NCSA_Telnet.

(I assume from the 2.2 "info.sheet" that version 2.2 will not help us with
the 512K Mac.  Is that correct.).

Thanks.
[ Ed. Note -
[  Unfortunately, your assumption is correct.  we have made use of some
[  features not present on the 512k mac roms, and therefore will not work
[  on any machine below the 512ke (and that is tight because of memory).
[ - Gaige ]

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

From: Peter DiCamillo <[e-mail]>
Subject:      tn3270 for the Macintosh
Date:         Mon, 08 Aug 88 03:09:52 EDT

Please forgive the posting of this announcement to several relevant
distribution lists.

The first release of Brown University's tn3270 for the Macintosh is now
available.  This program consists of the NCSA TCP/IP kernel by Tim
Krauskopf and Gaige B. Paulsen, Telnet 3270 option negotiation code
developed by Greg Minshall at Berkeley, and 3270 emulation and Macintosh
user interface code developed at Brown.  It allows a Macintosh with a
TCP/IP connection to access a host as a full-featured 3270 terminal.
tn3270 is available via Internet anonymous FTP, over BITNET, or from
Brown for a small distribution fee.  Details of tn3270's features and
availability are provided below.

NETWORK FEATURES

tn3270 includes all the features of version 2.0 of the NCSA TCP/IP
kernel.  These include support for both Ethernet connections and
LocalTalk connections via a Kinetics gateway, a built-in FTP server,
and domain nameserver support. Also, tn3270 supports dynamic IP number
assignment when a Kinetics gateway is running KIP code, and allows the
user to override the default Telnet terminal type and port number.

EMULATION FEATURES

On all Macintoshes, tn3270 emulates a 3278 with extended highlighting,
APL, and the APL/Text character set.  In addition, most graphics
capabilities of a 3179 G or PC/GX are emulated.  tn3270 also supports
several 3270 enhancements, including typeahead and special blank
processing.

On a Macintosh II (or other Macintosh with color Quickdraw) tn3270
supports 3279 base color, four color, and eight color text, and eight
color 3179 graphics.  On Macintoshes with large screens, tn3270 supports
either 9 or 12-point text for 24 lines, and 32 lines using 9-point text.

Although primarily a 3270 emulation program, tn3270 also provides basic
line mode Telnet support, and emulates a VT-52 terminal.

MACINTOSH FEATURES

tn3270 allows the 3270 cursor to be moved with a single mouse click, and
allows the user to set the function of a double mouse click.  Full
MultiFinder support is provided, and on color Macintoshes the standard
color picker may be used to set any screen colors.  tn3270 utilizes
offscreen bitmaps for fast, flicker-free screen refreshing.  The speed
of tn3270 can approach that of a locally-connected 3270, with updates
as fast as two screens per second.

SPECIAL FEATURES

In addition to FTP server support, special support is provided for
VM/CMS file transfer.  Easy-to-use CMS RMAC and WMAC commands may be
used to upload and download files during a CMS terminal session
through the Telnet connection.  Data transfer rates can be as high as
10K bytes/second.

Brown also distributes an asynchronous terminal program, Term, which
provides a user interface nearly the same as tn3270's when used with an
IBM 7171.  The combination of Term and tn3270 provides users with a
consistent terminal interface, whether they have a high-speed network
connection or a modem connection.  The same CMS RMAC and WMAC commands
also work with Term.

HOW TO OBTAIN TN3270

Brown encourages tn3270 to be freely distributed, provided the program
is not modified and the copyright notices are retained. tn3270 can be
obtained in any of the following ways:

Anonymous FTP from BROWNVM.BROWN.EDU (128.148.128.40):
    The distribution files are in the highest level directory.  Begin
    by retrieving the file $READ-ME.FIRST which describes the other
    files.

Anonymous FTP from NCSA (128.174.20.50):
    The distribution files are the contents of the directory
    NCSA_Telnet/tn3270.

BITNET distribution from [e-mail]:
    Request the distribution files by sending LISTSERV the command
    "get tn3270 package".  This command may be sent as a message
    over BITNET, or as the first line of text in standard RFC 822
    formatted mail. Other packages available are "tn3270xf" for the CMS
    file transfer programs, and "term" for the Term program.  Issue the
    command "get local filelist" for a complete list of available
    files.

Mail order from Brown:
    Starting on September 1, Brown will accept mail orders for copies
    of the tn3270 disk and documentation.  To place an order, send a
    check for $20 to:
        tn3270 Distribution
        Brown University Computer Store
        P.O. Box 1885
        Providence, RI 02912
    (Orders from Rhode Island must include 6% sales tax.)

KEEPING UP-TO-DATE

The NCSA Telnet Digest will be used for discussing issues related to
tn3270, as well as NCSA Telnet.  To subscribe to the digest, send a
request to [e-mail].

SOURCE AVAILABILITY

tn3270 source is written for Manx Aztec C, using the MPW-compatible
library and include files.  Brown intends to distribute the source in
the near future.  An announcement of source availability will be made
in the NCSA Telnet Digest mentioned above.

Peter DiCamillo
BITNET:    CMSMAINT@BROWNVM
Internet:  [e-mail]
U.S. Mail: Computing and Information Services, Brown University,
           P.O. Box 1885, Providence, RI 02912
Phone:     [phone]

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

From: [e-mail] (John Bradley)
Subject: NCSA Telnet under MSC 5.0 (or 5.1)
Date: Fri, 12 Aug 88 21:05:02 PDT

I would very much like to have a copy of the source ported in such a way that
it will compile under MSC 5.0.  The only driver it NEEDS to support is the
nicps2, so if you haven't ported all the drivers, no problem.  Also, I don't
care how neatly you ported it.  (ie, I don't care if it'll never compile under
Lattice C again...)

Any leads will be greatly appreciated.  I've attempted to port it myself, but
problems have occurred, and I'm rapidly running out of time to finish this.

John Bradley  -  [e-mail]