[ 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 ]
[ ISDev 8.02
| ISDev 8.01
| ISDev 8.00 ]
The problems listed on this page have been fixed in the latest maintenance release
and are listed for reference.
InstallShield Developer 8.01
Version: 8.01
Release Date: March 25, 2003 (English). German version not yet
available.
Release Notes:
Developer 8.0 SP1 Enhancements and Fixes
Closed bugs are marked
FIXED in ISDev 8.01 within the ISDev
8.00 list
[ Known Bugs | Other Known Issues ]
Password Protection Inadvertently Turned On
- Description:
- When you build a release it may be password protected, although you didn't
select this option. This seems to happen randomly, on InstallScript MSI
projects only.
- Workaround:
- None.
- Status:
- InstallShield has confirmed that this is a problem that has been
introduced with ISDev 8.01.
FIXED in ISDev 8.02
- Created: 2003-04-03 InstallShield tracking
number: 1-CYZF5
Password Protected Media Cannot be Installed
- Description:
- When running a password protected setup.exe, the OK button on the password
dialog is always disabled, even if you entered the correct password. This
problem affects both Basic MSI and InstallScript MSI projects.
- Workaround:
- Don't password protect your media. If you need a password protected setup,
build an uncompressed release and use PackageForTheWeb to compress the setup
files into a password protected exe.
- Status:
- InstallShield has confirmed that this is a problem that has been
introduced with ISDev 8.01.
FIXED in ISDev 8.02
- Created: 2003-04-03 InstallShield tracking
number: 1-D5UHM
Cannot Open MSM Files
- Description:
- If you try to open a merge module MSM file in Developer you'll receive an
error message "InstallShield Developer cannot open <path to msm file>. Please
contact InstallShield technical support for more information." Note that this
only applies if you try to open a MSM file for editing. You can add merge
modules to your project without problems.
- Workaround:
- In the InstallShield IDE select Open from the File menu. In the Open
dialog box change the "Open as" setting from "Auto" to "Wizard". On the first
wizard page select "Convert MSI/MSM to an InstallShield Project".
If you need to edit the merge module in direct mode, use Orca instead of
ISDev.
- Status:
- InstallShield has confirmed that this is a problem that has been
introduced with ISDev 8.01.
FIXED in ISDev 8.02
- Created: 2003-04-03 InstallShield tracking
number: 1-D5U6H
Copyright © 1997-2012 by InstallSite Stefan
Krueger. All rights reserved. Legal
information.
Impressum,Datenschutzerklärung,
Haftungsausschluss
By using this site you agree to the license
agreement. Webmaster contact
