> 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.

That's what I thought..

> If that's the case then it's been broken by human interference and

needs

> fixing.

I wasn't personally involved in the installs, but these terminals are
all installed from new, so will have been fresh Win2K systems, with no
previous Firebird/Interbase install, and FB was installed with the
standard installer. The only time we've not installed it as a service
is of course on the odd win98 machine (which we haven't in this case).

We're using Firebird 1.5. These terminals were all running interbase
6.0 Opensource, and we have a number 'out there' which are fine with
it (again, just the default installer). We've only got this problem
since switching the install over to FB. (We spent some time 'playing'
before deciding to make the switch.. Continuing to use an unsupported
dead-end is stupid IMO).

The really annoying thing is how intermittent the problem is. We
can't reliably repeat it, which makes it a real pain to track down.

Thanks for the responses so far....