WFWG 3.11: UNC Filenames with Word Fail on Novell Network |
ID: Q106021
The information in this article applies to:
- Microsoft Windows for Workgroups version 3.11
- Microsoft Word for Windows, versions 2.0, 2.0a, 2.0a-CD, 2.0b, 2.0c, 2.0c-CD, 6.0
SYMPTOMS
After you install Windows for Workgroups version 3.11, you may not be able to use universal naming conversion (UNC) filenames with Microsoft Word for Windows if you use a Novell network.
RESOLUTION
To work around this problem, add the NovellNet=YES entry to the [Microsoft Word 2.0] section of the WIN.INI file for Word for Windows 2.0. Or add NovellNet=Yes to the [Microsoft Word] section of the WINWORD6.INI file for Word for Windows 6.0.
MORE INFORMATION
NovellNet=Yes specifies how Word for Windows verifies that the directory is valid. For example, if you have the following directory structure
root -----> users -----> personal
Word for Windows will verify that the \USERS\PERSONAL directory exists before it tries to open the file. If that same directory structure exists on a Novell network, as follows
root ------------> users -----------> personal (read only) (no privileges) (read/write privileges)
When Word for Windows tries to access the USERS directory to reach the USERS\PERSONAL directory, the Novell network replies that you have no privileges in that directory; therefore, Word for Windows returns an error message for the task at hand.
The NovellNet setting ensures that Word for Windows changes directories to USERS\PERSONAL before reading the file and then performs a DOS call to change the directory back after it is done. This method works properly because you haven't directly accessed the USERS directory, which may have no privileges.
Additional query words: 3.11 winword 2.0 2.0a 2.0b 2.0c 6.0 6.0a 6.0c
Keywords :
Version : WINDOWS:2.x,3.11,6.0
Platform :
Issue type :
Technology : kbWordSearch kbWordWSearch
Last Reviewed: October 17, 2000 |
