Hi Once the newest 1.7 version is installed, it is difficult to start 32bit mode. In my case the following messages are output:
Air13:~ kamakura$ java -d32 -version Error: This Java instance does not support a 32-bit JVM. Please install the desired version. Toshinari Kamakura 2012/10/25 Peter B. Kessler <[email protected]> > (Oh boy, something I know about: Java versions and variants. :-) > > The "mixed mode" in the output of "java -version" means that the Java > HotSpot virtual machine runs Java code first by interpreting it, and then > by compiling the Java code that runs a lot (the hot spots). The variants > are: > > (1) the default configuration: a 64-bit Java virtual machine with an > interpreter and the "server" runtime compiler > > > $ java -version > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-10M3909) > > Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, mixed mode) > > Note the "64-bit", "Server VM", and "mixed mode" in the last line above. > > (2) with the interpreter only (slow, but small) > > $ java -Xint -version > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-10M3909) > Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, interpreted > mode) > > Note the "interpreted mode" in the last line above. > > (3) without the interpreter (really slow and bulky, because it generates > too much code; used only for testing the compiler) > > $ java -Xcomp -version > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-10M3909) > Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, compiled mode) > > Note the "compiled mode" in the last line above. > > Choosing 32-bit or 64-bit is a different set of options: -d32 or -d64. > The default is 64-bit Java virtual machine with the server runtime > compiler, as shown in (1) above. If you explicitly want a 32-bit JVM, you > can ask for it, though by default the 32-bit JVM uses the "client" runtime > compiler (in mixed mode) > > $ java -d32 -version > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-10M3909) > Java HotSpot(TM) Client VM (build 20.12-b01-434, mixed mode) > > Note the "-d32" on the command line, and the lack of "64-bit", and the > presence of "Client VM" in the last line above. > > If you want a 32-bit JVM with the "server" runtime compiler (in mixed > mode), you can ask for that explicitly > > $ java -d32 -server -version > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-10M3909) > Java HotSpot(TM) Server VM (build 20.12-b01-434, mixed mode) > > Note the "-d32" on the command line, and the lack of "64-Bit" in the last > line above. > > Yes, there are a lot of choices. We tried to make the default good for > most people, but made the others available because one size does not fit > all. I'm running "Snow Leopard", MacOS X 10.6. > > ... peter > > > Joey K Tuttle wrote: > >> I meant to reply to this too - I do run Mountain Lion, but normally only >> use j in a Terminal window (executing jconsole) - I tried that first and >> j602 started fine, but then I ran a verb I have defined - >> >> version =: 3 : 'JVERSION, (10{a.), (2!:0 ''sw_vers''), 2!:0 ''echo >> `java -version 2>&1`''' >> >> notice that it requests the version of Java available - that caused the >> system to reply: >> >> iMi7:~ jkt$ j6 >> version '' >> Installer: j602a_mac_intel.dmg >> Engine: j602/2008-03-03/16:45 >> Library: 6.02.023 >> ProductName: Mac OS X >> ProductVersion: 10.8.2 >> BuildVersion: 12C54 >> No Java runtime present, requesting install. >> >> Then a system dialog popped up and asked permission to download/install >> about 60 megabytes of Java material (presumably from Sun/Oracle). After >> that, the j602 IDE seemed to work fine. >> >> The root of this problem is that Apple has stopped distributing Java of >> any kind with Mountain Lion, also the "java preferences" application that >> was in Applications/Utilities is no longer a part of the system... >> >> The bit in my "version" verb that caused this sequence of events was >> "java -version" and here is an example of executing that (after the >> requested install described above) at a Terminal prompt: >> >> iMi7:~ jkt$ java -version >> java version "1.6.0_37" >> Java(TM) SE Runtime Environment (build 1.6.0_37-b06-434-11M3909) >> Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01-434, mixed mode) >> iMi7:~ jkt$ >> >> Perhaps the "mixed mode" attribute is what allows this Java to support >> the 32 bit j engine. In any case j602, both jconsole (in terminal) and >> j602.app, seem to work fine in OS X 10.8.2 when Java is installed. >> >> Hope this is helpful. >> >> - joey >> >> On 2012/10/23 17:08 , Ian Clark wrote: >> >>> Haven't installed Mountain Lion yet. But there's a list of ideas to try >>> here: >>> http://www.jsoftware.com/**jwiki/System/Installation/**J602/Mac/** >>> MacSnowLeopardInstallBug<http://www.jsoftware.com/jwiki/System/Installation/J602/Mac/MacSnowLeopardInstallBug> >>> >>> On Tue, Oct 23, 2012 at 12:13 AM, kamakura <[email protected]> >>> wrote: >>> >>>> Hi >>>> >>>> I sometimes use J602 version on MacOS Mountain Lion with Java >>>> Preferences setting 32bit CPU type precedence. However, recently Apple >>>> software update cut off Java Preferences application. So we cannot use >>>> 32bit CPU Java. I fail in starting J602 application with the following >>>> message: >>>> >>>> Load Library /Applications/j602/bin/**libjnative.jnilib failed. >>>> >>>> >>>> Does anyone know how to deal with this problem? >>>> >>>> >>>> >>>> +++++++++++++++++++++++++++++ >>>> Toshinari Kamakura >>>> >>>> Chuo University >>>> 1-13-27 Kasuga >>>> Bunkyo-ku >>>> Tokyo 112-8551, Japan >>>> ++++++++++++++++++++++++++++++ >>>> >>>> >>>> >>>> ------------------------------**------------------------------** >>>> ---------- >>>> For information about J forums see http://www.jsoftware.com/** >>>> forums.htm <http://www.jsoftware.com/forums.htm> >>>> >>> ------------------------------**------------------------------** >>> ---------- >>> For information about J forums see >>> http://www.jsoftware.com/**forums.htm<http://www.jsoftware.com/forums.htm> >>> >>> ------------------------------**------------------------------** >> ---------- >> For information about J forums see >> http://www.jsoftware.com/**forums.htm<http://www.jsoftware.com/forums.htm> >> > ------------------------------**------------------------------**---------- > For information about J forums see > http://www.jsoftware.com/**forums.htm<http://www.jsoftware.com/forums.htm> > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
