Setup Error Message "Cannot Change Properties of <Filename>"

WORKAROUND

If you receive this error message, do the following to correct the problem:

Delete the Original SETUP.INI from Your Drive

If you receive the error message above, restart the workstation and rerun the Setup program. If Setup, continues to fail, it may be because the original SETUP.INI file is still present as a Read-Only file. To resolve this problem, delete the original SETUP.INI file from your hard disk. Remember that Office MUST be installed to an empty directory.

Modify NET.CFG or SHELL.CFG Files (Novell Only)

1. Locate the file SHELL.CFG or NET.CFG on the workstation from which you are running the administrative setup of Office 4.0. If this file does not exist, create it using a text editor and place it in the same directory as NETX.COM.
2. Open the SHELL.CFG or NET.CFG file in a text editor. In the DOSREQUESTER section, change the line that reads

   READ ONLY COMPATIBILITY=ON
   
   -to-
   
   READ ONLY COMPATIBILITY=OFF

   If this line does not exist, create it. The entry must be indented (default 3 spaces) or it will be seen as an invalid section heading and not be used.
   
   Example:

         NETWARE DOS REQUESTER
            READ ONLY COMPATIBILITY=OFF
   						

   NOTE from Novell: DOS Requester version 1.20 fixes this.

         Read Only Compatibility = Off | On  (default Off)
   						

   This is not a new parameter, but the default has been changed with release 1.20 of the DOS Requester. In the last major release of the Requester this parameter defaulted to On. However, this default setting caused problems with a number of applications, so the parameter is now set to Off by default.
3. If the workstation is using the NetWare VLM shell version 1.1, (Netware 3.11), continue with the steps in the following section "VLM version 1.1". If you are not running VLM version 1.1, continue with steps 4-6 below.
   
   NOTE: In many cases, the procedure described in the section "VLM Version 1.1" will not be required. This process is time consuming. Continue with steps 4 through 6 below and perform the VLM procedure only if the problem persists.
4. Log off of the network, restart the workstation and connect to the server again.
5. Log on to the network, start Windows, and run setup /a from the Microsoft Office integrated Setup to install the application. The MSOFFICE directory must be empty for successful installation to occur.
6. When the application is installed, change the option in the SHELL.CFG or NET.CFG file back to =ON in case there are applications on the system that require this setting.

VLM Version 1.1

If you are using VLM version 1.1, you can obtain this updated version of the VLM shell. Novell has made these files available on CompuServe in the NOVFILES forum and on FTP.NOVELL.COM. VLMUP2.EXE (a self-extracting file) contains all the updated VLMs (Pre-release v1.20), the updated ODI drivers (LSL.COM and IPXODI.COM), the updated MLIDs, and other associated files. To find the version of VLM that you are using, type the following at the MS-DOS prompt: If this command presents too much information at one time, type the following: NOTE: The pipe symbol (|) and the word "more" direct the command to display information one screen at a time

VLM Version 1.1

If you are running VLM version 1.1, use the following steps to resolve this problem. (Note that these steps should be taken AFTER you complete the first two steps in the "Modify NET.CFG or SHELL.CFG Files" section above):

1. Remove the VLM shell and use the NETX shell to complete the administrative setup. If you cannot use NETX, you can install the VLM shell version 1.0. However, because reinstalling VLM version 1.0 is very time consuming, using NETX is the preferred method.
2. Log off of the network and restart the workstation.
3. Log on to the network, start Windows, and run setup /a from the Microsoft Office integrated setup to install the application. The MSOFFICE directory must be empty for successful installation to occur.
4. When the application is installed, change the option in the SHELL.CFG or NET.CFG file back to =ON in case there are applications on the system that require this setting. You can then use the VLM shell version 1.1 again without experiencing any problems.

Note that VLM is the latest version of the shell from Novell, replacing NETX. The VLM shell ships with Netware versions 3.12, 4.00, 4.01, 4.02 and Personal Netware. However, this shell can be used on any version of Netware.