Description of INSTALL /N (Workstation Installation)

 Last reviewed: April 18, 1995
Article ID: Q109651
The information in this article applies to:
  • Microsoft FoxPro for MS-DOS, versions 2.5, 2.5a, and 2.5b

SUMMARY

The Workstation Installation (INSTALL /N) option is run from a directory containing an Administrative Installation. The Workstation Installation consists of two parts -- Basic Installation and Configuration.

The Basic portion copies FOX.EXE to the Workstation directory and adds the Workstation and Administrative directories to the PATH statement in AUTOEXEC.BAT.

The Configuration portion runs the FoxPro application, ADDUSER.APP, which creates configuration and resource files in the Workstation directory, and then adds a SET FOXPROCFG statement to the AUTOEXEC.BAT.

MORE INFORMATION

NOTE: Before performing a Workstation Installation, an Administrative Installation must be available. The Administrative Installation (INSTALL /A) copies and expands all files to the Administrative directory. These files are used by FoxPro when it is running on a workstation.

Additional information on network installation is contained in INSTALL.TXT, found on the Setup disk (Disk 1) and in the main FoxPro directory (usually FOXPRO25).

Basic Installation

The Basic Installation option does the following:

  1. Asks you for the installation directory. You can use the default directory provided, or specify a different one, which is created if it doesn't already exist.

    The default directory is FOXPRO25 on the current drive. For example, if the current drive is N, the default directory is N:\FOXPRO25.

    NOTE: You can also specify the installation directory at the command line by including the directory name after typing INSTALL /N. For example, to make the installation directory C:\FOX, type the following: 

          INSTALL /N C:\FOX

  2. Prompts you to add the directories containing the Workstation and Administrative Installations of FoxPro to the AUTOEXEC.BAT file's PATH statement if they are not already in the PATH statement.

  3. Makes a backup of the AUTOEXEC.BAT file if you instructed the installation program to make changes to the PATH statement in the previous step. A backup of the AUTOEXEC.BAT file is saved to AUTOEXEC.000. If, AUTOEXEC.000 already exists, the backup is saved to AUTOEXEC.001 (and so on).

  4. Copies FOX.EXE to the installation directory.

  5. Asks if you want to configure FoxPro for your particular network environment. If you do not want to do this, press the ESC key. To proceed, press any other key.

Configuration

If you chose to configure FoxPro for your particular network environment (step 5 above), the installation program calls INSTALL2.BAT to start the FoxPro ADDUSER.APP application. INSTALL2.BAT is created by INSTALL /N, and contains the name of the current installation directory. In this example, INSTALL2.BAT contains the following line: 

   FOX -ek adduser.app N:\FOXPRO25\
The ADDUSER.APP application asks for information used to create the configuration file (CONFIG.FP by default), which is saved in the Workstation directory.

Then ADDUSER.APP adds a SET FOXPROCFG=<configuration pathname> statement to the AUTOEXEC.BAT file.

For more information about ADDUSER.APP, query on the following word here in the Microsoft Knowledge Base: 

   ADDUSER.APP

Additional reference words: FoxDos 2.50 2.50a 2.50b
KBCategory: kbnetwork kbsetup kbprg
KBSubcategory:

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: April 18, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.