PRB: Setup Wizard Replaces User-Created SETUP.EXE File

Last reviewed: June 27, 1995
Article ID: Q126441
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6a

SYMPTOMS

If a setup program is created for an application that will be distributed using the Setup Wizard and the user-created setup program has the name (SETUP.EXE), the Setup Wizard will replace the user-created program with its own file (which is also named SETUP.EXE).

CAUSE

The Setup Wizard does not check to see if a user-created file by the name of SETUP.EXE exists in the distribution directory where the files that comprise the user-created program reside.

WORKAROUND

Do not name any executables SETUP.EXE.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a new project with one program file.

  2. In the program file, execute the command:

    Wait Window "Hello"

  3. Choose Build, and select Executable -- assuming the distribution kit is installed. Name the executable SETUP.

  4. After the executable has been built, create a distribution directory, and copy the file SETUP.EXE and FOXW2600.ESL into the directory.

  5. Run the Setup Wizard, and respond to the on-screen prompts. After the Wizard has created the distribution disk directories, run SETUP.EXE in the DISK1 directory. What will be executed is the Microsoft Installation program, not your original executable.


Additional reference words: FoxWin 2.60a SETUP WIZARD EXECUTABLE
KBCategory: kbtool kbprb
KBSubcategory: FxtoolDk


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