Re: iAccess Client Solutions; "only an IBM ID" required; err, not exactly

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.