The changes in the layout of Firebird on windows (moving binaries to the <installation root> instead of <installation root>\bin) seems to be causing some problems for applications locating the client library binary:
For example Flamerobin is not able to find fbclient.dll if I install without copying to the windows (system32) folder, while this works fine with Firebird 2.5. When I install with client library copied to the windows folder it works. But when I trigger an error, the error message includes an error that it is unable to locate firebird.msg. I have also noticed a problem that I am at times unable to authenticate (using fbclient.dll), but I haven't been able to pinpoint the problem. I believe it doesn't work when I have both Firebird 2.5 and 3.0 running. I am not entirely sure about the details. I noticed this two weeks ago (can't remember if I couldn't authenticate to FB2.5 or 3.0 with legacy auth or srp or both), but I currently don't have the time to test this extensively and maybe someone else noticed as well. At that time authenticating with the Jaybird implementation of the wire protocol (which uses legacy auth) works fine. -- Mark Rotteveel ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
