Re: [Firebird-devel] Win32 build

[Dmitry K. <di...@de...>]

Hello, Claudio!

"Claudio Valderrama C." wrote:

> > Remember that a very little bug in installation can make bad first
> > product impression.

>         It seems it has been fixed in the source code (not sure if latest release
> carries the change), but from a Win32 POV, those things are important.
> Windows is an environment where one calls SETUP and [often] has to reboot
> after. Putting in the trash can the eternal discussion about Windows v/s
> UNIX installation mechanisms, if we produce a Win32 release, it should
> behave like a typical Win32 setup.

So, I see it as suggestion not to change SERVICES file at all?
It will be fine, but readme must say that FB uses 3050 port by default
(server and client).
This all will simplify base and custom installation (at least).

>         Geoff Worboys has told me, too that Firebird install for Windows doesn't
> include the
> GuardianOptions entry in the registry. Hence, IB Guardian won't start. This

this is not only one problem on Win32:
1. Borland never had command-line utility to configure guardian service.
   (instsvc only configures ibserver service)
2. Guardian always was configured by special interactive software, that
not included in Firebird install (I don't remember it's name, there were special CPL).
This software also was not working fine in some conditions (don't remember too).

> string version and (on Windows) in the registry path that firebird will use:
> will we continue using
> HKLM/Software/Borland for our releases?

HKLM/Software/Firebird will be better.
Really, if ibserver.exe name will be changed for firebird, there'll be possibility
to run FB and IB at the same time (at different ports). I don't know is it good
or bad. Of course it will be bad if two processes will try to work with the same
gdb.

-- 
Dmitry Kuzmenko, Epsylon Technologies.