We have a customer who needs to run our CB3 application on 64 bit Vista.
We're under a time deadline because if we can't do this quickly, his time to
return the computer will run out. Our current build fails completely
because we're using the old InstallShield that came with CB3 which is
apparently 16 bit. We're trying to build a new installation for the old
program using the InstallAware that came with CB2007. We can figure out
easily enough how to set it up to get our stuff installed but we're less
confident about getting the BDE installed and we don't have a 64 bit machine
to test on. InstallAware lacks the "install the BDE" option that the old
InstallShield had so we're going to have to do it by hand. I don't think we
can even use Borland's "BDE stub" because that probably...

See http://www.dbginc.com/bdenet/BDENet.html. This paper explains how
to install the BDE on a file server so that you do not have to install
it on each PC, however, IIRC, it does cover what files have to be
installed and the registry entries that must be created so it should
help you.

Note that I have no idea if the BDE will run on 64 bit Windows or not.
Hope this helps.

thanks, Bill. I've had that article of yours bookmarked for a long time and
I sent my programmer home with a copy to read tonight. if no one comes
along tonight who has actually done this, we'll see if we can get the
installation program to create the keys from your CreateKeys method. we
probably don't need to use ini files though. we'll just point the keys to
the locations the installer copied the files.

however, I don't see a list of the files that need to be copied in your
article. is it going to be the same set of files that a clean installation
puts into Program Files\Common Files\Borland\BDE?

Frank M. Cook wrote:

Yes. Those are the only files you need.

InstallAware did run on Vista 64 although we're having some difficulty
getting it to put the files where we asked it to. Not sure yet if that was
our error or Vista protecting Program Files tree. Because time is short,
our next step will be to attempt to simply copy the BDE files in manually
without using an install program, and then to create the Registry entries
manually. That should let us know if the BDE runs in this environment.

If we get over that hurdle, we can also copy our application files from
another computer at the site and see if our stuff works. we think it should
if the BDE is working properly underneath our stuff.

and if we get over both hurdles, we can return to automating the process
using InstallAware. I'll keep you all advised.

"Frank M. Cook" acsplus.com> wrote in message
news:48596c1b$1@newsgroups.borland.com...

really? we've had no trouble on 32bit Vista leaving the cfg file in Program
Files\Common Files\Borland\BDE. where are you putting it? we create an
OurCompany directory under the root and put out data there to get it out of
Program Files. should we create a BDE folder under our folder or should put
it in the hidden Application Data folder? we are resisting putting our data
files in Application Data because that would make it too difficult for our
users to back up or to transfer data to new computers.

It looks like they've done some housekeeping and eliminated old messages as
I don't find anything helpful in the old messages. I do have Bill Todd's
network installation instructions. what we're trying to do now is manually
set Registry entries for ConfigFile01, DLLPath, BLAPIPath, and SaveConfig.
We think if we get these four keys set, our application should be able to
take it from there.

if manually setting the four keys gets us working, we'll figure out how to
get InstallAware to automate this process. so far, we seem to have
InstallAware setting keys on XP but not Vista64.

based on the theory that the users will not universally have full rights to
the entire drive, you can't use the registry, you can't Program Files, and
you can't use anything else that is an "ordinary" Windows folder.. between
the info here, and the info on the various Paradox and/or BDE newsgroups
elsewhere, you will see many examples of that logic..

the "collective wisdom" is to make you own paths for everything, and to
default the BDE to use you own cfg files (the old Win 3.1 default)

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Frank M. Cook" acsplus.com> wrote in message
news:485a65c7@newsgroups.borland.com...

I haven't checked the Paradox groups. that's a good idea even though we use
dBase files.

we do use cfg files. I'm a little confused by the notion that you make your
own paths but don't use "ordinary" windows folders. we've been putting our
data in our own path but that is what I'd call an ordinary folder. I don't
see the issue in some users not having rights to that folder. if a user
wants to create a rights system to limit access to our program, why should I
defeat that by putting my data in all users\application data?

don't use Program Files or any other folder that Windows put there by
default.. the ability to put your own stuff under there depends on *many*
things under Vista..

it would be so much easier to say "don't use Vista".. but not everyone has
that option..

--
Steven Green - Myrtle Beach, South Carolina USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

"Frank M. Cook" acsplus.com> wrote in message
news:485a846a@newsgroups.borland.com...