The information in this article applies to:
SYMPTOMSIf you build a program on a network drive without having write priviledge to the root drive, the following error is generated by BINDMSF after linking: The .EXE file created will not run under MS-DOS or Windows. CAUSE
After linking a FORTRAN PowerStation application, the executable must be
bound by BINDMSF. BINDMSF creates a temporary file in the root of the
directory containing the .EXE file. If this directory is write protected,
the file can't be created, and the executable will not be bound to the
DOS extender.
RESOLUTION
There are three ways to work around the problem of a write protected drive:
-or- -or- MORE INFORMATION
The Microsoft binder utility BINSMSF attempts to create a temporary file in
the root directory of the drive that contains a project -- or the root
directory of the current directory when using the command line tools like
FL32 to build programs. This file is named '\2'. For example, if your file
server is mapped to drive R:, and you build a program in the
R:\WORK\PROJECT directory, the BINDMSF attempts to create the file named
'\2' in R:\ directory.
RIGHTSThe RIGHTS command generates output similar to this:
Workaround: Mapping the Directory that Contains the ProjectOne way to work around insufficient access rights in the root directory involves mapping the directory that contains the project as the root directory for the project drive. The Novell MAP ROOT command is provided for this purpose. For example, to map the WORK\PROJECT directory as the root of drive R:, enter the following at the MS-DOS command prompt:
The "SYS:" in the command line represents the volume on the file server on
which the project is installed. Novell volumes are similar to MS-DOS disk
partitions (C:, D:, and so on). To determine the correct volume, examine
the output of the RIGHTS command, as shown above.
After you enter the MAP ROOT command shown above, Novell uses the WORK\PROJECT directory as the root directory for drive R:. In other words, when the current directory is R:\, the WORK\PROJECT directory on the SYS: volume is actually the current directory. As long as the project is opened in the Visual Workbench from the R: drive, when the binder creates its temporary file in the root directory of the R: drive, it actually creates the file in the WORK\PROJECT directory on the SYS: volume. If the user has the necessary rights in this directory, the file creation and deletion operations succeed. Because the project directory contains the source code files, the user should have the right to search for, create, read from, write two, and erase files in that directory. You can also define a drive mapping as a root drive by using the Microsoft Windows File Manager in Microsoft Windows for Workgroups version 3.1. To do this, the Windows for Workgroups installation must include Novell NetWare support. To create a drive mapping in File Manager, perform these 11 steps:
REFERENCESFor more information on granting rights and mapping drives on a NetWare network, please refer to your Novell NetWare documentation. Additional query words: 1.00 1.00a
Keywords : |
Last Reviewed: November 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |