Flexera Software Community  

Go Back   Flexera Software Community > Products > Legacy Installer Products > InstallShield > InstallShield Windows 11.5
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 03-28-2006, 04:44 AM
madtech madtech is offline
User (5+ Posts)
 
Join Date: May 2003
Location: Leighton Buzzard, UK
Posts: 11
Unhappy Windows Vista and MDAC 2.7 Merge Module

When is the problem with the MDAC 2.7 Merge Module going to be fixed where it blocks installation on any operating system post-Windows Server 2003?

I see the current merge module still includes the following check

Code:
ElseIf ((vVerNT = "501") Or (vVerNT = "502")) Then
' If it is XP do not install
rather than just
Code:
ElseIf (vVerNT >= "501") Then
' If it is XP or higher, do not install
With just over six months until Vista RTM, I would have expected this to have been resolved by now so that we can start building sets that work across all versions of Windows.

Seven months ago Chandima said:
Quote:
Ah! We shall have that corrected shortly. The updated module will ship with the latest release but we will make it available on the merge module gallery as well. Thanks for the heads up!
That has obviously not happened, so when is this going to be resolved?

Last edited by madtech : 03-29-2006 at 08:56 AM.
Reply With Quote
  #2  
Old 04-18-2006, 09:59 AM
madtech madtech is offline
User (5+ Posts)
 
Join Date: May 2003
Location: Leighton Buzzard, UK
Posts: 11
Unhappy

As none of the Developers have replied to this thread, should I presume there are no plans to fix this bug any more?

If so, how do we work around the problem, short of distributing a different installation set for Windows Vista users?
Reply With Quote
  #3  
Old 04-24-2006, 01:57 AM
Stefan Krueger's Avatar
Stefan Krueger Stefan Krueger is offline
Uber User (1000+ Posts)
 
Join Date: Oct 2001
Location: Germany
Posts: 1,478
InstallShield accepted this as a feature request (IOC-000047479), but I don't know when or how they're going to change the module. Until then you need to modify the module yourself, or use a custom prerequisite instead.
__________________
Stefan Krüger Microsoft Windows Installer MVP
InstallSite.org Stefan's Blog



Please post your questions in the forum
Reply With Quote
  #4  
Old 04-24-2006, 06:04 AM
madtech madtech is offline
User (5+ Posts)
 
Join Date: May 2003
Location: Leighton Buzzard, UK
Posts: 11
Smile

Thanks for your help Stefan.

I hadn't realised it was possible to edit the MSM files using InstallShield. Took a while to figure out how to get into the VBS file in the Binary table, but now that is all edited, I would hope that solves the problem. Will test when I get a chance over the next few days.
Reply With Quote
  #5  
Old 04-24-2006, 03:24 PM
hidenori's Avatar
hidenori hidenori is offline
InstallShield Software Engineer
 
Join Date: Oct 2001
Location: Schaumburg, IL
Posts: 1,712
The work order #IOC-000047479 will be fixed in InstallShield 12.

Thank you.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT -6. The time now is 08:45 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
© 2010 Flexera Software Inc. All rights reserved.