Subject Startup parameters for Win32
Author Claudio Valderrama C.
Hello. I thought people running IB/FB on Win32 might be interested in those
flags that can be given at startup to the engine:

1.- The Guardian only understands -a for running it as an application.
Available on NT/W2k/XP because in W9X it always runs as an application.
I think we could implement -n when starting it as an application so it will
additionally run without an icon in the tray. Anyone interested? User would
lose the ability to see the Guardian report on engine failures (because
there's no icon to click in the tray) and I think it would be more useful
when GuardianOptions is "1" in the registry, because in this case, the
guardian keeps restarting IB as many times as necessary; otherwise it will
close itself after the server finishes for the first time.
When the guardian starts the server, it passes to the engine the parameters
-a -n if running as an application, so the engine won't show its own icon in
the tray (you see the Guardian icon instead). Here I got the idea of hiding
the guardian's icon, too.

2.- The engine itself supports several options:
-a run as application
-b run with high priority
-d debug and run as application
- n no icon (if as an application; when running as service it never shows
the icon)
- There are flags for TCP, named pipes and IPC but they are controlled by
the license file for IB with licenses and are always enabled for Firebird.
They are commented for now, although it would be nice to reverse them to
signal protocols that should be disabled.
-p followed by a port name or named pipe (gds_db by default), to change the
default (don't ask me if the client has matching functionality <g>).
-r run with normal priority (default)
- z print version and exit (in practice, I see nothing printed in the

Claudio Valderrama C. - -
Independent developer
Owner of the Interbase® WebRing