BUG: Setup CreateProgmanItem Does Not Overwrite Item

Last reviewed: January 5, 1995
Article ID: Q87493
The information in this article applies to:
  • Microsoft Windows Software Development Kit (SDK) for Windows version 3.1

SYMPTOMS

In the Microsoft Setup Toolkit for Windows, when the setup script calls the CreateProgmanItem() subroutine to replace an existing item in a Microsoft Windows Program Manager group with cmo% set to cmoOverwrite and with szOther$ set to a nonempty string, the setup driver does not replace the existing item. Instead, it creates a new item.

CAUSE

_MSTEST, the setup driver spawned by SETUP.EXE, incorrectly forms the name of the item to overwrite if szOther$ is not an empty string. This prevents _MSTEST from finding an item in the group with the specified name, and it creates a new item.

RESOLUTION

Microsoft has confirmed this to be a bug in version 3.1 of the Setup Toolkit for Windows. If the setup script must specify the icon file, icon resource index, x and y icon position, or working directory, and if it is unacceptable to potentially have two items of the same name in a group, the groups must be manipulated through a dynamic data exchange (DDE) conversation with Program Manager. Add a function that initiates and manages a DDE conversation with Program Manager to MCUISTF.DLL and call the function from the setup script.

MORE INFORMATION

Windows 3.0 does not support the cmoOverwrite command option flag for the CreateProgmanItem() subroutine.


Additional reference words: buglist3.10 3.10 MSSetup tool kit
KBCategory: kbtool kbbuglist
KBSubcategory: TlsMss


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