Re: Way to programmatically determine whether 32-bit or 64-bit Client Access is installed? -- MIDRANGE-L

Subject: Re: Way to programmatically determine whether 32-bit or 64-bit Client Access is installed?
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Thu, 3 Aug 2017 14:17:30 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Thu, Aug 3, 2017 at 1:50 PM, Dan <dan27649@xxxxxxxxx> wrote:

I noticed that I have the "Shared64" folder in my "Client Access" folder.
Can anyone verify that this does not exist on a 32-bit install and/or that
it will exist on a bare-bones 64-bit install?

I do not have "Shared64" (only "Shared"). I guess that means my
installation is 32-bit, though I do not know how else to verify that.
I spot-checked a few of the executables (including rfrompcb.exe and
rtopcb.exe) and they were all 32-bit, according to the detection
method given here:

<https://superuser.com/a/889267>

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Way to programmatically determine whether 32-bit or 64-bit Client Access is installed? , Dan

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.