On 30/05/13 16:29, Dmitry Kuzmenko wrote:

> Norman, if you speak about 32/64 bit correspondence, explain it.
> Not to me, but to person who you ask about it.

Yes, good point.

> Usually most people doesn't understand 32/64 at all.
> But, at least for client software there no difference
> of the server "bitness".
>
> Marcus Bajohr - respect for the list of "no-go".


Right, 32/64 bit - from memory as I'm a wee bit rusty on Windows these days.


If you have a 64 bit PC with a 64 bit operating system on it - be that
Windows, Linux or whatever - you can run 32 and/or 64 bit applications
on it. Under some Linux distros, you may need to install the 32 bit
support libraries though.

If you have a 32 bit machine, then you can only run 32 bit applications.

Now, if you are using client-server applications, then as long as you
have a client that is supported and runs on your machine, 32 or 64 bit,
then it makes no difference what the server is running as.

So a 64 bit client can talk to a 32 or 64 bit server and a 64 bit client
can communicate with a 32 or 64 bit server too.

The only restriction is what is running physically on your PC.

In the case of Firebird, you might be running a 32 bit client and
talking to a 32 or 64 bit server, it won't make any difference as you
will still see exactly the same data.

64 bit Windows 7, as far as I remember, does not like to mix 32 and 64
bit DLLs, EXEs etc, so it tends to install the 64 bit stuff into
"Program Files" and the 32 bit stuff into something like "Program Files
(X86)" or something with "(x86)" in the name.

This latter path name, because of the '(' and ')' characters, can cause
some applications (or client software) not to work properly, and you
have to reinstall it into a path that doesn't have the parenthesis (and
sometimes spaces too cause problems).

HTH

Cheers,
Norm.


--
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
Thorpe House
61 Richardshaw Lane
Pudsey
West Yorkshire
United Kingdom
LS28 7EL

Company Number: 05132767