Can't Change Status of System Subdirectory in Network Install

 Last reviewed: September 16, 1996
Article ID: Q117901
The information in this article applies to:
  • Microsoft Office Assistant for Windows, version 1.0

SUMMARY

Section 10 of the OAREADME.TXT file (located on Microsoft Office Assistant Disk 1) directs the system administrator to set the protection status of the Windows System subdirectory to read/write. This information may be confusing, because a network installation of Microsoft Windows does not have a System subdirectory.

MORE INFORMATION

Section 10 of the Microsoft Office Assistant 1.0 OAREADME.TXT file, "Tips for Network Administrators," contains the following information: 

   INSTALLING TO WINDOWS ON A NETWORK: When running the Office Assistant
   Setup program, set the Windows System directory to read/write so the
   Setup program installs the .TTF and .FIF files correctly.
This information is incorrect. A network installation of Microsoft Windows does not have a System subdirectory and, therefore, the .TTF and .FIF files from the Office Assistant installation must be placed in the Windows directory. This section has been revised in Microsoft Office Assistant version 1.0-CD. The revised paragraph states: 

   INSTALLING TO WINDOWS ON A NETWORK: If the Windows server directory is
   set to read-only, the Office Assistant Setup program will fail. Before
   running the Setup program, make sure no one else is using the system,
   and then set the directory to read/write. After the Setup program
   correctly installs the .TTF and .FIF files, set the Windows server
   directory to read-only again.

KBCategory: kbsetup kbdocerr
KBSubcategory:

Additional reference words: 1.00 offasst location files /a docerr




THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.