Both UNIX and Windows include a set of valid file name characters; however, these sets are different for each program. If you do not turn on and configure character translation, Server for NFS cannot create some valid UNIX file names and you may receive an error message if you try to create a file. The following list includes examples of characters that are supported in file names in UNIX but are not supported in Windows:
Creating a Character Translation File for Server for NFS
To create a character translation file for Server for NFS, you must use a pure ASCII text editor, such as Notepad. Do not use a word processing program. The format of the file is a list of mapped characters and their translations. The following text is an example of an entry in the file, where nn is the hexadecimal value for the character and the character is shown in double-byte mode:
0xnn 0xnn : 0xnn 0xnn [ ; comment]
All text on the line after a semi-colon is ignored as a comment. To use the translation file to map the question mark (?) to a dash (-), type the following line in the file:
0x00 0x3f : 0x00 0x2d ; replace client ? with server dash "-"
To prevent problems, you may want to translate the following characters:
Asterisk (*): 2a
Colon (:): 3a
Question mark (?): 3f
Note The hexadecimal numbers in the character translation file must be exactly two digits.