Roland,

> > Firebird creates a window for the local IPC protocol communication,
> > and it's that window that requires the server to be set for "optimized
> > for applications". If you don't require the local IPC protocol, then
> > there's a parameter in the Firebird.conf file that you can change.
> > And, this change would permit the server to be put in "optimized for
> > services" mode.
> >
> > Here's the parameter and it's description:
> > [...start description...]
> > CreateInternalWindow
>
> [snip]
>
> when I set "CreateInternalWindow = 0" then it isn't possible to comunicate
> with the server engine any more from the machine on which the server engine
> resides, neither using "localhost:mydatabase" nor "servermachine:mydatabase"
> (TCP/IP).
>
> If you or other users can confirm that, then I propose to report it to the
> devel-list as "unexpected behaviour" (or is it a real bug?).

I can't confirm your reported behaviour, but I can confirm with
CreateInternalWindow = 0 that I can't start the guardian or the
server (without the guardian) when running as service, even when
the "Interact with desktop... " option (that's translated from
my German installation) is *unchecked*.

Does somebody know if this is "as designed" that the guardian/server
can't be run as a service with CreateInternalWindow = 0? I haven't
found anything in the Release Notes about that.

Windows 2000 Prof. German SP3, Firebird 1.5 RC 7 SuperServer.


Thanks,
Thomas Steinmaurer

Logging/Auditing Suite for InterBase and Firebird
http://www.iblogmanager.com
Logging/Auditing Suite for Advantage Database Server
http://www.adslogmanager.com