News
A number of Fetch users have asked whether Fetch is
Year 2000 compliant. The answer is yes: all versions
of Fetch store and manipulate dates in a form that will
not overflow until the year 2040. (8/18/97)
Oops! The recently released Fetch 3.0.2 introduced
a bug in the View File command (the first character
in the file, and subsequent buffers, was dropped).
To correct this mistake, Fetch
3.0.3 has been released; click here
to download it. (3/10/97)
Fetch 3.0.2 has been released. Fetch 3.0.2 includes
many bug fixes, and is the first Mac FTP client to
support resuming downloads, including BinHex downloads.
For a complete list of new features see the "Release
Notes" section of Fetch Help. (3/4/97)
Fetch won
MacUser's 1996 Shareware award in the Internet
category. (8/16/96)
Single-user Fetch licenses can now be purchased over
the web. Go to the Fetch License Form to purchase
a license, or to the Licensing
section to learn more about Fetch licensing terms.
Features
Fetch has the following notable features.
- Multiple
Connections
- Fetch
allows multiple outstanding connections, and automatically
reconnects sessions that have been disconnected.
Drag and Drop
- Fetch
features extensive support for drag and drop (which
requires System 7.5, or else the Macintosh Drag
and Drop extension and Finder 7.1.3 or later). Files
and directories can be dragged to and from remote
sites. URLs can be dragged to bookmark list windows
and text editors. Even some preferences can be set
via drag and drop.
Open Transport
- Fetch
is one of the first applications to ship with Open
Transport code, for better performance on PCI Macintoshes
and soon non-PCI models as well.
Apple Events
- Fetch
is the only Mac FTP client with Apple Event Object
Model support, for easier and more powerful scripting
with languages such as AppleScript, Frontier, and
others. Fetch is also "recordable," so writing a
simple script can be as simple as hitting the "Record"
button in your script editor.
Bookmark Lists
- Fetch
supports multiple bookmark lists, with easy drag
and drop editing and reordering.
Resume Download
- Fetch
is the only Mac FTP client that can restart interrupted
transfers, making it unnecessary to re-download
data that has already been transfered.
Firewalls
- Fetch
supports simple proxy servers, SOCKS gateways, passive
mode transfers, and a user-selected port-number
range, all to make Fetch's operation behind firewalls
more convenient. In addition, Fetch supports the
One-Time Password and S/Key systems for protecting
the privacy of passwords.
Searching
- Fetch
supports the "SITE INDEX" command for searching
FTP archives by file name ("SITE INDEX" is not supported
by all servers).
Permissions
- Fetch
allows simple point-and-click management of remote
file permissions via the "SITE CHMOD" and "SITE
UMASK" commands (not supported by all servers).
File Format Conversion.
- Fetch
supports up and downloading files in AppleSingle,
BinHex, and MacBinary II format, as well as the
common Text and Raw Data formats.
Directory Trees.
- Fetch
can upload, download, or delete entire directory
trees (i.e. directories containing files and/or
sub-directories) with a single command.
Suffix Mapping.
- Fetch
comes with a list of suffix mappings which relate
file name extensions (such as ".gz") to Macintosh
file types (such as MacGzip). Users can modify the
default mappings and add their own as well. Fetch
can also use Internet Config's mappings.
Post-Processing.
- Fetch's
Post Processing feature makes it possible to have
downloaded files automatically passed to designated
helper applications, depending on their type. Fetch
can use Internet Config's post-processing settings
or its own.
URL support.
- Fetch
can access files or directories based on their Uniform
Resource Locator (URL), and can generate URLs for
displayed files.
Text Display.
- Fetch
can display text files, directory listings, and
server messages in its own windows, without requiring
a separate viewing program.
-
Custom Commands.
- Fetch
allows users to type in arbitrary FTP commands,
to navigate firewalls and access server-specific
commands.
History
Fetch
1.0 was written in the summer of 1989, in order to provide
a file transfer solution for Macs talking to Dartmouth's
various host operating systems, and in order to take
advantage of Dartmouth's newly acquired Internet connection.
Version 1.0 was a Macintosh desk accessory, and communicated
with TCP/IP machines via an AppleTalk stream protocol
(the Kiewit Stream Protocol) and Philip D. L. Koch's
KSP<->TCP gateway. Version 1.1 incorporated CStream,
a network class library, which provided support for
MacTCP. Version 2.0 added the ability to transfer directory
trees, suffix mapping, StuffIt! decoding, and AppleSingle
support. A bug fix release, 2.0.6, was the first version
of Fetch available for downloading on the Internet.
Version 2.1 included the Post Processing feature, and
enhanced file list, and text viewing. Version 2.1.1
added minor features, and 2.1.2 included URL support
and Power Mac native code. Version 3.0 was a major upgrade,
with support for multiple connections, drag and drop,
Internet Config, firewalls, AppleScript, and other features.
Versions 3.0.1, 3.0.2 and 3.0.3 fixed bugs, improved
performance, and added support for resuming downloads.
Fetch was and is written by Jim
Matthews.
Licensing
Fetch 3.0 may be freely distributed on Internet file
servers. Use of Fetch, or distribution by any other
means (e.g. on CD-ROM) may require a license, as detailed
below.
Fetch 3.0 is licensed free of charge to educational
institutions and non-profit organizations (i.e. charitable
organizations; government departments and government-
or corporate-funded research organizations do not
qualify). Users not affiliated with an educational
or non-profit organization who wish to continue using
Fetch should purchase a license. A single user license
costs $25. Multiple-user licenses are available at
the following prices: 10 users/$200, 100 users/$1000,
1000 users/$5000, unlimited users/$20,000, unlimited
users and unlimited updates/$30,000. To purchase a
license send a check drawn on a U.S. bank, a domestic
purchase order, an international money order, or Visa/MasterCard
information to:
Software Sales
Dartmouth College
6028 Kiewit Computer Center
Hanover, NH 03755-3523 USA
Phone: 603-646-1999
FAX: 603-646-2810
Note that these prices are for a license, not media;
we expect that licensees will download the software
from the Internet and therefore we do not mail a copy
of the software with the license agreement. Also note
that this license covers Fetch 3.0 and minor updates
(except for the unlimited users, unlimited updates
license, which includes all future versions of Fetch).
Users who have purchased single-user, and 100-user
licenses for Fetch 2.1 are automatically licensed
to use Fetch 3.0 and any minor updates to 3.0. Users
who purchased an unlimited user license for Fetch
2.1 may upgrade to Fetch 3.0 for $2,000, or upgrade
to Fetch 3.0 and all future versions for $5,000.
Fetch 3.0 may be distributed with books or magazines,
provided that no more than 10,000 copies are distributed,
its shareware status is made clear, and that one copy
of the book or magazine is mailed to the above address.
If more than 10,000 copies will be distributed a $2,000
license is available.
Special license rates are available to Internet Service
Providers (ISPs) who wish to license Fetch for their
Mac customers. For details send mail to Fetch@dartmouth.edu.
Distribution of Fetch by ISPs requires such a license.
The Fetch source code is available for licensing for
internal company use, commercial redistribution, and/or
the creation of derivative products. For details send
mail to Fetch@dartmouth.edu.
Limitations
and Known Bugs
Fetch currently has the following notable limitations
and bugs:
- Fetch
only supports simple (userid@host style) proxy servers.
- Open
Transport error messages are frequently displayed
as numbers in the -3000 range rather than as English
text. Disabling Open Transport calls is the only
workaround.
- Interrupted
transfers can only be resumed in the same Fetch
session.
These
issues may be addressed in a future version of the software.
Common
Questions
Some common questions about Fetch:
Q: When I upload GIF or JPEG files with Fetch 3.0
the bottom bit of the image does not show up.
A: That is a bug in Fetch that was fixed in Fetch
3.0.1 (and is still fixed in the latest version).
You should upgrade to the latest release (see the
News section, above).
Q: When I upload GIF or JPEG files in MacBinary format
my web browser can't display them.
A: Web browsers (and a lot of other software) do not
expect to find files encoded in a format like MacBinary
II; they expect to find the bare data. So use Raw
Data format for uploading web graphics, or other cross-platform
files.
Q: When I try to open a connection I get a -3221 or
a -3264 error.
A: Those are Open Transport errors (along with any
other error code in the range -3300 to -3000). You
should double check the settings in your TCP/IP control
panel, with the help of your ISP. If that does not
help try checking the "Don't make Open Transport
calls" box in the Misc. section of Preferences.
Q: Fetch can download files but when I try to upload
a file over my modem connection the computer freezes,
or the upload fails.
A: There is probably a problem with the flow-control
settings of your dial-up software or your modem. Make
sure that your modem init string enables hardware
handshaking, and that your dial-up software is configured
to do hardware handshaking. Consult your modem manual
or service provider for more information. Alternatively,
if you are using a Dayna ethernet card the problem
is a bug in the ethernet driver; contact Dayna for
an updated driver.
Q: When I try to open a connection, my computer freezes.
A: Check the configuration of your SLIP or PPP software,
and consult with the administrators of the dial-up
service you are using. This sort of problem is usually
caused by misconfiguration of the dial-up software.
Q: When I try to get a file from an IBM MVS server
Fetch creates an empty folder.
A: This is due to a bug in the server (and affects
some other servers besides IBM's). The workaround
is to check the "Treat mystery items as files"
box in the Misc. section of Preferences.
Q: I have a 14,400 bps modem, but I only get 1000
bytes/second.
A: Modems use 10 bits to send a byte, so 1000 bytes/second
over a modem translates to 10,000 bps. In addition
to data, your modem must also transmit packet headers,
acknowledgements, and other information. So you should
not expect to always get the modem's rated speed in
actual data throughput. If you think that your throughput
should be better (e.g. it is less than 80% of the
modem's rated speed) you should check your modem init
string and the configuration of your dialup software,
or check with your network service provider.
Q: Fetch slows down and eventually drops the connection
when I transfer a file over my dial-up link.
A: Check the configuration of your SLIP or PPP software,
and consult with the administrators of the dial-up
service you are using. This sort of problem is usually
caused by misconfiguration of the dial-up software.
Q: The file list includes other information besides
the file name, and the Get File button doesn't work.
A: Try refreshing the file list by choosing the "Refresh
File List" command from the Remote menu; that will
usually fix this problem. Otherwise you can hold down
the option key when you press the Get File button
and type in the file's name by hand.
Q: I can't connect to ftp.apple.com with Fetch but
I have no problem connecting from a Unix machine.
The server at ftp.apple.com requires that its clients
be assigned an official domain name. Your network
administrator may not have assigned names to the addresses
used by Macintoshes running MacTCP; that would cause
connection attempts from your Mac to fail while a
Unix machine succeeds. Your network administrator
can resolve this problem by assigning names to those
addresses.
Q: When I tell Fetch to send the FTP command "ls"
I get an error message about the command
"LS" ; why does Fetch capitalize the
command?
A: Fetch does not capitalize the command, the server
does. In fact capitalization of FTP commands does
not matter. The problem is that "ls" is
not an FTP command; it is a command used in many command-line
FTP clients, such as the standard Unix client, but
it is not a part of the FTP protocol. The corresponding
FTP command is "NLST". Similarly, "dir"
, "get", "put", and "cd"
are not FTP commands; the proper commands are "
LIST", "RETR", "STOR", and
"CWD."
Q: The file names in the file list don't look right
-- there is size and date information in the name
column.
A: Fetch sometimes guesses what kind of computer it
is talking to, and it can guess incorrectly. You should
be able to correct the problem by refreshing the file
list -- choose the current directory from the directory
pop-up menu above the file list.
Q: The files I get don't have the right icon.
A: This problem can be caused by a number of factors.
First be sure that you are using the right settings
-- if you've tried the Automatic setting
try Binary . It may also be helpful to read
the "Automatic/Text/Binary" help topic under
"Reference." If you are using System 4.2
and Finder 6.0 you should upgrade since that system
version has a bug that causes files to lose their
icons. If you use MultiFinder you should try saving
the file to a folder that is not currently open in
the Finder. The Finder's Get Info... command
sometimes fixes incorrect icons under MultiFinder.
If all else fails send mail to Fetch@dartmouth.edu.
Q: I can connect to a machine on my local network
but not to Internet FTP servers.
A: Check the Gateway Address section of the MacTCP
control panel, and make sure it contains the right
address. Also, check with your network administrator
to see whether you are separated from the Internet
by a firewall.
Q: I get the message "This is not a proper BinHex
format file."
A: This means that Fetch could not successfully de-binhex
the file. You should try unchecking the BinHex4
Format button in Preferences and downloading
again (see the "Preferences" help topic
under "Reference"). Then try to de-binhex
the file with either BinHex4 or Stuffit!
, two Macintosh utilities. If they succeed please
send a note to Fetch@dartmouth.edu, since this indicates
that Fetch has a bug. Otherwise the problem may be
that the BinHex file is incomplete. If it has other
pieces you will have to get them the same way and
assemble them on your Macintosh before running
BinHex4 or Stuffit! . Finally, the file
may just be corrupted. In that case contact the source
and ask for a new copy.
Q: I get the message "This is not a proper MacBinary
II file."
A: This message, and other ones about MacBinary I,
AppleSingle, StuffIt! and MacHost format files, mean
that the file has been corrupted in some way. Contact
the source of the file to get a new copy. If the file
was created by Fetch send a report to Fetch@dartmouth.edu
so we can try to find the bug.
Q: The Cancel button doesn't work when I'm connected
to a VMS Vax.
A: We have observed problems with Cancel on VMS and
CMS systems. We're working on these problems and in
the meantime you can cancel a transfer by closing
the connection altogether.
Return
to top
To Dartmouth Home
Page
Last edited 5/18/98 by Jim
Matthews
|