Shop

AdminStudio
InstallShield
Advanced Installer
other products

InstallShield

InstallShield 2016
Windows 10 Kacheln anpassen, Universal Windows Platform (UWP) und Nano Server, u.a.
Details hier

AdminStudio

AdminStudio 30% Aktionen

30% Rabatt beim Kauf von AdminStudio, nachdem Ihr Wartungsvertrag abgelaufen ist

30% Rabatt beim Wechsel auf eine höhere Edition oder Kauf eines Zusatzpakets

Details auf Anfrage

 

 

InstallShield und AdminStudio Schulungen

Offizielle Kurse mit Zertifikat

weitere Infos


 

Bugs Bulletin

[ MSI Engine | MSMs | InstallShield 12 and newer | InstallShield 11.5 | DevStudio 9.0 | IS Dev 8.0 | IS Dev 7.0 | IPWI 2.0 | ISWI 1.x | IS Pro 7.x | IS Pro 6.x | IS Pro 5.x ]

[ IS 6.3 | IPSE 6.2 | IS 6.1 | IS 6.0 ]

InstallShield Professional 6.1

Last version: 6.12 + Engine Hotfix of January 4, 2001.
Released: August 25, 2000
Download: Maintenance pack 2 for InstallShield Professional 6.1 can be downloaded from http://support.installshield.com/download/is612.asp.
Release Notes: A list of fixed bugs and open issues can be found at http://support.installshield.com/download/is6relnotes.asp
Engine Hotfix: The latest version of iKernel.exe is available from Knowledge Base article Q105097.

Known Problems in IS Pro 6.12

Problems that also apply to newer releases of InstallShield Professional are not listed here.

BDE Files Inadvertently Removed

Description:
If a component in your projet is set to require the component that includes the BDE 5.1 Object, you may loose BDE files in maintenance mode. This happens if you de-select the component that requires the BDE component, but do not touch the BDE component itself (i.e. leave it selected). In this situation, most of the BDE files get deleted.
Example: Component "BDE" includes the BDE object. Component "Test" requires component BDE. On initial install all components are selected. In Modify mode de-select the "Test" component. Although the BDE component is still selected, BDE files will get deleted.
The cause of this problem is obscure, and it has been reported that it sometimes occurs even if the de-selected component is unrelated to BDE, i.e. it is not requiring the BDE object.
Remarks: The Component_Uninstalling event for the BDE component is not fired in this situation, but the Uninstalling_File and OnRemovingSharedFile event handlers for the BDE files are called. Not all BDE files are removed, some SQL files are left behind. They get removed if you run Uninstall mode.
Workarounds:
None.
Status:
This problem is reproducible in IS 6.10.
FIXED in the latest version of the BDE 5.1 object which is included with IPSE 6.22 and available as separate download.
Created: 2000-02-15    Last update: 2001-05-05   InstallShield Tracking Number: 1-3W4BA

Duplicate BDE Alias Names Mangled

Description:
Using the BDE 5.1 Object. When an aliasname is added that already exists, the duplicate alias is named Alias1. That's ok. Subsequent adds produce Alias12, Alias123, Alias1234, etc. instead of Alias2, Alias3, Alias4, etc.
Workarounds:
None.
Status:
InstallShield confirmed that this is a bug in IS 6.10.
FIXED in the latest version of the BDE 5.1 object which is included with IPSE 6.22 and available as separate download.
Created: 2000-02-15    Last update: 2001-05-05   InstallShield Tracking Number: 1-3W4BE

Configuration Window On Each Restart After Installing MDAC 2.5 Object

Description:
After running a setup that includes the MDAC 2.5 object, each time you restart Windows a message about updating the system configuration is displayed for a moment.
Cause:
The MDAC 2.5 object launches mdac_type.exe version 2.5 from Microsoft. This package leaves behind and "mdac_runonce" entry in the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run registry key (note that it's using the Run key, not the RunOnce key). This causes the runonce.exe program to run each time you start Windows.
Workarounds:
MDAC packages Version 2.5 SP1 and 2.6 do not have this problem. You can replace the mdac_typ.exe in InstallShield's object directory with one of the new versions. Note that version checking in the object is hard wired, so your patched object will not update a system that already has MDAC 2.5 installed if you set CheckMDACVersion = TRUE.
Another option is to remove the obsolete mdac_runonce entry from registry after reboot. This is documented in Mocrosoft Knowledge base article Q268062.
Status:
Microsoft has confirmed that this is a problem in the MDAC 2.5 installer. It is fixed in MDAC 2.5 SP 1 and later.
FIXED in the latest version of the MDAC 2.5 Object which installs MSDAC 2.5 SP1. This object is included with IPSE 6.22 and available as separate download.
Created: 2000-10-04    Last update: 2001-05-05   InstallShield Tracking Number: 1-1O9TX

NT Services Sometimes Not Removed Upon Uninstall

Description:
If you use the NT Service Object to install an NT service, the service may still be listed in SCM after uninstall. This happens if the service is not running at the time of uninstall.
Workarounds:
Make sure your service is started before uninstall.
Status:
InstallShield confirmed that this is a bug in IS 6.03 and 6.10.
FIXED in 6.22.
Created: 2000-01-25    Last update: 2001-02-22   InstallShield Tracking Number: 1-3W4BY

Logging Uses a Lot of Memory

Description:
When installing large setups IS 6 uses a lot of memory for logging. This can cause setup to stall on systems with low physical memory (e.g. 32 MB).
Workarounds:
Use IS 5.5 instead (included on the IS Pro 2000 CD).
Status:
InstallShield has confirmed that this is a problem in IS 6.10, 6.11 and 6.20.
FIXED in 6.21
Created: 2000-06-11    Last update: 2001-01-16   InstallShield Tracking Number: 1-3O4TL

IS6 Evaluation Version Does Not Install on Windows 2000

Description:
If you try to install the Evaluation Version of InstallShield 6 on a system running Windows 2000 you get an error message and the installation aborts. However the full version of IS6 can be installed on Windows 2000.
Cause:
The Evaluation Version uses time lock software that is not compatible with Windows 2000.
Workarounds:
Install on Windows 9x or NT 4, or contact sales@installshield.com for an arrangement.
Status:
InstallShield confirmed that this is a problem with the time locking part of the evaluation version in IS 6.0 and 6.10.
FIXED in IS 6.22.
Created: 2000-01-12    Last update: 2001-01-13   InstallShield Tracking Number: 1-3ZIDU

Temporary Directory Not Cleaned Up If Setup Cancelled in Maintenance Mode

Description:
If you cancel setup from maintenance mode the temp directory doesn't get deleted. This bug doesn't affect canceling from first run of setup.
Workarounds:
None.
Status:
InstallShield confirmed that this is a bug in IS 6.03 and 6.10.
FIXED in IS 6.22.
Created: 1999-12-10    Last update: 2001-01-13   InstallShield Tracking Number: 1-3W4C2

Media Build Wizard Sometimes Ignores Disk Space Reservation

Description:
If you select 1.44 MB floppy as media type and reserve a large amount (> 750 KB) of space on disk 1, media builder does not reserve any space and does not issue any warning. The correct behaviour would be to display "Error 129: Media too small".
Workarounds:
InstallShield requires about 1 MB on disk 1, and automatically reserves some extra space (in case of bad clusters on the floppy).Therefore you cannot reserve more than about 150 KB on disk 1. You can reserve more space on the other disks.
Status:
This problem is reproducible in IS 6.03 and 6.10.
FIXED in IS 6.22.
Created: 2000-02-07   Last update: 2001-01-13   InstallShield Tracking Number: 1-3W4BQ

EzBatchReplace Sometimes Fails

Description:
On some systems EzBatchReplace does not perform its duty (i.e. the batch file is unchanged) or adds the line instead of replacing an existing line. In such situations it may return 0 or -1. Especially lines that start with "SET" appear to be affected by the problem.
Workarounds:
Use FileGrep and the gereral string processing functions to modify the line in the batch file.
Status:
InstallShield confirmed that this is a problem in IS 6.10. It could not be reproduced in 6.22, so it's probably fixed.
Created: 2000-03-22    Last update: 2001-01-13   InstallShield Tracking Number: 1-3VV9E

DLG_CLOSE Not Recognized as Keyword

Description:
When used in conjunction with the switch() function in a custom dialog, DLG_CLOSE is not recognized. During setup runtime, the close button on the custom dialog will not work.
Workarounds:
In your switch statement use
    case 2:
instead of or in addition to
    case DLG_CLOSE:
Status:
FIXED in IS 6.22.
Created: 2000-10-04    Last update: 2001-01-13   InstallShield Tracking Number:1-3NNVS

GPF When Trying to Rename a Component

Description:
When you try to rename a component, the IDE may crash with a General Protection Fault.
Specifically this happens if you created your project with the Visual Basic Project Wizard and then try to rename the component "Program Files" to some other name.
Cause:
The Program Files component includes the VB Runtime Object, and is set up to require this object. There is a known problem if objects are selected as required, so this may be a consequential damage.
Workarounds:
Temporarily move the VB Runtime Object to another component (e.g. drag it with the mouse and drop it on the Windows Files component), rename the Program Files component as desired, and move the VB Runtime Object back to the renamed Program Files component.
Status:
This problem is reproducible with IS 6.03. It is still there in IS 6.10.
FIXED in 6.21.
Created: 1999-12-15    Last update: 2001-01-03

Setup Fails with DosExecPgm Error Message

Description:
On some machines setup fails during the initialization phase and displays the following error message: "Setup Failed to run installation. The argument string passed to DosExecPgm is not correct.".
It is still obscure which conditions cause this problem. There is a discussion group for people affected by this error (under Special Topics -> DosExecPgm Error). If you are affected by this error, please collect as much information as possible, such as Windows version, language and service pack, network settings, regional settings, virus scanners, Internet Explorer, and other installed software packages, and post it to the group. Hopefully some scheme can be identified that helps to find the cause and fix the problem.
Workarounds:
The following steps have helped in some cases (all steps are required):
1. Clean the TEMP directory. Remove all folders that have been left behind by previous setups.
2. Reboot.
3. Run ScanDisk. Even if it doesn't report any errors on the drive, it seems to fix some disk problems.
Other things you can try:
- Delete the folder <COMMONFILES>\InstallShield\engine and try again.
- Reinstall IE5
Status:
InstallShield confirmed that this is a problem in IS 6.03 and 6.10.
In later versions the symptoms have changed. See article about error 0x80040707.
Created: 2000-03-08    Last update: 2000-05-20   InstallShield Tracking Number:1-3ZIE2

Media Builder Doesn't Use All Space On Floppy Media

Description:
When you create a setup project with IS6 and try to build 1.44 MB floppy disk media, you may get error 129 "Media too small". If you build the same project for CD-ROM type media, media build succeeds and the resulting Disk1 directory contains about 1.2 MB. This might be a precaution in case of corrupt sectors on the diskette, or simply a bug. Here are some typical situations where you will experience this problem:
Workarounds:
Use the Media Wizard to create a Custom Media install of, say 1500 KB.  This means your Disk1 will still have enough room, and remain below the real-world limit of 1440 KB.   Then, on the "Build Type" page of the Media Wizard, hit the Advanced Button.  Under "Disk Information" add reserved space to drop the actual build size back down to what will fit on a 1440 KB disk (i.e. 100 KB or so).  If you have a lot of diskettes, you can directly modify the default.mda to add them directly rather than using the UI, but note that the numbering of the DISKINFO structures is done by alphabetic sorting rather than numeric sorting.
Status:
This problem has been reported in the newsgroups for IS 6.10.
FIXED in IS 6.20.
Created: 2000-02-15    Last update: 2000-12-19   InstallShield Tracking Number: 1-3O4SV

SelectDirEx Returns Only Last Part of Selected Path

Description:
SelectDirEx returns only the last directory of the path that the users selected. E.g. if the user selected "C:\Windows\System" the function will only return "System".
Workarounds:
Add the BIF_EDITBOX flag to the fifth parameter (you can combine multiple flag using the logical or operator). This will add a path edit box to the dialog where the user can enter a path. Or use SelectDir instead.
Status:
InstallShield confirmed that this is a bug in IS 6.10.
FIXED in IS 6.22 for file system paths. Not fixed for printers.
Created: 2000-02-07    Last update: 2000-11-16

Truncated Texts in German Dialogs

Description:
On some German language message boxes and dialogs that are displayed during uninstall, some words are mis-typed:
"Dateiöschung" instead of "Dateilöschung"
"Deinstallatio" instead of "Deinstallation"
"ageschlossen" instead of "abgeschlossen"
Workarounds:
Download a patched version of _isres.dll with corrected texts and place it in your <PROGRAMFILES>\InstallShield\InstallShield Professional 6.1\Redistributable\Compressed Files\0007-German\Intel 32 directory.
ZIP IsresGer61x.zip   Patched by Thomas Wendt
File size: 34.862 bytes   Last update: 2000-10-18
Note: A similar patch is available for IS 6.03.
Status:
InstallShield confirmed that this is a problem in IS 6.10.
FIXED in IS 6.20.
Created: 2000-04-15    Last update: 2000-10-18

Problem with AskYesNo dialog in OnRebooted Event Handler

Description:
If you want to display an AskYesNo dialog in the OnRebooted event handler, a message box with the text "D:\is6\code\XT\RunTime\ISFunc\AskYesNo.rul" will pop up before the AskYesNo dialog.
Workarounds:
Call the MessageBox WinAPI directly.
Status:
This problem is reproducible in IS 6.10.
FIXED in IS 6.21 but not in 6.12.
Created: 2000-05-26    Last update: 2000-08-28     InstallShield issue number 1-181BB

Registry Editor in IDE Capitalizes Strings

Description:
Using the registry editor in IDE to create registry entries, the string gets converted to all caps. You cannot enter lower characters in registry entries.
Workarounds:
Use the registry script functions instead of the registry editor in IDE.
Status:
InstallShield confirmed that this is a bug in IS6.01 and 6.10.
FIXED in 6.20
Created: 1999-10-12    Last update: 2000-05-22
 

 

 

English News Discussions Windows Installer Related Tools More Help InstallScript About InstallSite Shop Site Search
deutsch Neuigkeiten Diskussionsgruppen Windows Installer MSI FAQ Artikel     Shop Suche

Copyright © by InstallSite Stefan Krueger. All rights reserved. Legal information.
GERMAN Impressum,Datenschutzerklärung, Haftungsausschluss
By using this site you agree to the license agreement. Webmaster contact