At 04:02 PM 27/11/2003 +0100, you wrote:

>Use the client that matches the version and date of the server executable
>and root out those rogue versions of gds32.dll on the workstation hard
>disks.
>
>The name of the server executable is ibserver (if you are using
>Superserver) or ib_inet_server (if you are using Classic). You should find
>them in /opt/Firebird/bin. To find out whether the server is Classic or
>SS, do a
>ps -aux | grep ib
>from a Linux shell.
>
>heLen
>
>
>
>Dear heLen,
>
>thanks a lot, I've found that the firebird server was installed from this
>file: FirebirdSS-1.0.2.908-1.i380.rpm, but I tried to find the proper client
>and wasn't successful.

For your Windows clients, you need to get the Firebird 1.0.2 Windows kit
and perform a client-only install on each client.

>On
>http://firebird.sourceforge.net/index.php?id=newsarchive there are a lot of
>files but non is described as a client for the FirebirdSS-1.0.2. Is it
>"jdbc-InterClient"?

No. Client libs are not distributed separately. That jdbc-InterClient is
the old (never finished) IB 6 Java driver and it doesn't work with Firebird.

>I have tried to install a different client (IBWin32ClientSetup.EXE), it's
>from another town in our country where they use the same application with
>Firebird on Linux and Windows clients and it works.

That won't have the Firebird client in it. You need to look at the
Properties sheet of the gds32.dll file on the client. On the Version page
of the tabsheet, you will see a list of properties under "Other version
information". The last entry "Special Build Description" should say
"Firebird 1.0.2". The "File version" entry near the top of that sheet
should be "6.2.3.908"

>But it didn't help, the
>error is the same, after some delay the programe announces the error win32
>10054 and ends in cycling error.

The "cycling error" loop is caused by your application software. Until
your supplier fixes it, it will happen every time there is an exception.

>Do I understand well that before installing the new client I shall delete
>the file c:\Windows\System\gds32.dll ?

You won't find gds32.dll in this location. On Win95/98/ME it is in
c:\Windows. On WinNT, Win2K and XP it is in c:\Windows\Winnt\System32.

Try to rename it first. If it won't let you rename it, then it is in
use. The machine will have to be rebooted.

>I used IB Expert to find out in the database properties that the the forced
>writes are "on".

Good. :-)

Helen