When transferring files to WebCom via FTP, do not use MacBinary format. Instead, use plain "binary" or "Raw Data" format. If the GIFs you have transferred to WebCom do not display at all, or appear totally distorted, this is the most likely cause.

The Macintosh, by default, creates "carriage returns" at the end of each line in a text file. In UNIX, a "line feed" is used to mark the end of each line in a text file. In DOS and Windows, both a "carriage return" and a "line feed" are used.

WebCom servers run under the UNIX operating system, and therefore expect a line feed at the end of each line in a text file. Since the Macintosh system uses only a carriage return at the end of each text line, and not a line feed, UNIX software is unable to distinguish between different lines in a Mac format text file (more precisely, it thinks the file contains one, extremely long "run-together" line). This is not a problem for DOS and Windows files since they have the crucial line feed in addition to a carriage return; and UNIX generally ignores the carriage returns.

To create files in a format compatible with WebCom services, use the "Save as Unix Text" option in the program you use to create your Web pages, or, if this is not available, use the "Save as DOS Text" option. In Microsoft Word, save as file type "Text with Line Feeds".

A number of WebCom services may not operate quite correctly if a text file used by the service is saved in Macintosh format. An index of explanations of how all relevant WebCom services are affected is listed below. (You don't need to read these, as long as you save your text files with line feeds).

• The WebCom Forms Processor
• Glimpse Indexing
• The ImageMap Map File
• Distribution List subscriber list files

Note: Files created and edited using the WebCom File Manager, will be saved in UNIX format, and will not experience this problem.