We are using a commercial product based on Firebird (currently 2.0.3)
running on Windows XP. The application is a client-server
configuration, with the application server program running as a
program (not a service) on the same computer that firebird runs on. I
cannot upgrade the version of firebird without losing my service
contract on the software.

At times something goes wrong, and the error message we get is not
enough information for us to figure out what happened. On one
occasion I was desperate enough to track down the cause that I moved
firebird and the database file onto another computer, and used
Wireshark to look at the sql traffic between the application server
and firebird. This traffic display was quite revealing, and I was
able to track down the problem without too much additional work.

This information is valuable, but it is a lot of work to move the
database in order to troubleshoot it. Various sources say that FBHook
can supply similar information, so I downloaded it and tried it.
After wasting a couple of man-days trying things and still coming up
with nothing, I ask for someone to help me with some kind of
documentation for FBHook, (or an alternative that will work in my
situation). Since alpha version 0.3 seems to work "good enough",
there seems to be no documentation, and running FBHook with a command
line parameter of /help produced nothing either.

My educated guess is that FBHook is a "loop through" style monitor,
where I am supposed to redirect my calls to the database to a new
port, where FBHook will log them and then pass them on to port 3050.

Based on the above assumption (after other methods based on other
assumptions failed), I started FBHook on the server, and then tried to
connect to it using DbVisualizer (using JayBird). I took an existing
connection to the database and edited it so that it went to port 61275
instead of port 3050. I know FBHook is there, because I get a
different error number when FBHook is started than when it is not, but
I cannot connect to my database. I renamed the supplied fbclient.dll
and copied the newer fbclient.dll that comes with our software, but
that didn't help either. Windows firewall was disabled during this test.

Would someone please be kind enough to supply whatever critical
piece(s) of information I do not have, so that I can implement
monitoring on my server?

Ted