Use the Files and Folders tab to set preferences for case handling and how folders are created.
Showing NFS files with archive attribute checked specifies that you want to see when a file has the DOS archive attribute set, although it has no meaning in NFS.
You can determine which case NFS should use when creating new files and doing file lookups. The preferred case is used only if the next option (Create File Names In Preferred Case) is selected.
The default selections for the two Case Handling options are intended to replicate the case-handling behavior of Windows 95 and Windows NT. Windows will allow you to create file names using mixed case. However, unlike UNIX, Windows cannot differentiate between two files with the same name but different cases in the same directory.
For this reason, you should not create files or directories on your NFS server whose names are the same except for case. For example, you should not create one directory named STATUS and another named status within the same parent directory.
Create File Names In Preferred Case causes NFS to create and save files using the case specified in the previous field, Preferred Case.
For example, if you select Uppercase as the preferred case and then select Create File Names In Preferred Case, all file names you enter will be converted to uppercase.
Use Case Sensitive File Name Lookup specifies that NFS should look up file names using the preferred case. This option is available only when you first select Create File Names In Preferred Case.
For example, if you select Uppercase as the preferred case, select Create File Names In Preferred Case, and then select Use Case Sensitive File Name Lookup, all file names will be created in uppercase, and a file lookup will look for the uppercase version of the file name searched for. If this feature is selected and you use Explorer to enter the directory on your NFS server called status, NFS looks for the directory STATUS. You will see an error such as D:\Status is not accessible. The folder was moved or removed. The folder is still there, but NFS cannot find it because it is looking for a different name.
If Use Case Sensitive File Name Lookup option is not selected, a file name lookup will first look for the file in the case in which it was created. If that instance of the file is not found, then file name lookup will search the entire directory. It uses the first instance of the case-insensitive version of the file that it finds.
For example, if you select Uppercase as the preferred case, then select Create File Names In Preferred Case, and then do not select Use Case Sensitive File Name Lookup, all file names will be created in uppercase, and a file name lookup will first look for the uppercase version of the file name searched for. If the file name is not found, then NFS will continue to search the entire directory in a case-insensitive manner.
Case-insensitive lookups are slower than case-sensitive lookups, but are more compatible with the way Microsoft Windows looks for file names.
Determine how NFS handles the group identification (GID) assigned to files it creates. UNIX System V normally assigns to a file the GID of the process that creates it. However, if the parent folder was set up to pass its GID to all files created within it, System V assigns the GID of the parent folder to the new file. Berkeley Software Distribution (BSD) UNIX always assigns the GID of the creating process to a new file.