Error installing from Shared CD-ROM on Novell Netware 3.12

ID: Q124763


The information in this article applies to:
  • Microsoft Office for Windows, version 4.3-CD


SYMPTOMS

When you perform a typical, custom/complete, or laptop installation of Microsoft Office for Windows version 4.3-CD and the CD-ROM has been set up as a shared resource on a Novell network, you may encounter the following message

Could not write to the <drive>\custom.dic
Where <drive> is the drive mapped to the CD-ROM server. Following this message, the server may lock up.


CAUSE

This error occurs when Microsoft Office Setup has copied approximately 21% of the files and is trying to create the CUSTOM.DIC file in the MSAPPS\PROOF directory. It occurs in any type of installation, other than an administrative installation, when Microsoft Excel is included in the installation.


WORKAROUND

This problem occurs only when Microsoft Excel is included in the installation. To install Microsoft Office Professional, do either of the following:

  • Perform an Administrative Setup (Setup /a) of Microsoft Office from the Shared CD-ROM to another server and run the setup from the second server.

    -or-


  • Perform a Custom/Complete Setup of Microsoft Office from the shared CD- ROM and do not include Microsoft Excel. In order to install Microsoft Excel, perform an administrative installation of Office to another server and install Microsoft Excel from the other server.



STATUS

Microsoft has confirmed this to be a problem in Microsoft Office version 4.3 for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


REFERENCES

For additional information about performing an Administrative Setup of Microsoft Office, see the following article(s) in the Microsoft Knowledge Base:

Q122522 Performing an Administrative Installation (Setup /a)

Additional query words: 4.30-CD hang freeze stop responding crash

Keywords :
Version : 4.30-CD
Platform : WINDOWS
Issue type :


Last Reviewed: June 18, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.