> > The install directory itself is not a problem, although some older FB
> > installs have used the existing IB directory.

I suppose it's just a matter of what we include in the
Client set of programs.

> > The larger problem is with the Registry keys and environment variables,
> > changing those for v1.0 would have broken some tools/applications.
>
> In some parts of my app I need to get access to gbak.exe or other tools.
> Since there is no environment variable "INTERBASE" set during installation,
> I use the registry to locate those binary files:
>
> HKLM\SOFTWARE\Borland\InterBase\CurrentVersion
>
> I've noticed that RC2 still creates this registry entry, as well as a new
> entry
>
> HKLM\SOFTWARE\FirebirdSQL\Firebird\CurrentVersion
>
> I think for V1.0 this should be keept to keep existing apps working. Since
> Interbase and Firebird could not co-exist on the same machine, it would be
> no problem to use the Borland-Registry key.

I've not had to work back that way yet, but it makes sence
to have both in the short term.

This probably links to a short discussion on the new front
end tool site, about having a 'configuration database' like
isc4.gdb, but where information required by external users
could be stored - a first attempt at an ALIAS engine, but
where you can find 'published' information about the server,
such as where its databases are, etc.

> What is a "Sports tank"?

The new sleek version of Firebird - there was a reference to
Interbase being used in an american tank system, and the
discussuion 'grew' out of that.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services