--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:

> all you do is install to different directories and set difffernet

ports for

> each installation.
> make sure when you install subsequent installs that you do not

initially set

> teh service to run until you have changed the port.
> Alan

Hi Alan,

Unfortunately that doesn't work. In a normal FB 1.5 (superserver)
install it adds a registry key to tell it where to load the
firebird.conf file from, irrespective of where it is installed. It
sets the location to the server exe parent folder.

All FB 1.5 server (at least superserver) instances read that reg key
and load the same firebird.conf. They all think that they
are "DefaultInstance". There does not seem to be a way to tell each
instance to load a different firebird.conf, other than deleting the
registry key in which case they fall back to locating the
firebird.conf from their independent server exe parent directories.
Currently the registry key that is checked is based on the hard-
coded #define FB_DEFAULT_INSTANCE "DefaultInstance" line in
registry.h.

I can't simply delete the reg key to force the instances to look in
their parent directory because later the user might install FB again
and the reg key will be there again to cause problems.

Regards,
Jarrod Hollingworth