PDA

View Full Version : Detection of BDE



NewsArchive
05-28-1997, 12:00 AM
Hi,

I am wondering about why ISX (any version) does not have the functionality
of detecting the currently installed BDE (if there is one) and either
overwriting (if the files to be installed are newer) the files or
installing any missing ones.

It seems that some members of the Delphi comp.lang.pascal.delphi.*
newsgroups have a problem if there is a BDE version installed.

Also the installer removes such files when uninstalling, rendering the rest
of the applications using the BDE inoperable. Is that an Installshield
problem or is that a Borland problem?

Happy coding

Stefan Paetow
ellipse data systems

== owner@ ==
== ellipse- ==
== data.com ==
== Fix the ==
== above for ==
== address ==

-
=========================================================================
= Any opinions here are my personal opinions, not those of my company =
= Home on the web: http://www.ellipse-data.com/ =
= Delphi Super Page: http://ftp.is.co.za/dsp/ =
= Delphi User Groups in South Africa: http://www.delphi.co.za/dugg/ =
=========================================================================

NewsArchive
05-28-1997, 12:00 AM
We're looking into this issue and if there is a problem in Express 2
you'll see a fix for this in a maintenance release.

--
Rajesh Ramachandran
InstallShield Corporation

NewsArchive
05-28-1997, 12:00 AM
Rajesh Ramachandran <rajesh@installshield.com> wrote in article
<01bc6bb3$00398960$8c46b1cc@drain>...
> We're looking into this issue and if there is a problem in Express 2
> you'll see a fix for this in a maintenance release.
>
> --
> Rajesh Ramachandran
> InstallShield Corporation
>
>

What about a maintenance release for 1.1? Is there one that I am unaware
of?

There are several bugs I would like to see fixed. I don't like having to
upgrade to get bug fixes. I like to upgrade for features (which, of course,
generally introduce more bugs). I don't make my customers pay for bug
fixes.

Am I unreasonable?

How about fixing the poor long file name support? It's no big deal, but...

And... I'd love to here SOMETHING about this...

I am using InstallShield Express Professional version 1.1.
When I run a 32-bit installation I have created, I get the following:

Runtime Error!
Program: C:\TEMP\_INS0432._MP
abnormal program termination

This seems to happen when I include an extension DLL I have created. (The
DLL is fine - it executes - the error happens well after the function in
the DLL has been called.) Without the DLL as part of the installation it
works fine..

16-bit installs seem to be able to call DLLs fine.

And the sad thing is that my DLL (now an EXE - because the DLL won't work)
is just to copy an uncompressed file from the first disk. A SIMPLE task
that InstallShield Express Professional can't handle.

I'm AMAZED that ISXP can't do this for me. Perhaps I'm missing something.

Any comments?

NewsArchive
05-28-1997, 12:00 AM
We're looking into this issue and if there is a problem in Express 2
you'll see a fix for this in a maintenance release.

--
Rajesh Ramachandran
InstallShield Corporation

NewsArchive
05-28-1997, 12:00 AM
Rajesh Ramachandran <rajesh@installshield.com> wrote in article
<01bc6bb3$00398960$8c46b1cc@drain>...
> We're looking into this issue and if there is a problem in Express 2
> you'll see a fix for this in a maintenance release.
>
> --
> Rajesh Ramachandran
> InstallShield Corporation
>
>

What about a maintenance release for 1.1? Is there one that I am unaware
of?

There are several bugs I would like to see fixed. I don't like having to
upgrade to get bug fixes. I like to upgrade for features (which, of course,
generally introduce more bugs). I don't make my customers pay for bug
fixes.

Am I unreasonable?

How about fixing the poor long file name support? It's no big deal, but...

And... I'd love to here SOMETHING about this...

I am using InstallShield Express Professional version 1.1.
When I run a 32-bit installation I have created, I get the following:

Runtime Error!
Program: C:\TEMP\_INS0432._MP
abnormal program termination

This seems to happen when I include an extension DLL I have created. (The
DLL is fine - it executes - the error happens well after the function in
the DLL has been called.) Without the DLL as part of the installation it
works fine..

16-bit installs seem to be able to call DLLs fine.

And the sad thing is that my DLL (now an EXE - because the DLL won't work)
is just to copy an uncompressed file from the first disk. A SIMPLE task
that InstallShield Express Professional can't handle.

I'm AMAZED that ISXP can't do this for me. Perhaps I'm missing something.

Any comments?

NewsArchive
05-29-1997, 12:00 AM
see the signature below for address wrote:
>
> Hi,
>
> I am wondering about why ISX (any version) does not have the functionality
> of detecting the currently installed BDE (if there is one) and either
> overwriting (if the files to be installed are newer) the files or
> installing any missing ones.
>
> It seems that some members of the Delphi comp.lang.pascal.delphi.*
> newsgroups have a problem if there is a BDE version installed.
>
> Also the installer removes such files when uninstalling, rendering the rest
> of the applications using the BDE inoperable. Is that an Installshield
> problem or is that a Borland problem?
>

I got a upgrade from IS to 1.1a and it fixed that problem. Since the
release of ISX2, ISXP has basically been removed from the site. Oh yeah,
except fot the fact that it won the SPA award. The only dropdown box
that I found with the ISXP was on the site feedback form.

--
jim mccullough
Digital Alchemy Labs, Inc.
http://www.dalab.com
mailto:the_alchemist@usa.net

NewsArchive
05-29-1997, 12:00 AM
see the signature below for address wrote:
>
> Hi,
>
> I am wondering about why ISX (any version) does not have the functionality
> of detecting the currently installed BDE (if there is one) and either
> overwriting (if the files to be installed are newer) the files or
> installing any missing ones.
>
> It seems that some members of the Delphi comp.lang.pascal.delphi.*
> newsgroups have a problem if there is a BDE version installed.
>
> Also the installer removes such files when uninstalling, rendering the rest
> of the applications using the BDE inoperable. Is that an Installshield
> problem or is that a Borland problem?
>

I got a upgrade from IS to 1.1a and it fixed that problem. Since the
release of ISX2, ISXP has basically been removed from the site. Oh yeah,
except fot the fact that it won the SPA award. The only dropdown box
that I found with the ISXP was on the site feedback form.

--
jim mccullough
Digital Alchemy Labs, Inc.
http://www.dalab.com
mailto:the_alchemist@usa.net