PDA

View Full Version : ISX 2.0 Not adding BDE Registry Entry



NewsArchive
01-19-1998, 01:00 AM
Express 2.0 is not adding HKEY_LOCAL_MACHINES\SOFTWARE\BORLAND entry in
the target machines registry. Do I not have something configured
correctly?


Thanks

Keith Breuer

NewsArchive
01-19-1998, 01:00 AM
On Mon, 19 Jan 1998 12:36:50 -0500, Keith Breuer <kbreuer@esicomputer.com>
wrote:
>Express 2.0 is not adding HKEY_LOCAL_MACHINES\SOFTWARE\BORLAND entry in

Should be HKEY_LOCAL_MACHINE

What exactly are you trying to add?

Stefan
ellipse data systems

NewsArchive
01-19-1998, 01:00 AM
Stefan Paetow wrote:
>
> On Mon, 19 Jan 1998 12:36:50 -0500, Keith Breuer <kbreuer@esicomputer.com>
> wrote:
> >Express 2.0 is not adding HKEY_LOCAL_MACHINES\SOFTWARE\BORLAND entry in
>
> Should be HKEY_LOCAL_MACHINE
>
> What exactly are you trying to add?
>

Sorry for the type-o...

After the installation, I run my newly installed program, and I get a
BDE error $2109. According to Borland, this error is caused because the
HKEY_LOCAL_MACHINE\SOFTWARE|BORLAND|DATABASE ENGINE|DLLPATH is empty or
does not exist. Well, in the target machine, there is no entry for
Borland at all. I am assuming that the setup is not creating this. Is
there something that needs to be configured in ISX to get the
installation to work properly. NOTE: I have been using ISX 1.1 and 2.0
for awhile now and have never had this problem before.

Thanks for the quick response!

NewsArchive
01-20-1998, 01:00 AM
On Mon, 19 Jan 1998 15:27:25 -0500, Keith Breuer
<kbreuer@esicomputer.com> wrote:
>After the installation, I run my newly installed program, and I get a
>BDE error $2109. According to Borland, this error is caused because the
>HKEY_LOCAL_MACHINE\SOFTWARE|BORLAND|DATABASE ENGINE|DLLPATH is empty or
>does not exist. Well, in the target machine, there is no entry for
>Borland at all. I am assuming that the setup is not creating this. Is
>there something that needs to be configured in ISX to get the
>installation to work properly. NOTE: I have been using ISX 1.1 and 2.0
>for awhile now and have never had this problem before.

I've been having the same problem with a CD-Rom build where the
setup.1 file iss about 83Mb. However when I create a simple test
installation, all works OK.

Could it be that this is a bug in ISX with handling installations
larger than the magic 64Mb? (Or some other funny number)

Mark.

NewsArchive
01-20-1998, 01:00 AM
On Mon, 19 Jan 1998 15:27:25 -0500, Keith Breuer <kbreuer@esicomputer.com>
wrote:
>BDE error $2109. According to Borland, this error is caused because the
>HKEY_LOCAL_MACHINE\SOFTWARE|BORLAND|DATABASE ENGINE|DLLPATH is empty or
>does not exist. Well, in the target machine, there is no entry for
>Borland at all. I am assuming that the setup is not creating this. Is

There shouldn't be anything else. All I can tell you is that InstallShield
is working on improving the BDE object, specifically because many people
have problems with it.

Stefan
ellipse data systems

NewsArchive
01-21-1998, 01:00 AM
Stefan Paetow wrote:
>
> On Mon, 19 Jan 1998 15:27:25 -0500, Keith Breuer <kbreuer@esicomputer.com>
> wrote:
> >BDE error $2109. According to Borland, this error is caused because the
> >HKEY_LOCAL_MACHINE\SOFTWARE|BORLAND|DATABASE ENGINE|DLLPATH is empty or
> >does not exist. Well, in the target machine, there is no entry for
> >Borland at all. I am assuming that the setup is not creating this. Is
>
> There shouldn't be anything else. All I can tell you is that
> InstallShield is working on improving the BDE object, specifically > because many people have problems with it.

I actually downloaded and installed the 2.01 upgrade it it seems to be
working for now. Do note however that the probblem wasn't occuring
until recently. It just started sorta out of the blue. I tried to think
what have I changed on my PC that could be causing this problem, but I
couldn't think of any thing. But for now it appears the upgrade has
cured my problem.

Thanks for your help.


Keith

NewsArchive
01-21-1998, 01:00 AM
On Wed, 21 Jan 1998 13:57:53 -0500, Keith Breuer <kbreuer@esicomputer.com>
wrote:
>until recently. It just started sorta out of the blue. I tried to think
>what have I changed on my PC that could be causing this problem, but I
>couldn't think of any thing. But for now it appears the upgrade has

I'm pleased to hear it went away.

Stefan
ellipse data systems