Sending Files

Locate the file you wish to send in the Local Browser on the left side of the window as previously described.  Enter the server address, port number, and, if needed, a username and password.  You may wish to browse the server's files and select a destination for your upload first.

If you select an existing file as your destination, it may be overwritten.

When you are ready to send the file, double click on the file in the Local Browser window, or single click on its entry then press the "Send" button.  Note that if the server is designated "Read-Only" or if you do not have write permission for the selected destination, then you will receive an Authorization error.

ExpeDat 1.11 servers will store the uploading data and related information in temporary files until the upload completes.  These may appear in the remote browser as files with types 'M' and 'T'.  For more information about partial uploads, see the section on Resuming Sends.

Once a file has been successfully uploaded, the server will attempt to set the modification date, access rights, ownership, and group id of the uploaded file to match those of the local file.  Whether or not this is successful will depend on the server version, operating systems, and your login access rights.

Warning about Symbolic Links

Symbolic links are pointers to files located in another part of the filesystem.  They will appear in the file listing with a type of '@'.  Targeting symbolic links can produce unexpected results.

Sending an individual local symbolic link is not currently supported.  Instead, you must navigate to the original file.  If a symbolic link points to a directory, you may browse that directory either by typing the link's path in the Local Path field, or by using the Browse button.

Windows shell links (".lnk" files) are not followed.  Instead, the link itself will be transferred.

This behavior is likely to change in future releases.

Irregular Files

Other irregular files (devices, sockets, pipes, etc.) also cannot be sent or targeted as the destination of a Send.  If an irregular file already exists at the destination path, then the upload will fail with an "Object Unavailable" error.  This behavior may change in a future release.