On Monday 22 September 2003 21:53, peter_jacobi.rm wrote:

> I should have made clearer, what I'm missing.
>
> I expect to use to OpenWatcom C/C++ compiler (but I would
> consider using FreePascal, if it makes things better).
>

No - the C compiler combined with gpre would be fine, but that is the least of
your problems.

> What's missing is the layer that translates FB API calls
> of some sort into wire protocol and forward this to
> the Packet or NDIS driver of the Ethernat card.
>
> And as there are no Dlls, this must be compiled in.
>
> I assume, theoretically, I would have only to grab the
> FB source tree for the client Dlls and make 'some minor
> porting' changes. Hmmmm.
>

You have two choices, neither of which are trivial.

1/ Look at compiling a version of gds32/fbclient that is not dependant on the
Win32 libraries. It is obviously possible, but how much work is involved in
doing this for DOS is anyones guess. However, there are plenty of examples in
the source for compiling the client library for all sorts of platforms. That
said, I don't think it has ever been done. Even the 16-bit version (gds.dll)
was for use in a Win 3.1 environment.

2/ Look at the JayBird source. Jaybird talks directly with the server via the
wire protocol. It does not use a client library. The .Net driver is derived
directly from the JayBird driver. You could port the basic concept to C++.
The downside to this approach is that if (when?) the wire protocol changes
you will need to re-write/extend the driver. (As will the JayBird and .Net
projects.)


Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase