At 09:41 AM 17/05/2005 +0000, you wrote:

>They are Set to auto. None of our apps are services - Just standard
>apps, although a couple just sit in the system tray.
>
>If we didn't launch stuff at startup, and just relied on manually
>launching the stuff, there is no problem. Since FB is supposed to be
>running as a service, it should be completely up and running before
>you've even logged into windows - This is what makes me think it might
>be the guardian's fault, as I think that runs as an app, rather than a
>service,

Guardian is installed to run as a service by default. It would certainly
be "something to fix up" if your system is waiting for a user to log on
before Guardian can be started. If they are both properly installed, i.e.
as per the standard installer, both should be up and running before the
login screen appears. Nobody has to be logged in for the service to be
accessible to clients.

> so it's not launching the FB Service until after windows is
>logged in and it starts?

If that's the case then it's been broken by human interference and needs
fixing.

>We're going to do some experimenting... another thing is that we never
>had this problem with interbase 6 Opensource.

No D.I.Y. installs in those days?

Is there a possibility that you have IB 6 artifacts hanging around? If
you're using Fb 1.0.x, it's quite possible, since the executables have the
same names. Whatever, it appears you have some kind of a mess-up there.
The first place to begin the reality check is by inspecting the property
sheets of the two running services (in the Services applet).

FYI, the service names are:
Firebird 1.0 - FirebirdGuardian and FirebirdServer
Firebird 1.5 - FirebirdGuardianDefaultInstance and
FirebirdServerDefaultInstance

./heLen