× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 08/11/2016
01:16:36 PM:

From: CRPence <crpbottle@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 08/11/2016 01:17 PM
Subject: Re: iAccess Client Solutions; "only an IBM ID" required;
err, not exactly
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

On 11-Aug-2016 12:21 -0500, Kevin Adler wrote:
On 10-Aug-2016 20:10 -0500, CRPence wrote:
On 10-Aug-2016 17:55 -0500, Kevin Adler wrote:
On 09-Aug-2016 18:38 -0500, CRPence wrote:
<snip>

What model Mac and what version of OS X are you running? I think
that the .app is built against 10.6 in both 32-bit and 64-bit
"fat binary" format, so it should support most any Mac out there
nowadays.

≤About This Mac:≥
Mac OS X Version 10.6.8
Processor: 2.16 GHz Intel Core Duo
Memory: 2 GB 667 MHz DDR2 SDRAM

Ok, so you have a 32-bit only Mac.

Apparently, I was wrong and the app that gets built is 64-bit only:

<key>LSMinimumSystemVersionByArchitecture</key>
<dict>
<key>x86_64</key>
<string>10.6</string>
</dict>


$ file MacOS/Application\ Stub
MacOS/Application Stub: Mach-O 64-bit x86_64 executable

And also looks like the same with the application launcher:

$ file Start_Programs/Mac_i386-32_x86-64/acslaunch_mac
Start_Programs/Mac_i386-32_x86-64/acslaunch_mac: Mach-O 64-bit
x86_64 executable


Hmm. OK. Does that indicate I should not use the application; that
doing so might interfere with my ability to use my system, such as
perhaps locking-up or otherwise crashing the system.? Or perhaps
instead that I might merely encounter minor inconveniences when things
do not function correctly, but typically identified as "not supported"
rather than application [component] crashes or mysteriously
ignored-requests or never-appearing output.?

The double-clicking on the .app giving an effective "unsupported"
error seems innocuous enough, but I have yet to try anything beyond
getting to the Welcome screen after launching the acsbundle.jar so some
confirmation about the safety of actually attempting to use the function

presented would be appreciated; or perhaps instead, if I should probably

just uninstall.


ACS is a Java application and it's designed to run on any platform with a
sufficiently "new" Java JVM. For convenience, we provide some start
programs for various platforms. These start programs have some benefits:
- file associations can be set for the application, but not a jar file
- feels more native
- nice icon for the application
- start applications will search various places for a suitable JVM, so you
don't have to monkey with that


The start programs or Mac app are not required, however. The only thing
really needed is the acsbundle.jar. It will work just fine on your Mac and
should be fully supported by IBM if you run in to a problem. You just
won't be able to use the Mac app or the start program.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.