Shop

InstallShield
Advanced Installer
AdminStudio
more / weitere

InstallShield

InstallShield 2018
Neue Version mit Verbesserungen für IIS, XML, MSBuild, PowerShell, Suite Projekte, Prerequisites u.a.
Details hier

InstallShield und AdminStudio Schulungen

weitere Infos

Bugs Bulletin: InstallShield Developer 7.0

[ 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 ]

[ ISD 7.04 | ISD 7.03 | ISD 7.02 | ISD 7.01 | ISD 7.00 ]

The problems listed on this page have been fixed in the latest maintenance release and are listed for reference.

InstallShield Developer 7.03

Version: 7.03
Release Date: April 29, 2002
Download: Select Check for Updates from the Tools menu (Download size 118 MB). Users of ISD 7.00 need to update to 7.02 before they can obtain ISD 7.03. This update is for the English edition only. German and Japanese version are expected to be released in June.
Release Notes: A list of enhancements, fixes and open issues is available at http://www.installshield.com/downloads/isd/isd_readme703.asp
Installation Notes: If you have previously installed the beta version of ISD 7.03 you must uninstall it and clean all InstallShield directories before installing the release version. ISD 7.03 is a full install package that can be installed on a fresh machine, but in that case your language packs won't get updated automatically. If you are using language packs and don't want to install 7.03 on to of 7.02 you must download the updates language packs from the InstallShield download center.
After installing ISD 7.03 use the Check for Updates function again to download additional merge modules that are not included in the package.

Known Problems in ISD 7.03

Norton LiveUpdate Fails on Development Machine

Description:
After installing service pack 4 for InstallShield Developer 7 on a machine with Norton LiveUpdate, you may receive the error message "NO PRODUCTS TO UPDATE 'There are no products on this machine that can be updated by LiveUpdate.'" Norton LiveUpdate is installed with various tools from Symantec Corporation, such as Norton AntiVirus.
Workarounds:
There is an article in the Symantec knowledge base avout this error message (not specific to InstallShield). The method suggested in section "Import a registry key" has been reported to fix the problem.
Status:
This problem has been reported by several users of Developer and AdminStudio.
FIXED in ISD 7.04
Created: 2002-08-07   Last update: 2002-08-09   InstallShield tracking number:

InstallScript Debugger Doesn't Start in German 7.03

Description:
When you try to run your setup in the InstallScript debugger, the debugger doesn't launch. Instead your setup executes as if started with the Run command. This only occurs in the German edition of Developer 7.03, the English edition is not affected by this problem.
Cause:
An incompatible version of isddbg.exe is installed with the German edition. The file is located in directory [ProgramFilesFolder]\InstallShield\Developer\System and has a version of 6.30.100.1255.
Workarounds:
Download isdbg.exe from knowledge base article Q106653. The string version of this file (as displayed in Windows 9x and NT) is 6.23.100.1200, the internal numerical version (as displayed by Windows 2000) is 7.1.0.165. After copying the file to the aforementioned directory run isdbg.exe /REGSERVER
Status:
InstallShield has confirmed that this is a problem in ISD 7.03 German. It will be fixed in 7.04 German.
Created: 2002-08-02   InstallShield tracking number: 1-A9GQE

Minor Update doesn't Update Version Information in Add/Remove Programs

Description:
Installing a minor update of a Standard project as full setup doesn't update   DisplayVersion, VersionMajor, and VersionMinor data for the following registry key if a previous version of the product was on machine prior to running minor update:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL\INSTALLSHIELD_{Product Code}
On Windows 2000 and XP this results in incorrect Product Version display under Support Information on Add/Remove Programs dialog.
BasicMSI projects are not affected by this problem.
Workarounds:
Distrubute your minor update as patch.
Status:
InstallShield has confirmed that this is a problem in ISD 7.03.
FIXED in ISD 7.04
Created: 2002-07-09   InstallShield tracking number: 1-8WE9D

Crash with VMWare and ISD 7.03

Description:
When you launch InstallShield Developer and have a VMWare (3.0 or 3.1) virtual machine open your computer may crash or reset itself.
Workarounds:
Use newer version of ISD.
Status:
InstallShield has confirmed that this was a problem in the first release of ISD 7.03. The ISD 7.03 update on the InstallShield web site has been fixed around May 14, 2002. Users who downloaded the update after this date should not experience this problem.
FIXED in ISD 7.04.
Created: 2002-06-13   Last update: 2002-07-09   InstallShield tracking number:

"Error reading setup.ini" after Upgrade to ISD 7.03

Description:
Testing your setup may fail with the above error message. Looking into setup.ini with a text editor you notice that the MsiVersion setting is empty.
Workarounds:
Perform a clean install of ISD 7.03 instead of updating on top of 7.02. Running a repair install of ISD also seems to fix this problem.
Status:
InstallShield support was unable to reproduce this problem.
Created: 2002-06-13   InstallShield tracking number: n/a

IsCmdBld.exe Crashes with UNC Path

Description:
When you perform a command line build ISCmdBld.exe crashes with Unknown exception if you use UNC paths in the parameters.
Workarounds:
A HotFix with a fiexed ISCmdBld.exe is available in InstallShield knowledge base article Q106423
Status:
InstallShield has confirmed that this is a bug in ISD 7.03.
FIXED in ISD 7.04.
Created: 2002-06-13   Last update: 2002-07-10   InstallShield tracking number: 1-96N04

Log File Corruption can Cause Unintentional Removal of Components

Description:
Corruption of log files can cause unintentional removal of installed components during maintenance setup. In a sample project, setup running in maintenance mode deleted all previously created shortcuts. InstallShield development team confirmed this to be a bug in the log file writing logic, which is supposed to be fixed in ISD 7.03.
Workarounds:
At the top of setup.rul add the following function prototype:
external prototype NUMBER __ISRTRestoreMainLog();

At the beginning of OnFirstUIAfter and OnMaintUIAfter call the function:
function OnFirstUIAfter()
begin
    __ISRTRestoreMainLog();
    ...
end;

function OnMaintUIAfter()
begin
    __ISRTRestoreMainLog();
    ...
end;
Status:
InstallShield has confirmed that this is a problem in ISD 7.02 and 7.03.
FIXED in ISD 7.04
Created: 2002-04-15   Last update: 2002-07-10   InstallShield tracking number: 1-8MVPI

Floppy Drive Conflict with TPkd.sys on Windows XP

Description:
After installing ISD on a Windows XP machine your flopy disk drive may report a conflict with TPkd.sys.
Cause:
The online activation enabled downloads of InstallShield Developer and InstallShield Express install a TPkd.sys driver provided by Pace Anti-Piracy for online activation. On some Windows XP systems whose motherboard does not support IRQ sharing, this driver may conflict with the floppy drive on IRQ 6.
Workarounds:
While logged onto the affected system with local administrator privileges, use the registry editor to set the registry value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TPkd\Start to 3, and restart the system. This will change the startup mode of the TPkd.sys driver to on Demand, rather than loading at Boot. This will allow access to the floppy drive, and will allow online activation to function normally.
Status:
InstallShield has confirmed that this is a problem in ISD 7.x (including 7.03) and InstallShield Express 3.x. It is documented in knowledge base article Q106005.
FIXED in ISD 7.04
Created: 2002-03-16   Last update: 2002-07-10   InstallShield tracking number: 1-8N7PM

Undesired Default Value with Empty String Created in Registry

Description:
In a Standard project if you create a registry key without any values attached, a default value with empty string will be created by ISD.
Workarounds:
Change the key type from "automatic" to "create during installation" or something similar. This will enter a value with "+" instead of an empty string as default value in the registry table, which instructs Windows Installer to create this key without a default value during installation.
Status:
InstallShield has confirmed that this is a problem in ISD 7.02 and 7.03. It is also reproducible in 7.01.
FIXED in ISD 7.04.
Created: 2002-01-04    Last update: 2002-07-10   InstallShield tracking number: 1-784LG

Close Button on Custom Dialogs Not Working

Description:
Clicking the close button [x] in the upper right corner of custom dialogs or pressing the ESC key may have no effect. Clicking the Cancel button works. This only applies to Standard projects.
Cause:
In the Standard Setup dialogs, there is an extra button for the dialog. You cannot see the button in the dialogs editor in ISD7 because the position of the button is not actually on the dialog itself, it is "outside", below the dialog. In Visual Studio you could see it, but not in ISD7. However, the combo box that lists all the controls for a dialog will have it. It's a pushbutton ControlId_2. The Sd dialogs need this button so they can exit with either the 'X' in the top right corner or by pressing the Esc key.
Workarounds:
Create this same button for a custom dialog with the same attributes as the other dialogs. The attributes are:
    (Name) ControlId_2
    Cancel True
    Control Identifier 2
    Control Style Text
    Default False
    Enabled True
    File Name <leave empty>
    Height <doesn't matter, make it small>
    Icon Size <leave empty>
    Left <depends where you create it>
    Other Windows Styles <leave empty>
    Right-to-Left False
    Sunken False
    Tab Index <make it the last one or make empty>
    Tab Stop False
    Text C <or anything you want>
    Top <doesn't matter>
    Visible False
    Width <doesn't matter, make it small>
Once you have this done in the dialog editor, your script will have to handle two (2) in its switch statement.
case 2:
    Do(EXIT);
Or internally, here's what just about all the SdDialogs do:
default:
    // check standard handling
    if (SdIsStdButton( nId ) && SdDoStdButton( nId )) then
        bDone = TRUE;
    endif;
These are undocumented functions which really don't do too much. SdDoStdButton actually calls Do(EXIT) it 2 is passed in. You can use these functions in your script.
Status:
InstallShield confirmed that this is a problem in ISD 7.00 - 7.03
FIXED in ISD 7.04.
Created: 2001-10-15   Last update: 2002-07-10   InstallShield tracking number: 1-7CWFM

Splash Bitmap not Migrated

Description:
Splash Screen bitmaps in the Setup Files view do not migrate.
Workarounds:
Add the bitmaps manually to the Setup Files | Splash Screen view.
Status:
InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 7.03.
FIXED in ISD 7.04
Created: 2001-08-18   Last update: 2002-07-10   InstallShield tracking number: 1-6A41T

Shortcuts not Migrated Properly from IS Pro

Description:
<TARGETDIR> referenced in parameters of shortcut in an InstallShield Professional project does not get migrated to [INSTALLDIR].
Workarounds:
Manually edit the shortcut properties after migration.
Status:
InstallShield has listed this problem as open issue in the release notes for ISD 7.00. Not fixed in ISD 7.01 - 7.03.
FIXED in ISD 7.04
Created: 2001-08-18   Last update: 2002-07-10   InstallShield tracking number: 1-6A5FT
 

 

 

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.
Impressum/Imprint Datenschutzerklärung/Privacy Policy
By using this site you agree to the license agreement. Webmaster contact