I've been following this discussion with interest because of my own frustration awhile back...
Since I rarely use jwd, Eric's suggestion of just moving on to j7 was ok - for me ... BUT, the machine I was frustrated about is soon to belong to someone else and I was hoping to leave a nice clean and stable version of J in the Application directory. So, when - On Nov 30, 2010, at 8:01 PM, Ian Clark wrote: >> try first locate a 32-bit java that works... > > On that score, try downloading and installing Mstat 5.4 from: > http://www.mcardle.wisc.edu/mstat/download/download.html > > It's a packaged j602 app (gratis), with its own bin/j.jar and bin/jwd. > The latter may have a few tricks you can study. I did download a copy of mstat, and it did run OK - (although the UI is more mysterious (to me) than the J IDE)... Looking at their equivalent to jwd (mstat) I found - LWiMac-6:bin jkt$ cat mstat #!/bin/sh osver=`sw_vers -productVersion` jopt=-d32 if [ "$osver" \< "10.5" ] then jopt='' fi cd "`dirname "$0"`/" java $jopt -Xss8000000 -Xdock:name=Mstat -Xdock:icon=mstat.png -jar j.jar -jprofile mstat.ijs --- and there, indeed, is the test using sw_vers that has been suggested in this thread. That could be co-opted into jwd and probably should be. But, back to my problem - I had already hacked jwd to have -d32 and it still didn't work. The failure reported by Murry Eisenberg, and happened to me too, was that "libjnative.jnlib failed" - and it continued to happen after I put in -d32 (hopefully that trick solved Murry's problem, but I didn't see a report from him saying that). So reading this current stuff, I dug a little deeper and discovered that these files in mstat - -rwxr-xr-x@ 1 jkt staff 2187036 Mar 4 09:09:46 2008 libj.dylib -rwxr-xr-x@ 1 jkt staff 18828 Mar 4 09:09:46 2008 libjnative.jnilib which are somewhat different than the ones in my j602 installation (that I put into this machine shortly after it was released) - they looked like: -rwxrwxrwx@ 1 jkt admin 1904524 Mar 4 08:35:02 2008 libj.dylib -rwxrwxrwx 1 jkt admin 15176 Mar 4 08:35:02 2008 libjnative.jnilib Then I downloaded a fresh copy of - J32 Mac Intel: j602a_mac_intel.dmg and it has binaries that match the mstat distribution - and (with the -d32 edit) they work on my machine. I don't know where my defective versions came from, and it seems quite strange that they are timestamped only a few minutes earlier than the good ones. But this was the problem I was having. Now the problem is solved - thanks for the discussion that motivated me to dig a little deeper... I think what happened is that in OS 10.6.5 Apple moved to Java 1.6 and there is no longer a separate 32 and 64 bit Java binary and the user is expected to use the -dxx parameter to override the default. It would seem worth the effort for jsoftware to update jwd in the download version of j602 by incorporating the version test above (or one similar) - it would be a minor effort/change for fixing a "bug" that will bite anyone trying to start using j in OS X :) - joey On Dec 5, 2010, at 5: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
