Herewith a few notes from tests etc. with RC7.

-------------------------------
New Configuration File section:
-------------------------------

In the Win32 bit it says:

3) Registry:
HKLM\SOFTWARE\ SOFTWARE\Firebird Project\Firebird
Server\Instances\DefaultInstance
and looks for the field RootDirectory.

I think it should say:

3) Registry:
HKLM\SOFTWARE\ SOFTWARE\Firebird Project\Firebird Server\Instances
and looks for the field DefaultInstance. It contains a string
defining the root directory.

Note that this string must include a trailing backslash.

-----------------
RemoteServicePort
-----------------
It says:

NOTE If a port number is provided in the TCP/IP connection string,
it will always take precedence over RemoteServicePort.

My tests do not confirm this - rather the opposite. If a port number
is specified in the config file it seems to override anything added
in the connection string. Even specifying 3050 in the file disables
the connection string port allocation. If that is a bug, then it
does not seem too important provided the documentation agrees with
the code.

The only way I could make a client use a different port to that in
the .conf file was to damage the registry entry so it could not find
the .conf file.


I could not find a description of how to specify the port in the
connection string anywhere in the release notes. I think it needs a
sentence such as:

The format of a TCP/IP connection string including a port number is
SERVERNAME/PORT:{FILE|ALIAS}

------------------
dll location tests
------------------

And, further to the previous tests of what happens with dll's in
different locations:

I don't think there are any surprises here, but it may help to have
confirmation that it performas as you might expect.

Using a traditional app that tries to load gds32, it will always use
a gds32 that is in the local application directory in preference to
one in the system directory. However, placing fbclient.dll in the
application's directory will not cause the application to use it
unless there is a myapp.local file or the registry entry is missing.

If you place the gds32 stub in the system directory but not in the
app directory and you place fbclient in the app directory, a
myapp.local file will make gds32.dll load fbclient from the app
directory even if there is a proper registry setting.


Thanks to the team for all the hard work getting this new release
ready.

Regards

Eric Thorniley