Q115294 - Project: SETUP.WRI Has Incorrect Network Instructions

Project: SETUP.WRI Has Incorrect Network Instructions

Q115294

The information in this article applies to:

Microsoft Project for Windows, version 4.0

SUMMARY

Microsoft Project version 4.0 ships with a file named SETUP.WRI. A section in this file, "Customizing Microsoft Project for Windows Installation for All Workstations," lists modifications you must make to the SETUP.STF file in order to run the Setup program in batch mode. However, when you run Setup with the modifications outlined in the SETUP.WRI file, one of the following may occur:

Setup installs the Typical installation even though you chose the Workstation installation.

Setup quits and you receive the error message "Microsoft Project 4.0 Setup was not completed successfully."

Setup quits and you receive the error message "Object ID x Invalid Destination Directory field: <drive\directory>," where x is the line number and <drive/directory> is the drive and path where you chose to install Microsoft Project.

Setup runs and gives the message that setup was successful, but Setup does not create Program Manager icons. Also, only the SETUP.STF file is copied to the workstation.

MORE INFORMATION

Listed below is a corrected version of the "Customizing Microsoft Project for Windows Installation for All Workstations" section of the SETUP.WRI file. This corrected version contains the necessary steps to create a SETUP.STF script that allows the setup program to run unattended.

Customizing Microsoft Project for Windows

You can create an installation script to control how Setup installs Microsoft Project so that workstation users can run Setup unattended. With a script, you can:

Perform a complete installation automatically, without input from the user.

Control which type of installation (Typical, Complete/Custom, Laptop (minimum), or Workstation) you want Setup to perform.

Specify the directory in which to install Microsoft Project.

Ensure that all installations in a workgroup are the same.

To customize an installation script, do the following:

Before you can create custom installations for end users, you must install Microsoft Project on your network file server. See "Installing Microsoft Project for Windows on a Network" above (this refers to running SETUP.EXE with the /A switch: a:setup/a).

Copy the SETUP.STF file in the directory in which you installed Microsoft Project, and then rename the copy of SETUP.STF to SETUPSTF.BAK to preserve the original installation options.

Open SETUP.STF in any spreadsheet application, word processor, or text editor. It is easiest to work with the file in a spreadsheet application, such as Microsoft Excel.

NOTE: SETUP.STF is a tab-delimited file.

Locate the following installation options in the third column (the 3rd column, 31st row):

Typical Complete/Custom Laptop (Minimum) Workstation

The word "Yes" should be next to Typical in column 2. This is the default option.

Type "yes" (without the quotation marks) in the column to the left of the type of installation you want. The other options should be blank, or "no."

If you select Complete/Custom, you can then specify which of the options get installed in rows 40-43 of column 2:


   Microsoft Project
   Online Help, Examples and Demos
   Tools
   Sample Templates

If you do not want Microsoft Project installed into the default "C:\WINPROJ" directory, then search for "C:\WINPROJ", and substitute the DRIVE\DIRECTORY that you want Microsoft Project installed to and leave all other information intact. If you are editing this file in Microsoft Excel, this information can be found in cell F24.

If you have chosen to install the Workstation option in step 5, search for the line that says "Batch Mode Root Object ID." In the adjacent column, (the 2nd column, 19th row) replace the value that says "5:01" with "6:01" (without the quotation marks). If you are editing this file in Microsoft Excel, this information can be found in cell B19.

Save the file. Be sure and save it in text-only format.

When setup is run, you must use the /q switch. The following table lists other switches you can use along with the /q switch:


   Switch  Definition  Used for                      Example
   ---------------------------------------------------------------------

   /n      username    This is used to force the     /n "Bill Jones"
                       user name.

   /t      tablename   This is used to substitute    /t "MINIMAL.STF"
                       the name of the new script
                       for tablename.

Note also that in the "About Licensing a Server" section of SETUP.WRI, the steps in "To license a server" are incorrect. You can safely ignore the steps in this section.

Additional query words: workstation wrong bad quiet invalid regload winproj.reg

Keywords :
Issue type :
Technology :