At 07:22 PM 3/08/2004 +0200, you wrote:

>Should Firebird Classic server work on Windows 95 ?
>I tried only on VirtualPC, and when the guardian starts I get error
>
> "fbserver.exe: The guardian was unable to launch the server thread.
> errno : 2"
>
>(When I installed Superserver instead of it, it worked o.k.)

That's because fbserver.exe is the process that Guardian starts.
:-) Classic is fb_inet_server.exe.

All my tests with the Classic installer so far fail to install Guardian in
a way that knows to start fb_inet_server.exe, as either a service or an
application. That's the case on both Win98 (application only, of course)
and Win2K (application or service). I haven't tried on Win95. I haven't
installed 1.5.1 Classic yet to test whether anything has changed in the
installer.

You can make Guardian run the fb_inet_server "listening" process by
creating a shortcut for fbguard.exe and modifying the Start line as follows:

"C:\Program Files\Firebird\Firebird_1_5\bin\fbguard.exe" -c

Likewise, if you're starting the application automatically at boot-up,
you'd need to modify that shortcut too.

My "take" on Guardian with Classic:
Guardian was designed to restart the multi-threaded Superserver process if
it stops abnormally. Since an individual server process is launched for
each connection to Classic, what would Guardian actually be expected to
restart if any instance of fb_inet_server crashed? If it was a server
instance started for a client, how would Guardian find the client whose
process crashed?

Because I couldn't make Guardian do anything sensible with Classic, in the
book I suggested just forgetting about Guardian for Classic. It doesn't
seem relevant. I'd be happy to be put straight about this, though.

/heLen