Microsoft KB Archive/133194

From BetaArchive Wiki

WP Kit Batch Mode Setup Doesn’t Install Shared Items to Server

PSS ID Number: Q133194 Article last modified on 07-27-1995

6.00 6.00a 6.00c

WINDOWS

The information in this article applies to:
- Microsoft Word for Windows, versions 6.0, 6.0a, 6.0c

SYMPTOMS

Shared items are installed locally even when “Server” is selected during the Administrative installation.

When running a Batch Mode Setup (also called Quiet or Silent Mode Setup) for the WordPerfect Conversions Kit using the /q switch, shared items are not installed in the Msappsand Msappsserver directories as specified in the Administrator’s installation.

Shared items are installed on the user’s workstation in the local Msappsand Msappsdirectories instead of on the server.

CAUSE

The WordPerfect Conversions Kit setup table, Setup.stf, is not correctly written. The “Batch Mode Root Object ID” does not call a routine that functions correctly, and the “&Complete” and “C&ustom” Batch Mode installation objects need to be set to no.

WORKAROUND

Modify the Setup.stf file in the Administrator’s Setup folder on the server.

If the WordPerfect Kit was previously installed on the workstation, the installed WordPerfect Kit components (particularly the Wpksetup.stf in the Word directory and the items in the Msapps subdirectories) need to be deleted.

If there is a local Msapps directory on the workstation, then the shared items will be installed locally. No modifications to the .stf file will point those items to another location.

NOTE: Although PSS will support some modifications to a copy of the Setup.stf file, PSS will NOT support modification of the Wpkit.inf file. Note also that while PSS will help customers modify specific lines of an .stf file, we will not rewrite the entire file in order to achieve a desired configuration. As a general rule, support is limited to options that can normally be changed by a user during a standard installation of the application.

To modify the Setup.stf file located on the server, do the following:

  1. The Administrator should make a copy of the Setup.stf file and rename it from Setup.stf to Setup.old.
  2. Open the Setup.stf file in Microsoft Excel by clicking Open on the File menu. Note: Do not open the file by double-clicking the Setup.stf file in File Manager.
  3. In the Text Import Wizard, click the Next button twice (to get to step 3 of 3 of the wizard).
  4. Select the second column in the Data Preview.
  5. Click Text in the Column Data Format box, and click Finish.
  6. Select Row 19, Column B (to the right of “Batch Mode Root Object ID”). This cell will contain the text “11 : 1” (without the quotation marks).
  7. Change the “11 : 1” to “14 : 1” (without the quotation marks).
  8. Select Row 43, Column B. This cell will contain the word “yes”.
  9. Change the “yes” to “no”.
  10. Select Row 44, Column B. This cell will contain the word “yes”.
  11. Change the “yes” to “no”.
  12. On the File menu, click Save As. Leave “Save File as Type” set to “Text (tab delimited)” and save the file.
  13. On the File menu, click Close. You’ll see the following message: “Save changes to ‘SETUP.STF’? Note: The current file format is not Microsoft Excel Workbook”.
  14. Click the No button.

MORE INFORMATION

This problem occurs if the Administrator chose “Server” when prompted for a location for shared items during an Administrator’s Setup (SETUP /a), then a user subsequently attempts to run a Batch Mode Setup (SETUP /q ).

This problem does not occur when a user runs a Workstation installation without the /q switch.

Affected shared items include the following:

Wpft5.cnv Wpft5.equ Wpft6.cnv Wpgexp.flt Wpgimp.flt

For additional information, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q119275 TITLE : Setup Error: Setup Cannot Update an Installation in Batch Mode

KBCategory: kbsetup kb3rdparty KBSubcategory: Additional reference words: textconv supplemental Installation Install network winword 6.00 ============================================================================= Copyright Microsoft Corporation 1995.