Beta.11, 6 December 1999
This page last updated: 30 December 1999
Beta.11 should be the last Beta before the final C-Kermit 7.0 release. New features of Beta.11 include:
C-Kermit is a combined serial and network communication software package offering a consistent, medium-independent, cross-platform approach to connection establishment, terminal sessions, file transfer, character-set translation, numeric and alphanumeric paging, and automation of communication tasks.
The current version of C-Kermit is 6.0, released in September 1996:
C-Kermit 7.0 entered public Beta testing January 30, 1999, as Beta.04. Beta.11 was released on 5 December 1999:
We are working on a new, less restrictive license for C-Kermit 7.0.
CLICK HERE To read the current draft license.
Here's a brief summary:
We also ask (but do not require) those who download C-Kermit from the net or receive it as part of another package to also purchase the user manual to (a) let you get the most out of the software; (b) reduce the load on our help desk; and (c) contribute some revenue to the nonprofit and entirely self-supporting Kermit Project.
NOTE: Beta-test versions are only for testing, not for licensing, redistribution, or production use. The new license is subject to revision, and will apply to C-Kermit 7.0 when it is released.
In response to those who wonder why C-Kermit itself is not totally free of restrictions on redistribution, it is simply because commercial C-Kermit licenses are a major component of the revenue that pays for the Kermit Project; without this revenue, we wouldn't be here.
Although C-Kermit and Kermit 95 share much of the same code base, they are not the same product. Each has features not found in the other; for example, Kermit 95 has built-in terminal emulation and integrated XYZMODEM protocol, whereas in C-Kermit these functions are accomplished externally. C-Kermit supports X.25 connections on certain platforms but K-95 does not support X.25. And so on. Each Kermit 95 release incorporates the Kermit file-transfer, command parsing, scripting, and certain other features of the current C-Kermit program (and thus the syntax of scripts is identical). Obviously, the platform-specific aspects are different; CLICK HERE for details on scripting.
Features that show up as links are described in greater detail below. The others (and many more) are described in the text file, ckermit2.txt. Items marked New are new to the latest Beta edit.
This is just a brief list; the complete story runs to more than 200 printed pages, and can be found in the ckermit2.txt file, which is a supplement to Using C-Kermit, 2nd Edition.
For even more detail, you can read the day-by-day edit history in the ckc196.txt file, as well as all the Alpha and Beta test announcements in the ck61*.txt and ck70*.txt files in the kermit/test/text/ directory.
The following sections present an overview of several of C-Kermit 7.0's new features. After these come links to the software itself.
In UNIX and Windows 9x/NT, C-Kermit 7.0 can be set up as an Internet daemon under inetd, similar to an FTP server, using a TCP port and Telnet options assigned for this purpose by the Internet Assigned Number Authority (IANA) and described in Internet Drafts currently under review:
http://www.columbia.edu/kermit/standards.html
The Internet Kermit Service Daemon (IKSD) can be accessed in client/server mode from any Kermit client (similar to how FTP works), but can also be accessed directly at its prompt, which opens up a whole new world of automation possibilities. Other advantages over FTP include:
Note that timestamps, permissions, text/binary mode switching, and directory tree transfer are not restricted to UNIX-to-UNIX connections, but also work with Kermit clients on other platforms including Windows 95/98/NT, OS/2, and VMS (as appropriate -- e.g. permissions don't apply to Windows).
A prototype IKSD is available for public access at:
kermit.columbia.edu 1649
Anonymous logins are welcome: give a user ID of "anonymous" or "ftp", and supply your email address as the password. You may log in interactively on a Telnet connection:
telnet kermit.columbia.edu 1649 Username: anonymous Password: abc@xyz.com
Or you can make a client/server connection as follows:
set host kermit.columbia.edu 1649 remote login anonymous abc@xyz.com
When you use C-Kermit 7.0 itself as the client, you will have a new "tight coupling" between client and server, in which each partner tracks the "mode" of the other (prompt, connect, server, etc). When you make an anonymous connection to this server, you will find yourself in the /pub/ftp tree, and can access any directories or files you could access with anonymous FTP to same server.
Links:
The UNIX version of C-Kermit 7.0 can now be used through any other communications program whose user interface goes through standard input and standard output. In addition, most of the UNIX versions can also control external programs via pseudoterminals, like 'expect'.
This allows you (for example) to use all the scripting and file transfer features of C-Kermit through clients of various services that C-Kermit might not support directly like an ssh client, tn3270 (for connecting to IBM mainframes), tn5250 (for AS/400 connections), various SOCKS Telnet clients, a cu or tip program that has access to a dialout device that Kermit does not, rlogin connections without being root. The commands are PIPE (for standard i/o redirection) and PTY (for pseudoterminals). Examples:
pipe cu -l tty04 pipe rlogin xyzcorp.com pipe srp-telnet xenon.stanford.edu pty ssh abccorp.com pty tn3270 cics.bigiron.com
PIPE is more portable but won't work with applications that don't use standard i/o, and it bypasses the terminal driver, which can result in CR/LF/CRLF confusion, inappropriate keyboard handing or echoing, etc. PTY is less widely available, but it allows you to control any text-mode application at all, and it does so through the terminal driver, thus bypassing the problems with PIPE.
In fact, the PTY interace lets you script interactions with any local text-mode program: your shell, lpc, Lynx, IRC, various text editors, and so on. This feature is available (as of Beta.11) in FreeBSD, NetBSD, OpenBSD, BSDI, Mac OS X, AIX 4.1 and later, DG/UX 5.4R4.11, Digital UNIX 3.2 and 4.0, HP-UX 9.00 and later, IRIX 6.0 and later, Linux, NeXTSTEP 3.x, QNX 4.25, SCO OSR5.0.5, SCO Unixware 7, SINIX 5.42, Solaris 2.x and 7, and SunOS 4.1.3.
UNIX C-Kermit can be built with support for MIT's Kerberos IV or Kerberos V, Stanford University's Secure Remote Password (SRP) protocol, or SSL/TLS security.
These protocols allow for mutually authenticated Telnet connections without sending passwords over the network, and optionally also for fully encrypted sessions. The encryption modules are not part of the regular C-Kermit package due to USA export law. If you are in the USA or Canada and you are interested in testing Kerberos, SRP, or SSL/TLS, CLICK HERE to download the security modules, or send us e-mail.
SSL/TLS is the IETF-approved form of public-key security, an alternative to SSH that is free of patent restrictions and that addresses the key-management and revocation issues that SSH presents. C-Kermit 7.0 Beta.11 supports the OpenSSL implementation of SSL/TLS, which allows pure SSL or TLS based connections with Tim Hudson's Telnet AUTH SSL and the IETF's Telnet START_TLS protocols, including verification of certificate chains for both client and server, and support for certificate revocation lists. A Unix telnet server that supports Telnet START_TLS is available from:
ftp://ftp.runestig.com/pub/starttls/inetutils-1.3.2-tls.tar.gz
SSL/TLS connections may also be used to connect to Secure Web Servers for use with the new HTTP commands:
SET HOST host https /SSL SET HOST host https /TLS
or between two C-Kermits to establish a private connection:
SET HOST * port /SSL <--- Server SET HOST host port /SSL <--- Client
Why not SSH?
There are two incompatible SSH protocols, v1 and v2. We don't support SSH version 1.x for a combination of legal and security reasons:
SSH version 2.x is not supported because:
[Top][Download][Documentation of security features]
A new suite of HTTP commands lets you manage Web servers with C-Kermit using HTTP 1.0 protocol. You can get and put files, obtain information about them, and so on, even when you could not ordinarily do so with FTP or Kermit (for example, because no FTP or IKSD server is installed on the Web server), and when you have the SSL/TLS option installed, you can do so securely.
C-Kermit 7.0 includes a new Telnet protocol engine incorporating:
Links:
The new EXEC command (Unix only) lets Kermit overlay itself in memory with an external program, starting this program with the given command-line options. EXEC /REDIRECT takes this one step further, redirecting the external program's standard i/o to Kermit's communications connection. You can use this feature to turn Kermit into your PPP dialer, which gives you all the advantages of C-Kermit's knowledge of modems, phone numbers, area and country codes, etc, and its dialing-directory and redialing capabilities. Example:
ask \%u { User: }
askq \%p { Password: }
set modem type usr ; Specify the kind of modem you have
set line /dev/ttyS1 ; Specify the device it's connected to
set speed 57600 ; and the speed
set flow rts/cts ; and flow control.
set dial retries 100 ; Try the dial sequence up to 100 times.
dial {{9-212-555-1212}{9-212-555-1213}{9-212-555-1214}{9-212-555-1215}}
if fail exit 1
for \%i 1 16 1 { ; Try up to 16 times to get login prompt
input 10 Login: ; Wait 10 sec for it to appear
if success break ; Got it - proceed...
output \13 ; Send a carriage return and try again
}
if ( > \%i 16 ) stop 1 NO LOGIN PROMPT
lineout \%u ; Send user ID
input 30 assword: ; Wait for Password prompt
if fail stop 1 NO PASSWORD PROMPT
lineout \%p ; Send the password.
exec /redirect pppd ; Replace ourselves with pppd.
Notice the advantages over the well-known PPP "chat script":
As of version 6.1, C-Kermit allows for optional command modifiers called switches.
A switch is a keyword beginning with a slash (/). Some switches accept values as operands. Switches affect only the command with which they are included; thus their affect is local, not global like SET commands. Here are some examples:
send oofa.txt ; No switches send /binary oofa.zip ; A switch without a value send /protocol:zmodem oofa.zip ; A switch with a value send /text /delete /as-name:x.x oofa.txt ; Several switchesSwitches bring a new level of flexibility to Kermit's command language. For example, they can be used for file selection in file-transfer commands:
send /after:8-Feb-1998_10:28:01 /larger-than:10000 /except:*.log *.*or for disposition of the source file after transfer:
send /binary /delete *.zipor for mailing or printing:
send /mail /subject:{Here is the recipe you wanted} lasagna.txt
send /print:{-PLaserWriter2 -#3} lasagna.ps
or whether to pass the file through a filter, or to descend directories
recursively, or to recover an interrupted transfer from the point of failure,
and so on, in any sensible combination.
Switches have been added not only to the SEND command, but also to most other file-transfer commands, as well as to the CONNECT, SET LINE, SET HOST, DIRECTORY, DELETE, PURGE, TYPE, RENAME, COPY, STATISTICS, and others. Certain commands including DIRECTORY, DELETE, PURGE, and TYPE let you set default switches to match your preferences so you don't have to type them each time.
A pattern is a string that includes special notation for matching classes or sequences of characters. C-Kermit 7.0 / K95 1.1.18 supports patterns in several places:
Patterns are also called wildcards, especially when used for filename matching, as they are in the UNIX version and in K-95 1.1.18. C-Kermit 7.0 supports the following notation:
C-Kermit 7.0 and its derivatives (including Kermit 95 1.1.18 and later) go to extraordinary lengths to transfer every file in the most appropriate mode, text or binary, automatically. Only in a few rare cases will the automatic methods fail to determine the appropriate mode for a particular file. When they do, however, it is almost always better to use binary mode, since this leaves the file intact and unchanged, rather than changing its characters or record format, and allows for recovery in case of broken transmissions. For this reason, the default file type (that is, the one that is used in the absence of any other information or instructions) in C-Kermit 7.0 has been changed from text to binary.
Of course you can change the default back to text simply by giving a SET FILE TYPE TEXT command (or putting it in your C-Kermit customization file) and you can also override the default and/or the automatic methods on a per-transfer basis (by using the new /BINARY and /TEXT switches on the SEND and GET commands) or even a per-file basis (by creating a SEND-LIST).
Also with this change comes the new SET FILE INCOMPLETE AUTO command, also the new default, which causes incompletely received files to be kept for binary-mode transfers and discarded for text-mode ones, since the main reason to keep incompletely received files is to allow recovery, which is possible only for binary-mode transfers.
C-Kermit 6.1 and later (and Kermit 95 1.1.16 and later) automatically choose the appropriate transfer mode, text or binary, for each file they send by following a rather complex procedure, which includes end-to-end "like system" recognition, whether character-set translation has been requested, and other factors. When the two ends recognize each other as "alike" (e.g. both are some form of UNIX) and character-set translation has not been requested, all files are transferred in binary mode. This improves performance, removes any possibility of "corruption" by inappropriate character-set or record-format conversions, and allows for recovery of interrupted transfers.
When the two systems do not recognize each other as alike, or character-set translation has been requested, the file sender chooses text and binary mode on a per-file basis by matching each file's name with a list of patterns. For example, if a file's name matches the pattern "*.txt" it is sent in text mode, whereas if it matches "*.zip" it is sent in binary mode. A comprehensive list of patterns is preconfigured, and commands are provided for you to edit the list, as well as to disable or re-enable this feature.
Filename pattern matching allows a file group to be sent between unlike systems (e.g. from UNIX to VMS) without having to separate the text and binary files, with full record-format and character-set conversion performed on text files, and binary files transferred without conversion, automatically. (NOTE: The filename pattern-matching feature is not used in VMS C-Kermit, which has a different method of accomplishing the same thing.)
The UNIX and VMS versions of C-Kermit 7.0 now include each file's permissions (protection code) among the transmitted file attributes. This is useful mainly in UNIX, so avoid loss of "execute" permission for programs or shell scripts during transfer. However, the mechanism also works across platforms so, for example, a UNIX file with execute permission will also have execute permission after being transferred to VMS (and vice-versa).
C-Kermit 7.0, when used in conjunction with Kermit 95 1.1.16 or later, MS-DOS Kermit 3.16 or later, or C-Kermit 7.0 itself, can perform "recursive" file transfers, in which all the (selected) files in the given directory are sent, plus all the files in all the subdirectories of the given directory, and all the files in their subdirectories, and so on.
Such transfers can take place not only between computers with similar file systems (such as Solaris and AIX), but also between dissimilar systems (like Windows 95 and HP-UX or VMS). Directories are created as needed during the transfer process.
Furthermore, any mixture of text and binary files can be accommodated via filename-pattern matching, as described in the previous section. This allows, for the first time anywhere (as far as we know) transfer of entire directory trees (entire file systems if you start at the root) between dissimilar computers in a single operation without the use of intermediate archives such as tar or ZIP.
In some versions of C-Kermit 7.0 (notably the UNIX version) it is now possible to pass outbound or incoming files through a "filter" as part of the transfer process. Similarly, it is now possible to send the output of an arbitrary command or program, or to receive into the standard input of a command or program. For example, you may now tell C-Kermit to send the output of a pipeline composed of tar and gzip, and another C-Kermit on the other end to receive to a pipeline composed of gunzip and tar. Or in case you have a text file written in a character set that C-Kermit doesn't know about, you can pass it through a translation filter. You can even use this feature to accomplish encrypted file transfers on connections that are not already encrypted otherwise.
File-transfer performance has been improved in several ways:
When full unprefixing and streaming are used with a large packet length, C-Kermit's file-transfer throughput is comparable with FTP; here are some typical text and binary file transfers between two UNIX workstations with the new C-Kermit over a local 10Mbps Ethernet (note the new brief file-transfer display option, the automatic switching between binary and text mode, and the new more-accurate statistics):
SENDING wart (binary) (23985 bytes): OK (0.040 sec, 599625 cps) SENDING wermit (binary) (1323517 bytes): OK (4.490 sec, 294769 cps) SENDING ckcnet.c (text) (269168 bytes): OK (0.790 sec, 340718 cps) SENDING ckwart.o (binary) (25332 bytes): OK (0.040 sec, 633299 cps) SENDING ckufio.c (text) (112341 bytes): OK (0.290 sec, 387382 cps) SENDING ckuusr.o (binary) (132340 bytes): OK (0.180 sec, 735222 cps) SENDING ckuus2.o (binary) (183168 bytes): OK (0.300 sec, 610559 cps) SENDING ckuus3.o (binary) (154492 bytes): OK (0.200 sec, 772459 cps) SENDING ckuus6.o (binary) (133128 bytes): OK (0.180 sec, 739599 cps)
C-Kermit 7.0 also responds much more quickly to connection loss and external interruptions during file transfer.
C-Kermit has included performance features like long packets for more over a decade, with others (sliding windows, control-character unprefixing, and now streaming) added over the years. Nevertheless, the popular perception is still that "Kermit is slow". This is due in part to the many third-party implementations that, indeed, are slow, as well to the persistence of fifteen-year-old Kermit programs from the Kermit project itself.
Of course modern Kermit protocol and software (since about 1990) can go as fast as you care to make it go, but its default tuning has always been for robustness rather than speed. It turns out, unfortunately, that first impressions matter most. If it's slow out of the box, few will make the effort to learn how to make it go fast, or to understand why it is delivered with slow tuning.
Therefore C-Kermit 7.0 is delivered with fast tuning:
Kermit software, a pioneer in international text transfer since the 1980s, now adds Unicode (ISO 10646) -- the Universal Character Set (UCS) -- to its already large repertoire of character sets. Unlike traditional character sets, the UCS encodes all of the world's major scripts, and therefore allows true multilingual text.
Kermit protocol and software has included character-set translation capabilities for more than a decade, allowing conversion of text among the many "traditional" standard and proprietary character sets like the ISO 8859 Latin Alphabets, PC code pages, IBM mainframe EBCDIC code pages, ISO 646 national character sets, JIS, DEC, HP, DG, Macintosh, NeXT, etc.
With growing acceptance of Unicode, there is increasing need for importation of text in "traditional" encodings into Unicode platforms and applications, and also for export of Unicode text to non-Unicode environments. C-Kermit now offers these services over a wide range of platforms and communication methods.
Obviously when translating from Unicode to a smaller set, Unicode characters that are not in the smaller set are lost.
[Top]
You can obtain the current C-Kermit 7.0 Beta test in any of several archive formats via anonymous ftp by clicking on the following links:
These archives contain complete UNIX and VMS source code as well as documentation updates, installation instructions, hints and tips files, initialization files, scripts, demos, etc.
Those who wish to follow developments on a daily basis can access the current working source code, updated (usually) each day:
- unix.tar.gz - UNIX source code (gunzip, tar xvf unix.tar)
- unix.tar.Z - UNIX source code (uncompress, tar xvf unix.tar)
- vms.zip - VMS source code (unzip)
- vos.zip - Stratus VOS source code (unzip)
- os9.zip - Microware OS-9 source code (unzip)
Beta-test versions of Kermit 95 1.1.18 (based on C-Kermit 7.0) are available upon request to registered users of K-95. Send requests by email to kermit-support@columbia.edu with a subject of "K95 IKS BETA REQUEST". Include your K-95 serial number and current version number in the body of the letter.
You can also download individual UNIX binaries from the list below, but in case of library or other version mismatches, it is better to build from source if you can.
If you want to build from source code, fetch one of the archives above if you have VMS-based unpacking tools, otherwise get the source files individually as described just below.
You can also retrieve the text files only (without the source code) in the following archives:
Source code and text files are also available separately in the kermit/test/text/ directory. These include files for platforms other than UNIX and VMS, such as Stratus VOS, Data General AOS/VS, OS-9, etc. See the ckaaaa.txt file for details.
NOTE: The UNIX, VMS, and AOS/VS source files are all at 7.0 level. The others (except, to some extent, OS-9) have not yet been upgraded to 7.0. Those that have NOT been upgraded yet include: Stratus VOS, Commodore Amiga, Plan 9, Macintosh, BeBox, Atari ST. Volunteers welcome.
[Top]
Individual binaries are also available from the kermit/test/bin/ directory for those who can not build from source code. Be sure to download in binary (not ASCII or text) mode. Those marked with "+" are current; those without the "+" are from earlier C-Kermit 7.0 or or 6.1 Alpha or Beta tests.
IMPORTANT: These files are not Windows files and do not follow Windows naming conventions. You might need to right-click and choose "Save Link As..." in your web browser to force download rather than some other undesired action.
Naming Conventions: Filenames start with "ck" for C-Kermit, then one letter or digit to indicate the platform ("u" for UNIX, "d" for Data General AOS/VS, "v" for VMS, "i" for Amiga, "9" OS-9, "p" for Plan 9, etc). After that comes a three-digit edit number:
193: Version 6.1.193, November 1996 through June 1998.Then the test version designator: "a" for Alpha or "b" for Beta, followed by the 2-digit test number. Example:
194: Version 6.1.194, June 1998 through December 1998.
195: Version 7.0.195, January 1999 through August 1999.
196: Version 7.0.196, September 1999 through the present.
cku196b11
Denotes C-Kermit for UNIX 7.0.196 Beta.11.
The rest of the name is platform-dependent; in UNIX it's the name of the makefile target, optionally followed by specific hardware platform and/or OS version, when it makes a difference. In VMS it's the platform ("axp" or "vax"), then the VMS version number (e.g. "vms71"), and then TCP/IP product and version number (or "nonet" if TCP/IP support is not built in). And so on.
REMEMBER: It's often better to build your own binary than to run a prebuilt one, due to the ever-increasing likelihood of OS and/or library version mismatch.
After downloading, rename to "wermit" or "wermit.exe" (etc), as appropriate for your operating system (as opposed to "kermit", to prevent confusion between the production and test versions) and, if necessary, give execute permission, e.g. (in UNIX):
$ mv cku196b11.linux-i386-rh6.1 wermit $ chmod +x wermit
Also remember that before C-Kermit can be used to dial out from UNIX, it will probably also be necessary to give the Kermit executable a certain owner and group, and to set it suid and/or sgid bits, to allow it access to the dialout device and/or lockfile directory (the same as any other dialout software, such as cu or minicom).
Note that any executable C-Kermit 7.0 binary should also be accompanied by an assortment of text files -- documentation updates, installation instructions, hints and tips, etc; see the previous section.
Notes:
If you are able to make a binary not listed below
(or that is listed below, but without the "+"), please contact us.
Filename Description ---------------------------------------------------------------------- ck9193a13-os9-2.4-net OS-9/68K 2.4 (with TCP/IP) + ck9196b11.os9-2.3-nonet OS-9/68K 2.3 (no TCP/IP) ---------------------------------------------------------------------- + ckd196b11-aosvsii-2.20.73.pr DG MV 2500 AOS/VS-II 2.20.73 ---------------------------------------------------------------------- ckl195b07-vos1333y-nonet.h71 Stratus Continuum VOS 13.3.3y no networking ckl195b07-vos1333y-tcp-nox25.h71 Stratus Continuum VOS 13.3.3y TCP/IP but no X.25 ckl195b07-vos1333y-notcp-x25.h71 Stratus Continuum VOS 13.3.3y X.25 but no TCP/IP ckl195b07-vos1333y-tcp-x25.h71 Stratus Continuum VOS 13.3.3y TCP/IP + X.25 ckl196b10-vos1402g-nonet.h68 Stratus Continuum VOS 14.0.2g no networking ckl196b10-vos1402g-tcp-nox25.h68 Stratus Continuum VOS 14.0.2g TCP/IP but no X.25 ckl196b10-vos1402g-notcp-x25.h68 Stratus Continuum VOS 14.0.2g X.25 but no TCP/IP ckl196b10-vos1402g-tcp-x25.h68 Stratus Continuum VOS 14.0.2g TCP/IP + X.25 ckl196b10-vos1333o-nonet.h68 Stratus mc680x0 VOS 13.3.3o no networking ckl196b10-vos1333o-tcp-nox25.h68 Stratus mc680x0 VOS 13.3.3o TCP/IP but no X.25 ckl196b10-vos1333o-notcp-x25.h68 Stratus mc680x0 VOS 13.3.3o X.25 but no TCP/IP ckl196b10-vos1333o-tcp-x25.h68 Stratus mc680x0 VOS 13.3.3o TCP/IP + X.25 cklxtr.cm Decoder macro for Stratus binaries ---------------------------------------------------------------------- cki196b10.exe Commodore Amiga, AmigaDOS 3.1 or higher ---------------------------------------------------------------------- + ckp196b11.plan9-m68k Plan 9 from Bell Labs on 680x0 + ckp196b11.plan9-i386 Plan 9 from Bell Labs on PC + ckp196b11.plan9-mips Plan 9 from Bell Labs on MIPS + ckp196b11.plan9-sparc Plan 9 from Bell Labs on Sparc ---------------------------------------------------------------------- + cku196b11.macosx10-ppc-1.0 Apple PowerBook G3, Mac OS X 1.0 (no curses) + cku196b11.macosx10c-ppc-1.0 Apple PowerBook G3, Mac OS X 1.0 (curses) cku196b10.macosx10nc-ppc-1.0 Apple PowerBook G3, Mac OS X 1.0 (ncurses) cku196b10.linuxppc-000 Apple PowerBook G3, LinuxPPC 000 cku195b06.mklinux-ppc-dr3 Apple Power Macintosh, MkLinux DR3 + cku196b11.sys3upcg AT&T 7300 UNIX PC (no curses) + cku196b11.sys3upcgm AT&T 7300 UNIX PC (no curses, minimum features) + cku196b11.sys3upcgc AT&T 7300 UNIX PC (with curses) + cku196b11.sys3upcgfd AT&T 7300 UNIX PC (with curses, compact version) + cku196b11.att351gm AT&T 7300 UNIX PC (hardware flow control) cku193b05.linux-2.0.33-m68k Commodore Amiga, Linux 2.0.33 RH 5.0 + cku196b11.dgux54310-m88k Data General AViiON 88110, DG/UX 5.4R3.10 + cku196b11.dgux54411-m88k Data General AViiON 88110, DG/UX 5.4R4.11 cku196b10.dec-osf30 DEC Alpha OSF/1 3.0 + cku196b11.du32 DEC Alpha Digital UNIX 3.2 cku195b07.du40-4.0b DEC Alpha Digital UNIX 4.0B cku195b09.du40-4.0d DEC Alpha Digital UNIX 4.0D + cku196b11.tru64-4.0e DEC Alpha Tru64 UNIX 4.0E + cku196b11.tru64-4.0g DEC Alpha Tru64 UNIX 4.0G + cku196b11.ultrix43-mips DECstation 5000, Ultrix 4.3 + cku196b11.ultrix43notcp-mips DECstation 5000, Ultrix 4.3, no TCP/IP + cku196b11.ultrix44-mips DECstation 5000, Ultrix 4.4 cku196b10.bsd211noicp DEC PDP-11, 2.11BSD (command-line only) cku196b10-cku195.sr DEC PDP-11, 2.11BSD strings module cku193b05.bsd44-hp9000-300 HP-9000/300 4.4BSD-Lite + cku196b11.hpux500-s550-5.21 HP-9000/550 HP-UX 5.21 no TCP/IP + cku196b11.hpux500wintcp-s550-5.21 HP-9000/550 HP-UX 5.21 TWG-TCP/IP 1.2 + cku196b11.hpux65-s300-6.5 HP-9000/3xx HP-UX 6.5 + cku196b11.hpux65c-s300-6.5 HP-9000/3xx HP-UX 6.5 + cku196b11.hpux65o-s300-6.5 HP-9000/3xx HP-UX 6.5 + cku196b11.hpux65oc-s300-6.5 HP-9000/3xx HP-UX 6.5 optimized + cku196b11.hpux70lfn-s300-7.05 HP-9000/3xx HP-UX 7.05, long filenames (LFN) + cku196b11.hpux70lfnc-s300-7.05 HP-9000/3xx HP-UX 7.05, LFN, curses + cku196b11.hpux70olfn-s300-7.05 HP-9000/3xx HP-UX 7.05, LFN, optimized + cku196b11.hpux70olfnc-s300-7.05 HP-9000/3xx HP-UX 7.05, LFN, curses, optimized + cku196b11.hpux70sf-s300-7.05 HP-9000/3xx HP-UX 7.05, short filenames (SFN) + cku196b11.hpux70sftcpc-s300-7.05 HP-9000/3xx HP-UX 7.05, SFN, TCP + cku196b11.hpux70osf-s300-7.05 HP-9000/3xx HP-UX 7.05, SFN, optimized + cku196b11.hpux70osftcpc-s300-7.05 HP-9000/3xx HP-UX 7.05, SFN, TCP, optimized + cku196b11.hpux80notcp-s300-8.00 HP-9000/3xx HP-UX 8.00, no TCP/IP + cku196b11.hpux80notcp-s400-8.00 HP-9000/4xx HP-UX 8.00, no TCP/IP cku196b10.hpux80onotcp-s400-8.00 HP-9000/4xx HP-UX 8.00, optimized, no TCP/IP + cku196b11.hpux80-s300-8.00 HP-9000/3xx HP-UX 8.00, no curses + cku196b11.hpux80-s400-8.00 HP-9000/4xx HP-UX 8.00, no curses + cku196b11.hpux80c-s400-8.00 HP-9000/4xx HP-UX 8.00, no curses cku196b10.hpux80c-s300-8.00 HP-9000/3xx HP-UX 8.00, curses + cku196b11.hpux80o-s300-8.00 HP-9000/3xx HP-UX 8.00, no curses, optimized cku196b10.hpux80o-s400-8.00 HP-9000/4xx HP-UX 8.00, no curses, optimized + cku196b11.hpux80oc-s300-8.00 HP-9000/3xx HP-UX 8.00, curses, optimized cku196b10.hpux80oc-s400-8.00 HP-9000/4xx HP-UX 8.00, curses, optimized + cku196b11.hpux90-s300-9.03 HP-9000/340 HP-UX 9.03 + cku196b11.hpux90m68ko-s300-9.03 HP-9000/340 HP-UX 9.03 cku195b07.hpux90-s800-9.04 HP-9000/8xx HP-UX 9.04 + cku196b11.hpux90-s700-9.05 HP-9000/712 HP-UX 9.05 + cku196b11.hpux90o-s700-9.05 HP-9000/712 HP-UX 9.05, optimized + cku196b11.hpux90o700-s700-9.05 HP-9000/712 HP-UX 9.05, optimized for s700 cku195b07.hpux90o700-s800-9.05 HP-9000/8xx HP-UX 9.05, optimized for s700 + cku196b11.hpux90-s300-9.10 HP-9000/340 HP-UX 9.10 + cku196b11.hpux90m68ko-s300-9.10 HP-9000/340 HP-UX 9.10 + cku196b11.hpux100-s700-10.01 HP-9000/735 HP-UX 10.01 + cku196b11.hpux100o-s700-10.01 HP-9000/735 HP-UX 10.01, optimized cku195b08.hpux100-s800-10.10 HP-9000/847 HP-UX 10.10 + cku195b07.hpux100o+s700-10.20 HP-9000/725 HP-UX 10.20, highly optimized + cku196b11.hpux100+s800-10.20 HP-9000/8xx HP-UX 10.20 + cku196b11.hpux100o-s800-10.20 HP-9000/8xx HP-UX 10.20, optimized + cku196b11.hpux100o+s800-10.20 HP-9000/8xx HP-UX 10.20, highly optimized + cku196b11.hpux100t+s800-10.20 HP-9000/8xx Trusted HP-UX 10.20 + cku196b11.hpux100to-s800-10.20 HP-9000/8xx Trusted HP-UX 10.20, optimized + cku196b11.hpux100to+s800-10.20 HP-9000/8xx Trusted HP-UX 10.20, highly optimized + cku196b11.hpux100-s700-10.20 HP-9000/715 HP-UX 10.20 + cku196b11.hpux100o-s700-10.20 HP-9000/715 HP-UX 10.20, optimized cku195b07.hpux100-s700-10.30 HP-9000/G70 HP-UX 10.30 cku195b07.hpux100o+s700-10.30 HP-9000/G70 HP-UX 10.30, highly optimized cku195b07.hpux1100-s700-11.00 HP-9000/715 HP-UX 11.00 cku195b07.hpux1100o+s700-11.00 HP-9000/715 HP-UX 11.00, highly optimized cku193b05.ps2aix3-1.2.1 IBM PS/2 AIX 1.2.1 + cku196b11.rs6aix32c IBM RS/6000 AIX 3.2 + cku196b11.aix41-4.1.3 IBM RS/6000 AIX 4.1.3 cku195b07.aix42-4.2.1 IBM RS/6000 AIX 4.2.1 + cku195b04.aix43-4.3.0 IBM RS/6000 AIX 4.3.0 cku195b04.aix43-4.3.1 IBM RS/6000 AIX 4.3.1 + cku196b11.aix43-4.3.2 IBM RS/6000 AIX 4.3.2 + cku196b11.clix-3.1 Intergraph Clipper CLIX 3.1 (no TCP/IP) + cku196b11.clixnet-3.1 Intergraph Clipper CLIX 3.1 (with TCP/IP) + cku196b11.sv68r3v6 Motorola MVME 147 68K, System V/68 R3V6 + cku196b11.sv88r40-4.3 Motorola MVME 187 88K, System V R4 V4.3 + cku196b11.sv88r40-4.4 Motorola MVME 187 88K, System V R4 V4.4 + cku196b11.next-m68k-3.1 NeXT 68040 NeXTSTEP 3.1 cku193b05.next-3.2-m68k NeXT 68040 NeXTSTEP 3.2 + cku196b11.next33-m68k-3.3 NeXT 68040 NeXTSTEP 3.3 + cku196b11.openstep42-m68k NeXT 68040 OPENSTEP 4.2 cku193a07.bsdi2-2.1 PC, BSDI 2.1 cku193a10.bsdi2-3.0 PC, BSDI 3.0 cku196b10.bsdi3-3.1 PC, BSDI 3.1 cku196b10.bsdi4-4.0 PC, BSDI 4.0 + cku196b11.bsdi4-4.0.1 PC, BSDI 4.0.1 + cku196b11.coherent42 PC, Coherent 4.2.10 cku195b05.dgux54411-i386 PC, DG/UX 5.4R4.11 cku195b08.dgux54420-i386 PC, DG/UX 5.4R4.20 cku196b10.dynixptx216c-i486 PC/486, Sequent DYNIX/ptx 2.1.6 cku196b10.dynixptx216cgcc-i386 PC/386, Sequent DYNIX/ptx 2.1.6 cku196b10.dynixptx216cgcc-i486 PC/486, Sequent DYNIX/ptx 2.1.6 + cku196b11.dynixptx44-i386-4.4.2 PC/386, Sequent DYNIX/ptx 4.4.2 + cku196b11.freebsd2-i386-2.2.7 PC, FreeBSD 2.2.7 (ncurses) + cku196b11.freebsd2c-i386-2.2.7 PC, FreeBSD 2.2.7 (curses) + cku196b11.freebsd3-i386-3.1 PC, FreeBSD 3.1 (ncurses) + cku196b11.freebsd3-i386-3.3 PC, FreeBSD 3.3 (ncurses) + cku196b11.freebsd3c-i386-3.3 PC, FreeBSD 3.3 (curses) cku193b05.linux-1.2.13-i386 PC, Linux 1.2.13, Red Hat 3.0.3 cku193b05.linux-2.0.33-i386 PC, Linux 2.0.33, Slackware 3.4 cku195b03.linux-i386-rh4.2 PC, Linux Red Hat 4.2 (libc5) cku195b02.linux-i386-rh5.1 PC, Linux Red Hat 5.1 + cku196b11.linux-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, ncurses) + cku196b11.linuxc-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, curses) + cku196b11.linuxnc-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, no curses) + cku196b11.linuxnotcp-i386-rh5.2 PC, Linux Red Hat 5.2 (glibc, no TCP/IP) cku196b10.linux-i386-rh6.0 PC, Linux Red Hat 6.0 (glibc, ncurses) + cku196b11.linux-i386-rh6.1 PC, Linux Red Hat 6.1 (glibc, ncurses) + cku196b11.linuxc-i386-rh6.1 PC, Linux Red Hat 6.1 (glibc, curses) + cku196b11.linuxnc-i386-rh6.1 PC, Linux Red Hat 6.1 (glibc, no curses) + cku196b11.linux-i386-sw3.5.0 PC, Linux Slackware 3.5.0 (libc5) + cku196b11.linux-i386-sw4.0.0 PC, Linux Slackware 4.0.0 (libc5) + cku196b11.linux-i386-sw7.0.0 PC, Linux Slackware 7.0.0 (glibc) cku195b07.linux-i386-su6.0 PC, Linux SuSe 6.0 (glibc) cku195b02.minix20 PC, Minix 2.0 + cku196b11.sysvr4sx-mpras-2.03 PC, NCR MP-RAS 2.03 + cku196b11.sysvr4sx-mpras-3.02 PC, NCR MP-RAS 3.02 + cku196b11.sysvr4sxtcpc-mpras-2.03 PC, NCR MP-RAS 2.03 + TCP/IP + Curses + cku196b11.sysvr4sxtcpc-mpras-3.02 PC, NCR MP-RAS 3.02 + TCP/IP + Curses cku196b10.netbsd-i386-1.3.3 PC, NetBSD 1.3.3 cku196b10.netbsd14-i386-1.4 PC, NetBSD 1.4 + cku196b11.netbsd-i386-1.4.1 PC, NetBSD 1.4.1 (curses) + cku196b11.netbsdnoiksd-i386-1.4.1 PC, NetBSD 1.4.1 (no IKSD) + cku196b11.netbsdn-i386-1.4.1 PC, NetBSD 1.4.1 (ncurses) cku195b04.openbsd-i386-2.3 PC, OpenBSD 2.3 cku195b07.openbsd-i386-2.4 PC, OpenBSD 2.4 + cku196b11.openbsd-i386-2.5 PC, OpenBSD 2.5 + cku195b10+.qnx16-4.25 PC, QNX 4.25 16-bit + cku196b11.qnx32-4.25 PC, QNX 4.25 32-bit + cku196b11.sco234 PC, SCO XENIX 2.3.4 (no TCP/IP or curses) + cku196b11.sco234c PC, SCO XENIX 2.3.4 (curses but no TCP/IP) + cku196b11.sco234netc PC, SCO XENIX 2.3.4 (curses + SCO TCP/IP) cku195b05.sco32v4net-4.0 PC, SCO UNIX/386 3.2v4.0 (with TCP/IP) cku195b05.sco32v4netndx-odt2 PC, SCO ODT 2.0 (with TCP/IP) + cku196b11.sco-odt30 PC, SCO ODT 3.0 (with TCP/IP) + cku196b11.sco32v4-4.2 PC, SCO UNIX/386 3.2v4.2 (no TCP/IP) + cku196b11.sco32v4ns-4.2 PC, SCO UNIX/386 3.2v4.2 (definitely no TCP/IP) + cku196b11.sco32v4net-4.2 PC, SCO UNIX/386 3.2v4.2 (with TCP/IP) + cku196b11.sco32v4gcc-4.2 PC, SCO UNIX/386 3.2v4.2 (gcc, no TCP/IP) + cku196b11.sco32v4netgcc-4.2 PC, SCO UNIX/386 3.2v4.2 (gcc, with TCP/IP) + cku196b11.sco32v5 PC, SCO OpenServer 5.0.0 (no TCP/IP) + cku196b11.sco32v5net PC, SCO OpenServer 5.0.0 (with TCP/IP) + cku196b11.sco32v504 PC, SCO OpenServer 5.0.4 (no TCP/IP) + cku196b11.sco32v504net PC, SCO OpenServer 5.0.4 (with TCP/IP) + cku196b11.sco32v505 PC, SCO OpenServer 5.0.5 (no TCP/IP) + cku196b11.sco32v505gcc PC, SCO OpenServer 5.0.5 (gcc, no TCP/IP) + cku196b11.sco32v505net PC, SCO OpenServer 5.0.5 (with TCP/IP) + cku196b11.sco32v505netgcc PC, SCO OpenServer 5.0.5 (gcc, TCP/IP) cku195b07.solaris24-i386-2.4 PC, Solaris 2.4 cku195b07.solaris2x25-i386-2.4 PC, Solaris 2.4 + SunLink X.25 cku195b04.solaris25-i386-2.5.1 PC, Solaris 2.5.1 + cku196b11.solaris25g-i386 PC, Solaris 2.5.1 (gcc) cku195b09.solaris26-i386 PC, Solaris 2.6 cku195b07.solaris7-i386 PC, Solaris 7 + cku196b11.solaris7g-i386 PC, Solaris 7 (gcc) cku195b05.is5r3jc-4.1 PC, Sunsoft Interactive UNIX 4.1 cku193b03.unixware-1.1.2 PC, Unixware 1.1.2 cku195b08.unixware2-2.0.3 PC, Unixware 2.0.3 + cku196b11.uw21-2.1.0 PC, Unixware 2.1.0 + cku196b11.uw21iksd-2.1.0 PC, Unixware 2.1.0 (+ IKSD support) cku193a13.unixware2-2.1.1 PC, Unixware 2.1.1 cku193b05.unixware2-2.1.2 PC, Unixware 2.1.2 + cku196b11.uw21-2.1.3 PC, Unixware 2.1.3 + cku196b11.uw21iksd-2.1.3 PC, Unixware 2.1.3 (+ IKSD support) + cku196b11.uw7-7.0.1 PC, Unixware 7.0.1 + cku196b11.uw7-7.0.1 PC, Unixware 7.1.0 + cku196b11.uw7iksd-7.0.1 PC, Unixware 7.0.1 (+ IKSD) + cku196b11.uw7iksd-7.0.1 PC, Unixware 7.1.0 (+ IKSD) cku193b05.pyramid Pyramid MIS-12/06 OSx5.1a-93a080 + cku196b11.pyrdcosx Pyramid MIS-ES6/1024 SMP_DC-OSx1.1-95c087.4 + cku195b09.irix53 SGI IRIX 5.3 cku195b09.irix62 SGI IRIX 6.2 cku196b11.irix62-02 SGI IRIX 6.2 cku195b06.irix64 SGI IRIX 6.4 + cku196b11.irix65indy-6.5.4f SGI IRIX 6.5.4f (Indy) cku195b06.irix65-o2-6.5.3m SGI IRIX 6.5.3m (O-2) cku196b10.irix65-o200-6.5.4f SGI IRIX 6.5.4f (Origin 200) + cku196b11.irix65-o200-6.5.6f SGI IRIX 6.5.6f (Origin 200) + cku196b11.sinix542 SNI SINIX-N 5.42 MIPS (RM200) + cku196b11.sni543 SNI Reliant UNIX (SINIX-Y) 5.43 MIPS (RM600) + cku196b11.sni544 SNI Reliant UNIX (SINIX-Y) 5.44 MIPS (RM600) cku196b10.iclsys5r4m+ ICL DRS6000 (Sparc) UNIX 4.2MP 7MPLUS.11.2 cku196b10.netbsd-sparc-1.3.3 Sun Sparc, NetBSD 1.3.3 cku196b10.netbsd14-sparc-1.4 Sun Sparc, NetBSD 1.4 + cku196b11.netbsd-sparc-1.4.1 Sun Sparc, NetBSD 1.4.1 + cku196b11.netbsdnoiksd-sparc-1.4.1 Sun Sparc, NetBSD 1.4.1 + cku196b11.sunos41c-4.1.3 Sun Sparc, SunOS 4.1.3_U1 + cku196b11.sunos41gcc-4.1.3 Sun Sparc, SunOS 4.1.3_U1 (gcc) + cku196b11.sunos41gcc-4.1.4 Sun Sparc, SunOS 4.1.4 (gcc) cku196b10.solaris23-sparc-2.3 Sun Sparc, Solaris 2.3 cku195b07.solaris2x25-sparc-2.3 Sun Sparc, Solaris 2.3 + SunLink X.25 cku195b05.solaris23g-sparc-2.3 Sun Sparc, Solaris 2.4 (gcc) + cku196b11.solaris24-sparc-2.4 Sun Sparc, Solaris 2.4 cku195b09.solaris24g-sparc-2.4 Sun Sparc, Solaris 2.4 (gcc) cku195b02.solaris24x25-sparc-2.4 Sun Sparc, Solaris 2.4, SunLink X.25 + cku196b11.solaris25-sparc-2.5.1 Sun Sparc, Solaris 2.5.1 + cku196b11.solaris25g-sparc-2.5.1 Sun Sparc, Solaris 2.5.1 + cku196b11.solaris26-sparc Sun Sparc, Solaris 2.6 + cku196b11.solaris25x26-sparc-2.6 Sun Sparc, Solaris 2.6 + SunLink X2.5 9.00 + cku196b11.solaris26g-sparc Sun Sparc, Solaris 2.6 (gcc) + cku196b11.solaris7-sparc Sun Sparc, Solaris 7 + cku196b11.solaris7g-sparc Sun Sparc, Solaris 7 (gcc) ---------------------------------------------------------------------- + ckv196b11-axp-vms62-nonet.exe Alpha CPU, VMS 6.2, no TCP/IP ckv193a10-axp-vms62-tgv40.exe Alpha CPU, VMS 6.2, MultiNet 4.0 ckv193b09-axp-vms62-tgv40b.exe Alpha CPU, VMS 6.2, MultiNet 4.0B + ckv196b11-axp-vms62-ucx33.exe Alpha CPU, VMS 6.2, UCX 4.0 + ckv196b11-axp-vms62-ucx40.exe Alpha CPU, VMS 6.2, UCX 4.0 + ckv196b11-axp-vms62-ucx42.exe Alpha CPU, VMS 6.2, UCX 4.2 + ckv196b11-axp-vms71-nonet.exe Alpha CPU, VMS 7.1, no TCP/IP ckv196b10-axp-vms71-tgv40a.exe Alpha CPU, VMS 7.1, MultiNet 4.0A + ckv196b11-axp-vms71-tgv40b.exe Alpha CPU, VMS 7.1, MultiNet 4.0B ckv196b10-axp-vms71-tgv41a.exe Alpha CPU, VMS 7.1, MultiNet 4.1A ckv195b04-axp-vms71-tgv41b.exe Alpha CPU, VMS 7.1, MultiNet 4.1B ckv195b09-axp-vms71-tgv42a.exe Alpha CPU, VMS 7.1, MultiNet 4.2A + ckv196b11-axp-vms71-pst53.exe Alpha CPU, VMS 7.1, TCPware 5.3 + ckv196b11-axp-vms71-ucx41.exe Alpha CPU, VMS 7.1, UCX 4.1 ckv195b04-axp-vms71-ucx42.exe Alpha CPU, VMS 7.1, UCX 4.2 + ckv196b11-axp-vms72-nonet.exe Alpha CPU, VMS 7.2, no TCP/IP + ckv196b11-axp-vms72-tgv42a.exe Alpha CPU, VMS 7.2, MultiNet 4.2A + ckv196b11-axp-vms72-ucx50.exe Alpha CPU, VMS 7.2, UCX 5.0 ---------------------------------------------------------------------- ckv193b05-vax-vms44-nonet.exe VAX CPU, VMS 4.4, no TCP/IP ckv193b05-vax-vms44-twg32.exe VAX CPU, VMS 4.4, Wollongong 3.2 ckv196b10-vax-vms45-nonet.exe VAX CPU, VMS 4.5, no TCP/IP + ckv196b11-vax-vms47-nonet.exe VAX CPU, VMS 4.7, no TCP/IP + ckv196b11-vax-vms55-nonet.exe VAX CPU, VMS 5.5-2, no TCP/IP + ckv196b11-vax-vms55-ucx20.exe VAX CPU, VMS 5.5-2, UCX 2.0 + ckv196b11-vax-vms55-pst53.exe VAX CPU, VMS 5.5-2, TCPware 5.3 ckv196b10-vax-vms55-tgv41b.exe VAX CPU, VMS 5.5-2, MultiNet 4.1B ckv195b04-vax-vms55-cmuip.exe VAX CPU, VMS 5.5-2, CMU/IP ckv195b08-vax-vms61-nonet.exe VAX CPU, VMS 6.1, no TCP/IP ckv195b08-vax-vms61-tgv40a.exe VAX CPU, VMS 6.1, MultiNet 4.0AX + ckv195b11-vax-vms62-nonet.exe VAX CPU, VMS 6.2, no TCP/IP + ckv195b11-vax-vms62-ucx33.exe VAX CPU, VMS 6.2, UCX 3.3 + ckv195b11-vax-vms62-ucx41.exe VAX CPU, VMS 6.2, UCX 3.3 + ckv196b11-vax-vms71-nonet.exe VAX CPU, VMS 7.1, no TCP/IP ckv195b04-vax-vms71-pst32.exe VAX CPU, VMS 7.1, TCPware 3.2 ckv195b04-vax-vms71-pst53.exe VAX CPU, VMS 7.1, TCPware 5.3 + ckv196b11-vax-vms71-tgv40b.exe VAX CPU, VMS 7.1, MultiNet 4.0B + ckv196b11-vax-vms71-twg35.exe VAX CPU, VMS 7.1, Wollongong 3.5 + ckv196b11-vax-vms71-ucx42.exe VAX CPU, VMS 7.1, UCX 4.2 + ckv196b11-vax-vms72-nonet.exe VAX CPU, VMS 7.2, No TCP/IP + ckv196b11-vax-vms72-ucx50.exe VAX CPU, VMS 7.2, UCX 5.0
Questions? Comments? -- Send e-mail.
[Top]