AppleTalk Connections

Does each file have three parts?

UNIX stores Macintosh files in three forks: the data fork, the resource fork, and the finder information fork. The data fork contains the actual data contained in the file, the resource fork indicates the application to launch when you open the file, and the finder information fork maintains data about the file's creator, type, location on the desktop, and icon.

TAS stores these parts in separate directories. When you create a file from a Macintosh client, TAS writes the data fork writes to the current directory, the resource fork to the subdirectory .tnatr:reso-fork, and the finder information to the file .tnatr:intf. If TAS cannot locate all of these pieces, the file may not launch correctly. In versions of TAS previous to 5.x, TAS writes the data fork to the current directory, the resource fork to the .resource directory and the finder information to the .finderinfo directory.

Does the finder information map file exist and contain the correct information?

The finder maintains information about files, such as the file's creator, type, location on the desktop, and icon. When the server cannot locate finder information, it attempts to generate reasonable default values for this information based on data in the map file. These values may not contain the correct information.

An AppleTalk map associates file suffixes with Macintosh applications. The client operating system uses these associations to determine which application it should invoke when it accesses a file.

Follow these links to check mapping configuration:

• AppleTalk Realm->Suffixes for AppleTalk Map->[select a suffix]->Modify

The Modify button does not appear if no maps exist.

To check mapping configuration from the UNIX command line, use the tnsuffix command.

Do the Macintosh and PC versions of the program share the same data format?

Occasionally, these platforms cannot share files of the same program.