Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Long filename on a Novell 3.12 server
Message
De
06/07/1997 13:55:42
 
 
À
06/07/1997 09:22:53
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00038733
Message ID:
00038737
Vues:
34
Hi Per! I've found article in win95 RK which looks useful to you: Supporting Long Filenames on NetWare Servers Computers running Windows 95 can use long filenames on NetWare 3.x and 4.x volumes configured to use the OS/2 namespace, which emulates an HPFS volume. Filenames on such NetWare volumes have a maximum length of 254 characters and use an 8.3 truncation on the first instance of the filename. For example: longfilenameold.tst --> LONGFILE.TST longfilenamenew.tst --> LONGFIL0.TST To enable long filenames on a NetWare volume 1. At the NetWare server console prompt, type the following lines: load os2 add name space os2 to volume sys 2. Then add the following line to the STARTUP.CNF file: load os2 3. Shut down the file server. Then copy the file OS2.NAM from the NetWare distribution disks or compact disc to the same disk and directory that contains SERVER.EXE on the NetWare file server. 4. Restart the NetWare file server. If you have problems with this procedure, contact Novell for more information. When you use long filenames for files on a NetWare volume while running Windows 95, the following exceptions occur: ¹ You cannot use a combination of short names and long names for a path used in an MS-DOS Prompt window ¹ You cannot use cd in an MS-DOS Prompt window to switch directories using first a long filename, then using a trunctated name, or vice versa ¹ You cannot use dir in an MS-DOS Prompt window to check a directory on a NetWare server if you used a truncated name to switch to that directory To avoid these problems, use Windows Explorer. Otherwise, avoid long directory names if you do a lot of work at the command prompt. NetWare 3.11 servers experience problems with applications that open a large number of files. Error messages report these problems as sharing or lock violations, or report a “file not found” error when you know the file exists, or report other errors in opening files. Novell supplies a patch for this problem, which you can obtain from the Novell forum on CompuServe¯. However, if you have not applied the patch, this problem affects how NetWare 3.11 servers handle long filenames, even if the OS/2 namespace is enabled. To avoid such problems, Windows 95 Setup only enables long-filename support with NetWare servers version 3.12 or higher. If the NetWare patch has been applied at your site, you can ensure support for long filenames with all NetWare servers by setting SupportLFN=2 in the following Registry key: Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\Nwredir The possible values for this Registry key are the following: ¹ 0, which indicates that long filenames are not supported on NetWare servers. ¹ 1 (the default), which indicates that long filenames are supported on NetWare servers version 3.12 and greater. ¹ 2, which indicates that long filenames are supported if the NetWare server supports long filenames. This can include NetWare 3.11 servers where the patch has been applied. These values can also be set globally using system policies. The related policy name is Support Long Filenames under the policies for Client for NetWare Networks. Have a happy day Vladimir Shevchenko > I installed my software on a novell 3.12 server, but Im using long > filename. > Is there a solution on this problem. Is there a *.nam file for win95 files > or??
* Human is a question asked by birth and answered by death. Machine is another kind of question with another kind of answer
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform