Dear,

On Thu, 4 Dec 2003 09:47:39 -0600,
Ed Salgado wrote :

> We have a dual-processor 2.4Ghz Xeon machine running Win2000 server with
> the Firebird database. Everything seems to run fine, but the Firebird
> database takes a long time to start up. The system is set up to auto-logon
> and run our app from the startup group, but our app fails to connect because
> Firebird hasn't booted yet.

There is NOTHING in Windows that says Services will be ALL already be
started when the user logs on. The only thing you can do (if your app
runs on the same machine as the server) is to have your app connect to
the Windows Service Manager and polls it to see if Firebird has
started. If not wait a bit then recheck. When started, let your app
proceed with the connection.

Services are started by Windows. And MS did all it could in Windows
2000 et XP to as quickly as possible gives you the logon scren (or
proceed with the auto-logon). This enhance the possibility that not
all services will already be started when the startup group will be
processed by the Explorer.

Maybe there is a trick or registry setting to tell Windows to *differ*
login until all services are started (I think it reminds me something),
but I'm not sure.

The firebird-support is much more suited to this than this list.
I'm cross-posting there. Please all followups to firebird-support.

--
Best Regards,
Olivier Mascia