I use a MacBook Pro with a 2.6 GHz intel Core 2 Duo processor and 4 GB 667 mHz DDR2 SDRAM. I just upgraded my operating system to Snow Leopard (OSX v10.6), and then did the upgrade to v10.6.2. I downloaded ImageJ 1.42, and find that it will not run (the microscope icon in the dock just bounces once, and the program will not start). I even downloaded and installed the JavaFor MacOSX.6Update1. It still would not open. Is there a fix for this problem? I would appreciate any help to resolve this. Thanks in advance!
Tom Hering Thomas M. Hering, Ph.D. Visiting Associate Professor of Orthopedic Surgery Department of Orthopedic Surgery School of Medicine Washington University in St. Louis St. Louis, MO 63110 The materials in this email are private and may contain Protected Health Information. If you are not the intended recipient be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via return email. |
Hello Dr. Hering,
On December 8, 2009 01:44:37 pm Hering, Thomas wrote: > I use a MacBook Pro with a 2.6 GHz intel Core 2 Duo processor and 4 GB 667 > mHz DDR2 SDRAM. I just upgraded my operating system to Snow Leopard (OSX > v10.6), and then did the upgrade to v10.6.2. I downloaded ImageJ 1.42, > and find that it will not run (the microscope icon in the dock just > bounces once, and the program will not start). I even downloaded and > installed the JavaFor MacOSX.6Update1. It still would not open. Is there a > fix for this problem? I would appreciate any help to resolve this. Thanks > in advance! Probably some kind of Java version mismatch, but... Try starting the application from Terminal and see what errors get spit out by the JVM. Instructions are on the ImageJ install page for Mac OS X. Instruction there is wrong though: Not: java -jar -mx256m ij.jar but: java -jar -Xmx256m ij.jar Also, try using: java -jar -Xms64m -Xmx256m ij.jar or similar instead -Xmx option specifies maximum memory allowed for application heap -Xms option specifies starting memory allocated to application from alloted heap and speeds up the program on startup (default memory on OS X is quite low without this approx. 2-4MB). Note -Xms must be =< -Xmx. Report what you see. Also check Java version or preferences set up (in Applications > Utilites > Java Preferences of Finder) for a mismatch. Check Java version in Terminal with: java -version. I am surprised there is no .dmg and .app for this on OS X. I can make one, but have not tried this on our Mac yet (Leopard). I will check it out. Best regards, Raymond Martin |
Hi Raymond,
Sorry for the delay in my reply. I tried what you suggested, and have copied the terminal session below: the response was "Unable to access jarfile ij.jar" Last login: Mon Dec 7 18:31:30 on ttys000 mightymac4-3-local-3:~ Tom$ java -jar -Xmx256m ij.jar Unable to access jarfile ij.jar mightymac4-3-local-3:~ Tom$ java -jar -Xms64m -Xmx256m ij.jar Unable to access jarfile ij.jar mightymac4-3-local-3:~ Tom$ Thomas M. Hering, Ph.D. Visiting Associate Professor of Orthopedic Surgery Department of Orthopedic Surgery School of Medicine Washington University in St. Louis St. Louis, MO 63110 ________________________________________ From: ImageJ Interest Group [[hidden email]] On Behalf Of Raymond Martin [[hidden email]] Sent: Tuesday, December 08, 2009 2:47 PM To: [hidden email] Subject: Re: ImageJ 1.42 won't start in Mac OSX, v 10.6.2 Hello Dr. Hering, On December 8, 2009 01:44:37 pm Hering, Thomas wrote: > I use a MacBook Pro with a 2.6 GHz intel Core 2 Duo processor and 4 GB 667 > mHz DDR2 SDRAM. I just upgraded my operating system to Snow Leopard (OSX > v10.6), and then did the upgrade to v10.6.2. I downloaded ImageJ 1.42, > and find that it will not run (the microscope icon in the dock just > bounces once, and the program will not start). I even downloaded and > installed the JavaFor MacOSX.6Update1. It still would not open. Is there a > fix for this problem? I would appreciate any help to resolve this. Thanks > in advance! Probably some kind of Java version mismatch, but... Try starting the application from Terminal and see what errors get spit out by the JVM. Instructions are on the ImageJ install page for Mac OS X. Instruction there is wrong though: Not: java -jar -mx256m ij.jar but: java -jar -Xmx256m ij.jar Also, try using: java -jar -Xms64m -Xmx256m ij.jar or similar instead -Xmx option specifies maximum memory allowed for application heap -Xms option specifies starting memory allocated to application from alloted heap and speeds up the program on startup (default memory on OS X is quite low without this approx. 2-4MB). Note -Xms must be =< -Xmx. Report what you see. Also check Java version or preferences set up (in Applications > Utilites > Java Preferences of Finder) for a mismatch. Check Java version in Terminal with: java -version. I am surprised there is no .dmg and .app for this on OS X. I can make one, but have not tried this on our Mac yet (Leopard). I will check it out. Best regards, Raymond Martin The materials in this email are private and may contain Protected Health Information. If you are not the intended recipient be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via return email. |
I am using ImageJ on Snow Leopard.
This message "Unable to access jarfile ij.jar" comes if ij.jar is not in the place you look for. cd to the place where ij.jar is located! e.g. cd /Applications/ImageJ Regards Karsten Am 09.12.2009 um 18:00 schrieb Hering, Thomas: > Hi Raymond, > > Sorry for the delay in my reply. I tried what you suggested, and have copied the terminal session below: the response was "Unable to access jarfile ij.jar" > > Last login: Mon Dec 7 18:31:30 on ttys000 > mightymac4-3-local-3:~ Tom$ java -jar -Xmx256m ij.jar > Unable to access jarfile ij.jar > mightymac4-3-local-3:~ Tom$ java -jar -Xms64m -Xmx256m ij.jar > Unable to access jarfile ij.jar > mightymac4-3-local-3:~ Tom$ > > > Thomas M. Hering, Ph.D. > Visiting Associate Professor of Orthopedic Surgery > Department of Orthopedic Surgery > School of Medicine > Washington University in St. Louis > St. Louis, MO 63110 > > ________________________________________ > From: ImageJ Interest Group [[hidden email]] On Behalf Of Raymond Martin [[hidden email]] > Sent: Tuesday, December 08, 2009 2:47 PM > To: [hidden email] > Subject: Re: ImageJ 1.42 won't start in Mac OSX, v 10.6.2 > > Hello Dr. Hering, > > On December 8, 2009 01:44:37 pm Hering, Thomas wrote: >> I use a MacBook Pro with a 2.6 GHz intel Core 2 Duo processor and 4 GB 667 >> mHz DDR2 SDRAM. I just upgraded my operating system to Snow Leopard (OSX >> v10.6), and then did the upgrade to v10.6.2. I downloaded ImageJ 1.42, >> and find that it will not run (the microscope icon in the dock just >> bounces once, and the program will not start). I even downloaded and >> installed the JavaFor MacOSX.6Update1. It still would not open. Is there a >> fix for this problem? I would appreciate any help to resolve this. Thanks >> in advance! > > Probably some kind of Java version mismatch, but... > > Try starting the application from Terminal and see what errors get spit out > by the JVM. Instructions are on the ImageJ install page for Mac OS X. > Instruction there is wrong though: > > Not: java -jar -mx256m ij.jar > > but: java -jar -Xmx256m ij.jar > > Also, try using: java -jar -Xms64m -Xmx256m ij.jar or similar instead > > -Xmx option specifies maximum memory allowed for application heap > -Xms option specifies starting memory allocated to application from alloted > heap and speeds up the program on startup (default memory on OS X is quite low > without this approx. 2-4MB). Note -Xms must be =< -Xmx. > > Report what you see. > > Also check Java version or preferences set up (in Applications > Utilites > > Java Preferences of Finder) for a mismatch. Check Java version in Terminal > with: java -version. > > I am surprised there is no .dmg and .app for this on OS X. I can make one, > but have not tried this on our Mac yet (Leopard). I will check it out. > > Best regards, > > Raymond Martin > > The materials in this email are private and may contain Protected Health Information. If you are not the intended recipient be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via return email. Karsten [hidden email] |
Are these problems with 32-bit or 64-bit?
ImageJ 64-bit runs within an admin account, but only the 32-bit version will run if logged in as a user. So far, changing permissions on the 64-bit ImageJ for non-admin user accounts has not resolved the problem. I've tried on 3 different Intel Macs with OS10.6.2, some with Java 1.6.0_17. Has anyone else encountered this, or solved it? Thanks, Glen Glen MacDonald Core for Communication Research Virginia Merrill Bloedel Hearing Research Center Box 357923 University of Washington Seattle, WA 98195-7923 USA (206) 616-4156 [hidden email] On Dec 9, 2009, at 12:13 PM, Karsten Rodenacker wrote: > I am using ImageJ on Snow Leopard. > This message "Unable to access jarfile ij.jar" comes if ij.jar is not in the place you look for. > cd to the place where ij.jar is located! > e.g. > cd /Applications/ImageJ > > Regards > Karsten > > Am 09.12.2009 um 18:00 schrieb Hering, Thomas: > >> Hi Raymond, >> >> Sorry for the delay in my reply. I tried what you suggested, and have copied the terminal session below: the response was "Unable to access jarfile ij.jar" >> >> Last login: Mon Dec 7 18:31:30 on ttys000 >> mightymac4-3-local-3:~ Tom$ java -jar -Xmx256m ij.jar >> Unable to access jarfile ij.jar >> mightymac4-3-local-3:~ Tom$ java -jar -Xms64m -Xmx256m ij.jar >> Unable to access jarfile ij.jar >> mightymac4-3-local-3:~ Tom$ >> >> >> Thomas M. Hering, Ph.D. >> Visiting Associate Professor of Orthopedic Surgery >> Department of Orthopedic Surgery >> School of Medicine >> Washington University in St. Louis >> St. Louis, MO 63110 >> >> ________________________________________ >> From: ImageJ Interest Group [[hidden email]] On Behalf Of Raymond Martin [[hidden email]] >> Sent: Tuesday, December 08, 2009 2:47 PM >> To: [hidden email] >> Subject: Re: ImageJ 1.42 won't start in Mac OSX, v 10.6.2 >> >> Hello Dr. Hering, >> >> On December 8, 2009 01:44:37 pm Hering, Thomas wrote: >>> I use a MacBook Pro with a 2.6 GHz intel Core 2 Duo processor and 4 GB 667 >>> mHz DDR2 SDRAM. I just upgraded my operating system to Snow Leopard (OSX >>> v10.6), and then did the upgrade to v10.6.2. I downloaded ImageJ 1.42, >>> and find that it will not run (the microscope icon in the dock just >>> bounces once, and the program will not start). I even downloaded and >>> installed the JavaFor MacOSX.6Update1. It still would not open. Is there a >>> fix for this problem? I would appreciate any help to resolve this. Thanks >>> in advance! >> >> Probably some kind of Java version mismatch, but... >> >> Try starting the application from Terminal and see what errors get spit out >> by the JVM. Instructions are on the ImageJ install page for Mac OS X. >> Instruction there is wrong though: >> >> Not: java -jar -mx256m ij.jar >> >> but: java -jar -Xmx256m ij.jar >> >> Also, try using: java -jar -Xms64m -Xmx256m ij.jar or similar instead >> >> -Xmx option specifies maximum memory allowed for application heap >> -Xms option specifies starting memory allocated to application from alloted >> heap and speeds up the program on startup (default memory on OS X is quite low >> without this approx. 2-4MB). Note -Xms must be =< -Xmx. >> >> Report what you see. >> >> Also check Java version or preferences set up (in Applications > Utilites > >> Java Preferences of Finder) for a mismatch. Check Java version in Terminal >> with: java -version. >> >> I am surprised there is no .dmg and .app for this on OS X. I can make one, >> but have not tried this on our Mac yet (Leopard). I will check it out. >> >> Best regards, >> >> Raymond Martin >> >> The materials in this email are private and may contain Protected Health Information. If you are not the intended recipient be advised that any unauthorized use, disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via return email. > > Karsten > [hidden email] |
On Dec 9, 2009, at 4:05 PM, Glen MacDonald wrote:
> Are these problems with 32-bit or 64-bit? > > ImageJ 64-bit runs within an admin account, but only the 32-bit version will run if logged in as a user. So far, changing permissions on the 64-bit ImageJ for non-admin user accounts has not resolved the problem. > > I've tried on 3 different Intel Macs with OS10.6.2, some with Java 1.6.0_17. Has anyone else encountered this, or solved it? This problem is fixed in the OS X version of ImageJ 1.42 now available on the ImageJ download page. The permissions for the ImageJ64 application did not allow a user without admin privileges to run it when Image was installed in the /Applications folder. -wayne |
In reply to this post by Glen MacDonald-2
Hi,
> Are these problems with 32-bit or 64-bit? > > ImageJ 64-bit runs within an admin account, but only the 32-bit version > will run if logged in as a user. So far, changing permissions on the > 64-bit ImageJ for non-admin user accounts has not resolved the problem. > > I've tried on 3 different Intel Macs with OS10.6.2, some with Java > 1.6.0_17. Has anyone else encountered this, or solved it? As an aside, I downloaded and tried the OS X version today and had no problems with either 32 or 64-bit. 64-bit seemed to start a little slower, but that was it. The thing is that I did not move these to Applications, I just ran them from their decompressed folder. So if you do not have an overwhelming need for the application to be system wide try it from a User folder instead. Cheers, Raymond |
As Wayne mentioned a couple of hours ago, a permissions issue with the 64-bit version has been fixed. I didn't try running the earlier version without dropping them into the Apps folder. these were on multi-user workstations where system wide installations are convenient. But, I will try that if the problem pops up again
thanks, Glen On Dec 9, 2009, at 8:30 PM, Raymond Martin wrote: > Hi, > >> Are these problems with 32-bit or 64-bit? >> >> ImageJ 64-bit runs within an admin account, but only the 32-bit version >> will run if logged in as a user. So far, changing permissions on the >> 64-bit ImageJ for non-admin user accounts has not resolved the problem. >> >> I've tried on 3 different Intel Macs with OS10.6.2, some with Java >> 1.6.0_17. Has anyone else encountered this, or solved it? > > As an aside, I downloaded and tried the OS X version today and had no problems > with either 32 or 64-bit. 64-bit seemed to start a little slower, but that was > it. The thing is that I did not move these to Applications, I just ran them > from their decompressed folder. So if you do not have an overwhelming need for > the application to be system wide try it from a User folder instead. > > Cheers, > > Raymond |
In reply to this post by Glen MacDonald-2
Hi,
Previously I mentioned that there was no .dmg for OS X and Wayne you stated that there was a need for an image to instruct users on what to do with it once open. I think you have mixed .dmg up with .pkg. .dmg is merely a disk image, not an installation medium. .pkg is used to install applications on OS X and these are often come inside .dmg. Thus .dmg is very similar to the available tar.gz and is what Mac users usually expect to download if there is no .pkg. Just add a readme, install or other texts in that to explain. When a Mac user downloads a tar.gz or other it does not necessarily open all the way (tar.gz becomes .tar), but a .dmg will open and mount for easier use. So how about it? Raymond |
In reply to this post by Hering, Thomas
> Previously I mentioned that there was no .dmg for OS X and
> Wayne you stated that there was a need for an image to > instruct users on what to do with it once open. I think you > have mixed .dmg up with .pkg. .dmg is merely a disk image, > not an installation medium. .pkg is used to install > applications on OS X and these are often come inside .dmg. > > Thus .dmg is very similar to the available tar.gz and is > what Mac users usually expect to download if there is no > .pkg. Just add a readme, install or other texts in that to > explain. When a Mac user downloads a tar.gz or other it does > not necessarily open all the way (tar.gz becomes .tar), but > a .dmg will open and mount for easier use. > > So how about it? The OS X version of ImageJ is now distributed as .zip file. The problem with using a .dmg file is that the user ends up with a copy of the ImageJ folder inside a read-only disk image, and some users do not realize that the ImageJ folder needs to be copied somewhere else. A readme file is not a good solution. -wayne |
Free forum by Nabble | Edit this page |