VB3 How to Change the Setup Application Name in SETUP1.EXE

Last reviewed: January 9, 1997
Article ID: Q101743
The information in this article applies to:

- Standard and Professional Editions of Microsoft Visual Basic

  programming system for Windows, version 3.0

SUMMARY

The Setup Wizard in Visual Basic version 3.0 creates SETUP1.EXE that when executed displays a blue background with white letters that say: "<EXE NAME> Setup," where <EXE NAME> is the name of your application. This article explains how to change that message to something other than the default.

MORE INFORMATION

To change the display of <EXE NAME>, follow these steps:

  1. Run the Setup Wizard as you normally would to create installation disks.

  2. Start Visual Basic and load the project SETUP1A.MAK (The Setup Wizard created this project in the C:\VB\SETUPKIT\SETUP1 directory).

  3. In the General Declarations section of SETUP1A.FRM, change the value of constant APPNAME:

    Const APPNAME = "<Whatever you want to put here>"

  4. From the File menu, choose Make EXE to create the file SETUP1.EXE.

  5. Exit to MS-DOS.

  6. Copy and compress the file SETUP1.EXE to your distribution disk.

    C:\VB\SETUPKIT\KITFILES\COMPRESS -r SETUP1.EXE A:\

    This will copy over the old SETUP1.EX_ that was created on the distribution disk by the Setup Wizard.


KBCategory: kbtool kbprg
KBSubcategory: TlsSetWiz
Additional reference words: 3.00


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: January 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.