Microsoft KB Archive/124966

{|
 * width="100%"|

Microsoft Project 4.0 Setup Information

 * }

Q124966

-

The information in this article applies to:


 * Microsoft Project for Windows, version 4.0

-

SUMMARY
The following information discusses Microsoft Project Setup, including how to change your working directory after a workstation installation, incorrect information in the SETUP.WRI file, and the files that are installed with the different installation types. This information is contained in the following sections:


 * Changing Working Directory on Server After Workstation Installation


 * Incorrect Network Instructions in SETUP.WRI
 * Too Many Files Installed On Local Workstation
 * Files Installed with Each Installation Type

Changing Working Directory on Server After Workstation Installation
When you perform a workstation installation of Microsoft Project, your Microsoft Project working directory is set to the directory on the network server instead of the directory to which you installed Microsoft Project on the workstation.

CAUSE
When you run the Microsoft Project Setup program, the default directory (working directory) is set to the directory to which you installed the application. For example, if you installed Microsoft Project to C:\WINPROJ, the directory that is selected in the Directories list when you open or save files is C:\WINPROJ.

However, when you perform a workstation installation so that you are running Microsoft Project from a network server, the working directory is set to the network server directory as well.

WORKAROUNDS
To change the working directory for Microsoft Project, use any of the following methods.

Method 1: If you start Microsoft Project using the Program Manager icon:


 * 1) At Program Manager, click the Microsoft Project icon to select it.
 * 2) From the File menu, choose Properties.
 * 3) In the Working Directory box, enter the path for your working directory.
 * 4) Choose OK.

When you run Microsoft Project by double-clicking the icon, the working directory will be the directory that you entered in the Properties dialog box.

Method 2: If you start Microsoft Project using the button on the Microsoft Office Manager (MOM) toolbar, do the following:


 * 1) From the Microsoft Office menu, choose Customize.
 * 2) Select either the Menu tab or the Toolbar tab.
 * 3) Select Microsoft Project from the list of applications, and choose the Edit button.
 * 4) In the Working Directory box, enter the working directory.
 * 5) Choose OK to accept the changes.
 * 6) Choose OK to close the Customize dialog box.

When you run Microsoft Project by choosing the Microsoft Project icon on the MOM toolbar, or by choosing Microsoft Project from the Microsoft Office menu, the working directory will be the directory you enter in the Customize dialog box.

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

"Q113820 Working Directory on Server After Workstation Install"

INCORRECT NETWORK INSTRUCTIONS IN SETUP.WRI
Microsoft Project version 4.0 ships with the file SETUP.WRI, which contains information on setting up and using Microsoft Project on a network. 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 symptoms may occur:


 * Setup installs a Typical installation even though you chose the Workstation installation option.
 * 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: ," where x is the line number and  is the drive and path where you chose to install Microsoft Project.
 * Setup runs and displays the message indicating that Setup was successful, but Setup does not create Program Manager icons. Also, only the SETUP.STF file is copied to the workstation.

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:


 * 1) 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).
 * 2) Make a copy of 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.
 * 3) 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.
 * 1) 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" in the column to the left of the type of installation you want (without quotation marks). 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 to 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 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 you run Setup, 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. 

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

"Q115294 Project: SETUP.WRI Has Incorrect Network Instructions"

TOO MANY FILES INSTALLED ON LOCAL WORKSTATION
When you perform a workstation installation of Microsoft Project, the sample template files and the sample macro files are copied to the PROJECT directory. These files should not be located in the PROJECT directory; the only file that should be copied in this directory is the SETUP.STF file.

The SETUP.STF file that is created when you run an administrative installation (setup /a) of Microsoft Project has an incorrect entry that causes the Setup program to place the sample template files and the sample macro files [approximately 2 megabytes (MB) worth] in the PROJECT directory.

WORKAROUND
To avoid having the workstation installation copy the sample template files and the sample macro files to your Microsoft Project directory, do the following:


 * 1) Make a copy of the SETUP.STF file in the directory to which you installed Microsoft Project, and then rename the copy of SETUP.STF to SETUPSTF.BAK to preserve the original installation options.
 * 2) 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.
 * 1) Search for the line that reads "Workstation Local." In the third adjacent column, (the 5th column, 36th row) replace the value "17 18 19 20" with "17 18" (without quotation marks). If you are editing this file in Microsoft Excel, this information is located in cell F36.
 * 2) Save the SETUP.STF file. Run the setup program SETUP.EXE from the directory to which you installed Microsoft Project.

NOTE: Before you can create custom installations for other users, you must install Microsoft Project on your network file server. See the SETUP.WRI file for more information about running SETUP.EXE with the /a switch (drive\setup /a).

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

"Q118770 Project: Too Many Files Installed Local Workstation"

NOTE: 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.

FILES INSTALLED WITH EACH INSTALLATION TYPE
Microsoft Project has four types of installations: Typical, Laptop(or Minimum), Workstation, and Complete/Custom. The table below shows the total hard disk space required for each installation type.

<pre class="FIXEDTEXT">                 Total:      Total: Files in      Total: Files Kilobytes (K)   All Files   WINDOWS Directory    in  WINPROJ Directory -- Typical       16,998,157     4,844,366           12,153,791 Minimum        8,927,656     3,164,429            5,763,227 Workstation    5,593,288     4,864,638              728,650 Complete      17,898,854     4,864,638           13,034,216 Files that are temporarily used during setup have a combined size of 274,424K.

NOTE: These sizes are the approximate maximum for the chosen option.

The following is a complete list of all files, sizes, their destination directory, and which type of installations they are installed with.

NOTE: Files with the (*) may not be installed.

"OPENMAIL.EXE is only installed if a mail system is detected." "MSSP_BR.LEX is only installed if something other than United States is selected for the Country setting in the Control Panel." "MAPIVIM.DLL is only installed if a VIM compliant mail system is detected." "Files with the (**) should not be installed during a Workstation installation, but are. For more information, see the 'Too Many Files Installed On Local Workstation' section above." <pre class="FIXEDTEXT">                                                      Type of Installation File Name     Destination Dir              Size (K)   Typ  Min  WkS  Cmp

OPENMAIL.EXE  \WINDOWS                     50,738     X*   X*   X*   X* MSINFO.EXE     \WINDOWS\MSAPPS\MSINFO       40,960     X         X    X MSSP_AM.LEX    \WINDOWS\MSAPPS\PROOF        176,839    X         X    X MSSP_BR.LEX    \WINDOWS\MSAPPS\PROOF        176,298    X*        X*   X* MSSPELL.DLL    \WINDOWS\MSAPPS\PROOF        86,016     X         X    X ANIBUTON.VBX   \WINDOWS\SYSTEM              99,888     X    X    X    X APPEXEC.DLL    \WINDOWS\SYSTEM              8,192      X    X    X    X BTTNCUR.DLL    \WINDOWS\SYSTEM              18,128     X    X    X    X CMDIALOG.VBX   \WINDOWS\SYSTEM              18,688     X         X    X COMMTB.DLL     \WINDOWS\SYSTEM              40,784     X    X    X    X COMPOBJ.DLL    \WINDOWS\SYSTEM              102,400    X    X    X    X CTL3D.DLL      \WINDOWS\SYSTEM              20,272               X    X CTL3DV2.DLL    \WINDOWS\SYSTEM              21,648     X    X    X    X GIZMOBAR.DLL   \WINDOWS\SYSTEM              14,080     X    X    X    X GRID.VBX       \WINDOWS\SYSTEM              45,136     X    X    X    X MAPIVIM.DLL    \WINDOWS\SYSTEM              55,744     X*   X*   X*   X* MSAJT200.DLL   \WINDOWS\SYSTEM              994,496    X         X    X MSFFILE.DLL    \WINDOWS\SYSTEM              177,840    X    X    X    X MSMAPI.VBX     \WINDOWS\SYSTEM              37,712     X    X    X    X MSOUTLIN.VBX   \WINDOWS\SYSTEM              24,000     X         X    X MSTOOLBR.DLL   \WINDOWS\SYSTEM              9,232      X    X    X    X OLE2.DLL       \WINDOWS\SYSTEM              313,344    X    X    X    X OLE2CONV.DLL   \WINDOWS\SYSTEM              57,328     X    X    X    X OLE2DISP.DLL   \WINDOWS\SYSTEM              90,144     X    X    X    X OLE2NLS.DLL    \WINDOWS\SYSTEM              99,200     X    X    X    X OLE2PROX.DLL   \WINDOWS\SYSTEM              55,808     X    X    X    X PROJ2ACC.DLL   \WINDOWS\SYSTEM              157,440    X         X    X PROJHELP.DLL   \WINDOWS\SYSTEM              5,200      X         X    X SCP.DLL        \WINDOWS\SYSTEM              9,904      X    X    X    X SDM.DLL        \WINDOWS\SYSTEM              102,032    X    X    X    X SPLUS.DLL      \WINDOWS\SYSTEM              82,832     X    X    X    X STDOLE.TLB     \WINDOWS\SYSTEM              4,322      X    X    X    X STORAGE.DLL    \WINDOWS\SYSTEM              157,184    X    X    X    X THREED.VBX     \WINDOWS\SYSTEM              64,544     X    X    X    X TYPELIB.DLL    \WINDOWS\SYSTEM              142,592    X    X    X    X VBA.DLL        \WINDOWS\SYSTEM              820,064    X    X    X    X VBAEN.DLL      \WINDOWS\SYSTEM              9,360      X    X    X    X VBAEN.OLB      \WINDOWS\SYSTEM              31,060     X    X    X    X VBAMAPI.DLL    \WINDOWS\SYSTEM              6,320      X    X    X    X VBOA300.DLL    \WINDOWS\SYSTEM              13,824     X    X    X    X VBRUN300.DLL   \WINDOWS\SYSTEM              398,416    X    X    X    X VER.DLL        \WINDOWS\SYSTEM              9,696      X    X    X    X VSHARE.386     \WINDOWS\SYSTEM              14,933     X    X    X    X ANALYZER.EXE   \WINPROJ                     36,400     X         X    X BACKUP.MPT     \WINPROJ                     427,008    X    X         X BATCH.EXE      \WINPROJ                     28,407     X         X    X CBTLIB4.DLL    \WINPROJ                     18,800     X              X CONVERT.EXE    \WINPROJ                     51,500               X    X CONVERT.WRI    \WINPROJ                     6,528                X    X CUE.LES        \WINPROJ                     202,489    X              X DATA.EXE       \WINPROJ                     13,340     X              X DATABASE.WRI   \WINPROJ                     8,832      X         X    X DEWPROJ.EXE    \WINPROJ                     148,000    X    X         X GLOBAL.MPT     \WINPROJ                     427,008    X    X         X MPXFILE.WRI    \WINPROJ                     47,616     X              X MSP40OLE.DLL   \WINPROJ                     200,224    X    X         X PJREADME.HLP   \WINPROJ                     22,273     X              X PLAY.EXE       \WINPROJ                     108,912    X              X PLOTTERS.WRI   \WINPROJ                     13,184     X              X PROJEN40.OLB   \WINPROJ                     109,472    X    X         X PROJPSS.HLP    \WINPROJ                     34,097     X              X QP.LES         \WINPROJ                     250,140    X              X SAMPLES.WRI    \WINPROJ                     48,640     X         X    X SETUP.WRI      \WINPROJ                     21,504     X              X TIMETRAK.EXE   \WINPROJ                     47,418     X    X         X TMPLTWIZ.EXE   \WINPROJ                     97,867                    X TMPLTWIZ.WRI   \WINPROJ                     12,416                    X VBA_PJ.HLP     \WINPROJ                     1,442,882  X              X VBA_PJ.WRI     \WINPROJ                     2,048      X              X WINPROJ.DLG    \WINPROJ                     1,116,624  X    X         X WINPROJ.EXE    \WINPROJ                     3,217,920  X    X         X WINPROJ.HLP    \WINPROJ                     2,581,007  X              X WINPROJ4.REG   \WINPROJ                     3,573      X    X         X CUECARDS.DOC   \WINPROJ\CUECARDS            2,911                     X CUECARDS.DOT   \WINPROJ\CUECARDS            83,456                    X DOITCUE.HLP    \WINPROJ\CUECARDS            80,546                    X HCP.ERR        \WINPROJ\CUECARDS            7,463                     X HCP.EXE        \WINPROJ\CUECARDS            236,288                   X HCP.PIF        \WINPROJ\CUECARDS            545                       X STARTUP.DOC    \WINPROJ\CUECARDS            7,168                     X STARTUP.DOT    \WINPROJ\CUECARDS            17,920                    X BULLET.MRB     \WINPROJ\CUECARDS\BITMAPS    322                       X CHOICE.MRB     \WINPROJ\CUECARDS\BITMAPS    760                       X DOIT.MRB       \WINPROJ\CUECARDS\BITMAPS    388                       X GREYMENU.MRB   \WINPROJ\CUECARDS\BITMAPS    1,033                     X GREYNEXT.MRB   \WINPROJ\CUECARDS\BITMAPS    1,066                     X MENU.MRB       \WINPROJ\CUECARDS\BITMAPS    1,099                     X NEXT.MRB       \WINPROJ\CUECARDS\BITMAPS    1,270                     X ABOUTBOX.FRM   \WINPROJ\EXAMPLES\ANALYZER   7,627      X         X**  X ANALYZER.MAK   \WINPROJ\EXAMPLES\ANALYZER   238        X         X**  X GLOBAL.BAS     \WINPROJ\EXAMPLES\ANALYZER   12,413     X         X**  X GREETING.FRM   \WINPROJ\EXAMPLES\ANALYZER   7,588      X         X**  X MORE.FRM       \WINPROJ\EXAMPLES\ANALYZER   3,913      X         X**  X MOST.FRM       \WINPROJ\EXAMPLES\ANALYZER   5,790      X         X**  X PROJLIST.FRM   \WINPROJ\EXAMPLES\ANALYZER   3,283      X         X**  X STRINGS.BAS    \WINPROJ\EXAMPLES\ANALYZER   3,768      X         X**  X BATCH.MAK      \WINPROJ\EXAMPLES\BATCH      252        X         X**  X DEF.FRM        \WINPROJ\EXAMPLES\BATCH      16,301     X         X**  X MAIN.FRM       \WINPROJ\EXAMPLES\BATCH      23,979     X         X**  X PUBLIC.BAS     \WINPROJ\EXAMPLES\BATCH      17,586     X         X**  X INFLATE.XLM    \WINPROJ\EXAMPLES\INFLATE    160,768    X         X**  X GLOBAL.BAS     \WINPROJ\EXAMPLES\TIMETRAK   10,265     X         X**  X GRIDFUNC.BAS   \WINPROJ\EXAMPLES\TIMETRAK   16,345     X         X**  X MAIN.BAS       \WINPROJ\EXAMPLES\TIMETRAK   28,525     X         X**  X OPTIONS.FRM    \WINPROJ\EXAMPLES\TIMETRAK   8,702      X         X**  X OPTIONS.FRX    \WINPROJ\EXAMPLES\TIMETRAK   770        X         X**  X RESLIST.BAS    \WINPROJ\EXAMPLES\TIMETRAK   10,951     X         X**  X SCHEDULE.BAS   \WINPROJ\EXAMPLES\TIMETRAK   18,536     X         X**  X SPLASH.FRM     \WINPROJ\EXAMPLES\TIMETRAK   2,782      X         X**  X SPLASH.FRX     \WINPROJ\EXAMPLES\TIMETRAK   1,090      X         X**  X TASKINFO.FRM   \WINPROJ\EXAMPLES\TIMETRAK   17,118     X         X**  X TASKINFO.FRX   \WINPROJ\EXAMPLES\TIMETRAK   2,884      X         X**  X TIMETRAK.ICO   \WINPROJ\EXAMPLES\TIMETRAK   766        X         X**  X TIMETRAK.MAK   \WINPROJ\EXAMPLES\TIMETRAK   283        X         X**  X AUDIT.MPT      \WINPROJ\LIBRARY             34,304     X              X EVENTPLN.MPT   \WINPROJ\LIBRARY             41,984     X              X LANINST.HLP    \WINPROJ\LIBRARY             22,955     X              X LANINST.MPT    \WINPROJ\LIBRARY             37,888     X              X LANSUB.MPT     \WINPROJ\LIBRARY             36,864     X              X MKTPLAN.MPT    \WINPROJ\LIBRARY             41,472     X              X PERT.MPP       \WINPROJ\LIBRARY             76,800     X         X**  X ROLLOUT.MPT    \WINPROJ\LIBRARY             54,784     X              X ROLLUP.MPT     \WINPROJ\LIBRARY             23,040     X         X**  X SOFTDEV.HLP    \WINPROJ\LIBRARY             48,694     X              X SOFTDEV.MPT    \WINPROJ\LIBRARY             71,168     X              X TEMPLATE.WRI   \WINPROJ\LIBRARY             5,376      X              X _MSSETUP.EXE   \WINPROJ\SETUP               14,103                    X ACMSETUP.HLP   \WINPROJ\SETUP               19,125     X              X MSCPYDIS.DLL   \WINPROJ\SETUP               14,832     X              X MSSETUP.DLL    \WINPROJ\SETUP               191,360    X              X PJSETUP.TTF    \WINPROJ\SETUP               79,720     X              X PROJ_BB.DLL    \WINPROJ\SETUP               312,784    X              X SETUP.EXE      \WINPROJ\SETUP               255,776                   X SETUP.STF      \WINPROJ\SETUP               65,980     X    X    X    X WINPROJ4.INF   \WINPROJ\SETUP               14,320     X              X ACMSETUP.EXE   Used only during setup       9,125 ACMSETUP.STF  Used only during setup       55,578 ADMIN.INF     Used only during setup       14,320 COMPLINC.DLL  Used only during setup       102,400 DECOMP.EXE    Used only during setup       39,044 SETUP.INI     Used only during setup       149 SETUP.LST     Used only during setup       604 WGSETUP.EXE   Used only during setup       39,856 WGSETUP.INI   Used only during setup       481 WGSETUP.LST   Used only during setup       546 WGSETUP.STF   Used only during setup       2,321

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

"Q119730 Project: Files Installed with Each Type of Installation" Additional query words:

Keywords :

Issue type :

Technology : kbProjectSearch kbProject400