OK, I promise this is my last comment on this... I too have a PPC iMac - it runs j602 just fine using the PPC download.
The java problem with 10.6 (especially 10.6.5) is an issue ONLY on INTEL machines. And even there, it only became a thorny issue with 10.6.5 and the new level of java (1.6). What I would like to hear about is someone who can boot their INTEL Mac with 10.5 (or 10.4) and see if the -d32 parm in jwd works there. If it does, then I think it should be included in the INTEL j602 jwd - maybe the testing for what OS isn't needed, but I've seen no comment on that. This may well be, as William Shakespeare wrote, Much Adoe About Nothing ..... - joey On Dec 5, 2010, at 8:14 PM, Ian Clark wrote: > @Joey > >> don't worry about the PPC version (which will only run up to and including >> OS 10.5...) > > I fear that's the one we do have to worry about. A lot of people (my > daughter especially) are still running Macs purchased 2006 or earlier, > at which date Apple discontinued powerPC chips. Especially in > universities. These, at best, will be running 10.5 -- and will forever > be stuck at that level. > > See my last posting, to Bill. I'm proposing an easy general solution, > if Bill agrees. > > Ian > > > > On Mon, Dec 6, 2010 at 3:49 AM, Joey K Tuttle <[email protected]> wrote: >> Ian, >> >> As I previously pointed out - there is a separate download for Intel and PPC >> versions of J for OS X - has anyone experimented with -d32 in 10.5 and >> earlier?? I haven't seen any indication of that and it might well work just >> fine - again, don't worry about the PPC version (which will only run up to >> and including OS 10.5...) >> >> - joey >> >> >> On Dec 5, 2010, at 7:27 PM, Ian Clark wrote: >> >>> @Bill, >>> >>> You're right. >>> >>> And I think we'll need a separate if...fi for 10.5, 10.6 and 10.7. >>> Naive, but just too bad. (Easy to debug though). >>> >>> Lion (10.7), just announced, will only run on Intel chips. So it >>> should specify -d32 without exception. >>> 10.8 and beyond: j602 can expected to be obsolete and unsupported. >>> >>> Snow Leopard (10.6), what I've got, will only run on Intel chips, so >>> too it should specify -d32 without exception. >>> >>> Leopard (10.5) is the mischief. It was a transitional product and it >>> supported everything. It should only specify -d32 for Intel chips. I'd >>> hazard a guess: call: uname -m --and look for the last 2 digits = 86. >>> >>> I can test the 10.6 section triggers for my machine. We'll need >>> volunteers to test a script on other Macs. >>> >>> I'll compose a test-script and publish it on this list, plus >>> instructions how to run it. >>> >>> But really it's the java version that matters. Can we cut the Gordian >>> knot? Run java without -d32, look at the exit code, and if it's bad, >>> run it again, this time WITH -d32. >>> >>> Yet another strategy, the one I'd recommend... >>> >>> A pair of alternative icons would save all this fuss. No tricky logic >>> to debug. No doubt about how java was actually called on a user's >>> machine. If one doesn't run, the other might... >>> ++ j602.app (...the existing one, no changes to be made) >>> ++ j60232.app (...a new one resembling it, which I shall build and >>> ship to Bill). >>> >>> Ian >>> >>> >>> On Mon, Dec 6, 2010 at 1:15 AM, bill lam <[email protected]> wrote: >>>> May be a nested if statement to check both uname -m and sw_vers. >>>> >>>> Вск, 05 Дек 2010, Ian Clark писал(а): >>>>> Norman, Joey, >>>>> >>>>> This is basically what the MSTAT app does. >>>>> >>>>> Download Mstat 5.4 from: >>>>> http://www.mcardle.wisc.edu/mstat/download/download.html >>>>> >>>>> But I did a few experiments running Terminal and I've given myself >>>>> serious doubts as to whether that "if-fi" statement will behave itself >>>>> on all Macs. It works on my (modern) Mac, but all is not what it >>>>> seems. It may be working for the wrong reason. >>>>> >>>>> So, speaking for myself, I wouldn't (yet) recommend it as a universal >>>>> fix for the J602-for-Mac download. I'll need to do some more tests. >>>>> (But I defer to higher unix authorities). >>>>> >>>>> Bill and I will try to work something out. >>>>> >>>>> Ian >>>>> >>>>> >>>>> On Sun, Dec 5, 2010 at 5:39 PM, Norman Drinkwater >>>>> <[email protected]> wrote: >>>>>> On Intel OSX, the problem is that older versions are only 32-bit, while >>>>>> later ones have both 32- and 64-bit java. >>>>>> >>>>>> On an Intel Mac try this as the jwd script >>>>>> >>>>>> #!/bin/sh >>>>>> osver=`sw_vers -productVersion` >>>>>> jopt=-d32 >>>>>> if [ "$osver" \< "10.5" ] >>>>>> then >>>>>> jopt='' >>>>>> fi >>>>>> cd "`dirname "$0"`/.." >>>>>> java $jopt -Xss8000000 -Xdock:name=J -Xdock:icon=bin/icons/jred.icns >>>>>> -jar j.jar "$@" >>>>>> >>>>>> Note from the line starting with "java" down, all of the info should be >>>>>> on a single line. >>>>>> >>>>>> Norman >>>>>> >>>>>> On 12/5/2010 7:37 AM, Brian Schott wrote: >>>>>>> Ian et al, >>>>>>> >>>>>>> I just checked, and your concern is valid about going back before >>>>>>> non-intel Macs. When I altered the j602/bin/jwd to include `-d32` the >>>>>>> launch of J602 failed. So I guess an if...fi is required. Darn. >>>>>>> >>>>>>> On Sun, Dec 5, 2010 at 3:01 AM, Ian Clark<[email protected]> wrote: >>>>>>>> >>>>>>>> Might the -j32 flag actually be disruptive if you go back before >>>>>>>> 64-bit java was released? (10.5 was it?) Or on non-Intel Macs? >>>>>>>> >>>>>>>> Ian >>>>>>> >>>>>> ---------------------------------------------------------------------- >>>>>> For information about J forums see http://www.jsoftware.com/forums.htm >>>>>> >>>>> ---------------------------------------------------------------------- >>>>> For information about J forums see http://www.jsoftware.com/forums.htm >>>> >>>> -- >>>> regards, >>>> ==================================================== >>>> GPG key 1024D/4434BAB3 2008-08-24 >>>> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 >>>> ---------------------------------------------------------------------- >>>> For information about J forums see http://www.jsoftware.com/forums.htm >>> ---------------------------------------------------------------------- >>> For information about J forums see http://www.jsoftware.com/forums.htm >> >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
