None of my .jar files will open (most importantly the dimsum.jar which I use almost everyday). I have run a clean up of my cache and tried everything I can think of to bring back the .jar operations and nothing works as it did before. My console Messages consist of a huge list of font names something like ([0x0-0x233233].com.apple.JarLauncher[1561] Type: TONES Name: ZoobeSSK-BoldItalic)and I get a loading screen that never leads to the main program. Can anyone suggest a solution?
17" MacBook Pro, 2.4GHz Intel, 3GB SDRAM,
Mac OS X (10.5.6),
http://www.mandarintools.com/download/DimSum.jar
I had this problem before and I simply rearranged my Java preferences so the 32-bit J2SE 5.0 was at the top of the list and it worked out but this time the solution didn't work. Right now my Java Applications list order is like this
J2SE 5.0 32-bit
Java SE 6 64-bit
J2SE 1.4.2 32-bit
J2SE 5.0 64-bit
Well, just an update, and being that I am not a developer, I thought maybe I could skirt the problem by changing my .jar file into an .app and skip the Java console all together. So I DL'd jarbundler which it turns out is also a .jar file and it won't open either. Here is the Console message if this helps:
10-1-28 上午07:34:44 [0x0-0x503503].com.apple.JarLauncher[3309] SystemFlippers: didn't consume all data for long ID 0 (pBase = 0x100142770, p = 0x100142774, pEnd = 0x100142778)
10-1-28 上午07:34:44 [0x0-0x503503].com.apple.JarLauncher[3309] SystemFlippers: didn't consume all data for long ID 0 (pBase = 0x10012d530, p = 0x10012d534, pEnd = 0x10012d538)
10-1-28 上午07:34:44 [0x0-0x503503].com.apple.JarLauncher[3309] Failed to load Main-Class manifest attribute from
10-1-28 上午07:34:44 [0x0-0x503503].com.apple.JarLauncher[3309] /Users/XIV/Desktop/jarbundler-2.1.0/jarbundler-2.1.0.jar
I have the same problem on my 2006 intel macbook pro with 10.5.8
I found that it depends on what folder the .jar file resides in. If I download a new one, it will run from within the Downloads folder, or from within the main Hard drive folder, but not if I bury it far into one of my user subfolders. That might be a clue.