preliminary MDAC 2.6 testing
Heather B.
Could others using command line flags and running MDAC as a custom action
please respond with their suggestions of what flags to use? I have tested
version after version of the new MDAC merge module before it has become
available to the general public and none of them solve the problems we are
having with our setup running on Win98, Win2000, and Win XP.
After literally 6 months of problems with InstallShield's MDAC merge modules
and problems related to, and caused by, the stupid MDAC merge module, I am
giving up on the merge module approach.
Clearly InstallShield has no idea how to properly install MDAC, and how to
work with MSI, for that matter. If it weren't for the literally hundreds of
hours I have invested in working with and tweaking our InstallShield project
to work around all of their ridiculous ongoing issues and get ISX to do what
it purports to do, I would be giving up on InstallShield entirely and moving
to WISE.
Any and all suggestions to help me salvage all of the wasted hours I have
put into InstallShield Express and get MDAC reliably installed with our
project would be appreciated greatly.
Thank you.
Heather
"Chandima Rajakaruna" <no re...@installshield.com> wrote in message
news:3b9d1050$1...@news.installshield.com...
> Word of caution. I think MDAC has minimum system requirements of Internet
> Explorer 4.01 Sp2 and Windows NT Service 5. Installing MDAC on systems
that
> do not meet these requirements might cause endless reboots. Also if I am
not
> mistaken MDAC 26 should not install on XP because it has files with
version
> number 2.7 (and reg entry) which suggests it comes with MDAC 2.7.
>
> FYI- We will be releasing a new updated MDAC26 and MDAC25 Sp2 merge module
> very soon. It includes quite a few fixes and might suit your needs.
>
> "James P. Hoffman" <jpho...@velocenet.net> wrote in message
> news:3b9ccd90$1...@news.installshield.com...
> > FYI, I've done some preliminary testing with running MDAC_typ.exe as a
> > custom action. First, I found it needs to run "After Register Product"
> since
> > ISX breaks MDAC 2.6 on the test WinME machine during product
registration.
> > Second, I found it best run without a command line because the program
> takes
> > awhile and no feedback feels odd, also because MDAC tells the user if
they
> > need to reboot. Finally, you need to use Wait for action = NO" and
"Ignore
> > Exit Code = YES" or the install may hang. (If it does, you can cancel
> dsetup
> > and the install ends successfully.) Microsoft says that MDAC will not
> > install inself on a 2k machine since it's shipped with the system; I
> haven't
> > tested this.
> >
> >
>
>