The Kermit Project |
612 West 115th Street, New York NY 10025 USA • email@example.com
READ THIS FIRST:
August 2011: Due to the proliferation of firewalls, network address translators, and the like, FTP — a fundamental Internet standard since 1971 — has become increasingly problematic. For this reason, access to the entire Kermit software archive is now available through your Web browser via HTTP protocol (the protocol used by Web browsers), which for all practical purposes, is never blocked. Now, for the first time, you can download any Kermit program with its source code by clicking on a link to a Zip or Tar.gz file. CLICK HERE to visit the archive. The rest of this page is about FTP, which (as of this writing) is still available for those who are not blocked from using it.
The primary ftp site for Kermit software is:
ftp.kermit.columbia.edu kermit.columbia.edu ftp.columbia.edu
There is no ftp-mail server, and we do not send Kermit software by email -- in most cases it is too big to survive the trip.
These days, the easiest way to access the Kermit ftp site is with a Web browser. Our Web address is:
A page giving quick access to the current releases of the most popular Kermit programs is here:
The web pages guide you easily to the files you need, and give you all the other information you might want -- frequently asked questions, licensing information, etc.
But of course there are drawbacks. Many Web-browser FTP clients give you no control over the mode (text or binary) in which the file is downloaded, nor what becomes of the file after it is downloaded. Furthermore, some Web browsers do not allow FTP transfer of file groups -- only one file at a time may be transferred.
Hint: In most browsers, you might have to right-click on a filename and choose "Save" to make it download, rather than appear as garbage on your screen, or have it fed to a random application.
Windows-based graphical FTP clients are especially annoying, as they like to choose "helper applications" for the file you are trying to download, based on its name, on the often erroneous assumption that it's a Windows file. In the Kermit ftp area, ".doc" files are plain text, not Word For Windows; ".hlp" files are plain text, not Windows Help, and so on. Binaries such as "cku197.sunos41c-4.1.3-sparc" or "k11nrs.tsk" are simply to be ftp'd in binary mode and saved, not associated with any Windows application.
Some of the graphical FTP clients can surprise you; they download the file, but then you can't find it afterwards, either because it put it in a directory you weren't expecting, or it changed the name of the file (case of letters, adding numbers to the end, etc). Or they transferred in binary mode when you needed text mode, or vice versa. If your Web browser or graphical FTP client can't cope with downloads, then use FTP the Old Fashioned Way. Open a Command window on your Windows PC, or a shell window on your UNIX workstation, etc. Then, at the DOS / shell prompt:
and then press the Enter or Return key.
User (kermit.columbia.edu):In response, type the word "anonymous" (lowercase, spelled out in full) and then press the Enter or Return key.
To download text files, first give the FTP "ascii" command, then use the FTP "get" command to download a single file, or "mget" to download multiple files. Please note: If you download text files in binary mode, their record formats might be wrong, but they should still be readable. If the GET or MGET command fails, see the troubleshooting section below.
To download binary files, first give the FTP "binary" command, then use the FTP "get" command to download a single file, or "mget" to download multiple files. Please note: If you download binary files in "ascii" (or text) mode, they will be completely corrupted and you won't be able to use them.
When you are finished, give the ftp "bye" command.
If you download an executable file to UNIX, you have to "chmod +x" the file before you can run it ("man chmod" for details).
You can transform any Kermit Project FTP link into an HTTP one to bypass the firewall. For example, this link:
The Kermit FTP site should be available 24 hours a day, 7 days a week, and serves thousands of files every day to sites all over the world. There are presently no limitations on the number of simultaneous users, the number or size of files you can request, etc. If you have trouble getting into our FTP server, the trouble is almost certainly on your end.
Our FTP server has enough power to keep up with the demand. If you think it is slow, the slowness most likely comes from the Internet connection itself, not from our FTP server. However, in the 24-48 hours after a major Kermit software announcement, the demand can be quite heavy, and this can slow down not only the server, but also key gateways or routers, contention-based network segments, etc. A fact of life. Nevertheless, any time we get complaints that the server is down or not responding, they almost never turn out to be true; inspection of the server usually shows lots of active users at any given time, day or night.
If you have trouble:
If you want to use Columbia University TCP services, you must have a proper DNS entry for your computer, and you must export it so that the Columbia University FTP server can look it up. If this is not the case, ask your ISP or network administrators to rectify the situation (or use HTTP instead of FTP to retrieve Kermit files).
If you are trying to download a new copy of a file (e.g. because we told you we replaced it), but you keep getting the old copy, it's because your ftp client goes through some kind of cache (e.g. a proxy Web server) and due to a bug, time skew, or other problem in your network, the cache is not refreshed when the real file changes. Problems like this can be fixed only by your network manager, ISP, or webmaster.