"Günter" <info@NoSpam-mk-news.com> wrote in message 
news:59b6332d$1@pnews.thedbcommunity.com...
> Hi Leslie,
>
> how do you  "install bde outside"?

We use the correct installer which is actually Installshield and created a 
wrapper incoporating the standard BDE installation steps within ours and 
then we added some custom actions to configure various aspects of the BDE.

Because we also knew this would be useful to the Paradox group we made it as 
generic as possible and allow the caller to determine behaviour via an ini 
file - meaning that we never have to rebuild the installer (unless it is to 
add new features). The BDE destination folder is actually optional and set 
via this ini file, which we have defaulted to \BDE32 on the Windows 
Installation Drive.


> my installer use the capability of Inno-Setup, the bde install there
> need a correction for 2GByte-border, but i hacked this in the past.

The 4Gb diskspace patch is one of the options we allow as well as install 
time alias creation and also conditional settings such as only updating the 
MAXFILEHANDLES if they are currently lower than the value you want. This 
means not damaging other applications which require a larger value than you 
may be trying to set. The standard BDE installer gets this sort of thing 
wrong because its cfg merge feature is pretty dumb at some things.


> actual my installer need admin rights

Installers usually run elevated anyway so that in itself is not an issue. In 
fact if you call the installer setup.exe Windows will automatically elevate 
it.

But yes I can see that because of the way inno-setup works you may have to 
mess around with things a little bit more because you are doing things 
sequentially - effectively after the event. My guess is that alias creation 
is also a separate step as well. Ours is as all in one as we can get with 
the current solution.


> and a correction to move after
> first start the modified IDAPI32.CFG from
> C:\Users\xxx\AppData\Local\VirtualStore\Program Files (x86)\Common
> Files\Borland Shared\BDE to c:\progr... for running runtime9 as normal 
> user.
>
> your solution is better.

Yes, Virtual folders are a nightmare and need to be avoided at all cost. But 
make no mistake we are still moving things around as we need to cater for 
the BDE already being installed.
So really it is just that we are doing it at a different point in the 
installation process to you (because we can) which simplifies things a lot 
more.

Our solution was done as a quick response to UAC being introduced. However, 
with time and hindsight there are better ways to get the BDE on the machine 
while still remaining compliant. I just cannot justify looking at it too 
much at the moment because we are looking to move away from the BDE anyway

So although it works, I am not entirely happy with our solution. Maybe just 
for the hell of it one day I will have another crack at it just as an 
exercise - cause that's what IT people do right we don't play being the 
victim ?

Leslie.