Ref: 10710028
Title: Some General 3+Mac release notes, file naming idiosyncracy
Date:  7/5/88

Copyright 3Com Corporation, 1991.  All rights reserved.

If you format a 3Server3 using non-default values in 3DISK, the
server will hang when the server-user attempts to share a folder
(directory).  After this happens, reboot the server and all
should be fine.  The shared folder should be there and
accessible.

The application FEDIT from MacMaster Systems cannot be used to
examine shared folders.

If your Home Folder is opened on the desktop and is empty, the
line indicating number of items, bytes on the disk, and bytes
available will occasionally flash.  The Finder is checking the
network for new items and doing a screen refresh.  To eliminate
the flashing, copy or create a file or folder in the Home
Folder.

After using PEEK, you must reboot your netstation.  (This is a
developer's tool.)

From within MPW, you cannot unlink or log out if files are open on
a shared folder.  (This is another developer's tool.)

File-naming idiosyncracy to be aware of:  Since the server software
is designed to support both DOS and Macintosh clients, the server must
maintain Mac and DOS names for all files and folders.  Within a folder,
all Mac names must be unique and all DOS names must be unique.

If a Mac user attempts to move or rename a Mac file/folder, there
is a chance that a conflict in DOS names will be encountered and a
message will appear indicating that an "object by that name already
exists."  To the Mac user, no such object is visible.  However, if
you look around, you will probably detect which Mac object is being
referred to.  For example:

1.  Create the following two Mac folders in separate directories:  Empty
Folder, Empty Foot Locker.

2.  Now attempt to move them into an empty directory.  Since they
both map to "Empty_Fo", there will be a DOS name conflict and
the move will not be permitted.  If you change the name, move
the object, and then rename the file, there will not be a
problem.

Another situation where these conflicts arise is if a Mac object is
being created with or renamed to a name already taken as the DOS
name of another Mac object in the folder.  This will result in
similar messages.  If the Mac name is a legal DOS name, then its
DOS name and Mac name must be identical.
