http://imagej.273.s1.nabble.com/Macosx-10-5-Java-Update-4-on-intel-tp3692120p3692125.html
> I confirm the behavior with the ImageJ64.app stub launcher and Apple's
> Java Update 4 (which includes java 1.6.0_13 x86_64). I have the same
> errors on the console.
> I can start ImageJ.app (in 32bits), and I can start ImageJ in 64bits
> from the command line, so there is a problem with the ImageJ64.app
> stub launcher and the Apple update.
> Mat
>
>
> On Tue, Jun 16, 2009 at 8:12 AM, Karsten
> Rodenacker<
[hidden email]> wrote:
>> ... that cannot be, it's a macbook pro and a mac pro with that
>> behaviour.
>>
>> I thought that something is wrong with the application ImageJ64, in
>> combination with the new java update! I am not a java expert, but
>> something
>> with the stub (?) seems not to be in order!
>>
>> Regards
>> Karsten
>>
>> Am 16.06.2009 um 12:43 schrieb Johannes Schindelin:
>>
>>> Hi,
>>>
>>> On Tue, 16 Jun 2009, Karsten Rodenacker wrote:
>>>
>>>> I have some Problems with ImageJ64. It will not start anymore
>>>> after the
>>>> Java
>>>> Update 4!
>>>> Konsole messages are
>>>> 16.06.09 10:18:48 [0x0-0x1d39d38].gov.nih.info.rsb.ImageJ[18842]
>>>> [JavaAppLauncher Warning] Java application launched from PPC or
>>>> bad stub.
>>>> Relaunching in 32-bit, and tagging sub-processes to prefer 32-bit
>>>> with
>>>> $JAVA_ARCH=i386.
>>>
>>> You seem to have a 64-bit PowerPC. Apple does not support Java
>>> 1.6 on
>>> that machine, and apparently the launcher you are using tries to
>>> force
>>> running in 32-bit, although it assumes that you have an Intel
>>> processor.
>>>
>>> Sorry, I have no immediate fix, and unfortunately Fiji shares the
>>> same
>>> problem at the moment. Fortunately I got ahold of such a machine,
>>> and I
>>> will work on this issue this week.
>>>
>>> Ciao,
>>> Dscho
>>
>> Karsten
>>
[hidden email]
>>