That doesn't make sense. Novell has had namespace and foreign language support (via special nlms) since 2.15. I managed Novell networks for 16 years (up until 4 years ago) and never ran into that problem. the last network had 25 Novell servers on a wan. While MSFT's systems were certainly more user friendly out of the box, nothing beat the security of a Novell Network. I once had servers that had been running for 7 years without ever going down or experiencing problems. I'm glad to be out of the networking field though - too many nights and weekends onsite! :o)



>Hi Tracy,
>
>the long filename support in Novell is not flawless, for instance it is a big problem that it changes the ascii value of all the foreign characters in the filenames. Anyway, I jumped off the Novell bandwagon many years ago.
>
>>Maybe someone should send the adminstrator the below document instead (3.x +):
>>
>>http://support.novell.com/cgi-bin/search/searchtid.cgi?/10019083.htm
>>
>>And for 2.x:
>>
>>From the NetWare server console prompt, type "LOAD OS2"
>>
>>2. From the NetWare server console prompt, type "ADD NAME SPACE OS2 TO SYS"
>>3. Repeat Step 2 for any other volumes on the NetWare server.
>>
>>
>>? :O)
>>
>>>>>SYS(2015) is not safe either, SUBSTR(SYS(2015)3) is safe AFAIK.
>>>>
>>>>Why?
>>>
>>>To be honest, I am not sure. It may be for compatibility with old DOS machines, or Novell servers which are not configured to handle long file names.