Hey Jonathan and Cornel, Yeah, this is part of the joy of Windows. Originally I didn't even have the installer set "apollo.vmoptions" but it wasn't working for certain Windows users so I had to explicitly set the memory (which is set to have a maximum of half the available memory on the installed computer). I guess you just can't win with Windows, as not having the memory set fails on some machines and having it set fails on others...
As for shared installations, in particular to *nix and OSX, launching $APOLLO_ROOT/bin/apollo will disregard "apollo.vmoptions" using the memory setting in the configuration. So you could just symlink to that script instead. However, you still run into the issue of making sure that the memory setting caters to the lowest common denominator. Cheers, Ed On Wed, 24 Jun 2009, Jonathan Crabtree wrote:
Cornel, Thanks, it's helpful to know that I'm not the only one who has seen this, and it suggests that it might be helpful to add a note to the Windows install instructions. Another -Xmx pitfall that I forgot to mention is that if you're installing Apollo on a shared volume for use by more than one machine, you have to be careful that you don't do the installation on a machine with more memory than the others that will be using it (or, if you do, you should subsequently lower -Xmx.) I did a shared Linux install a couple of days ago using one of our high-memory machines and then wasn't able to run it on a lower memory machine, due to the -Xmx setting, which only worked on the high-memory machine. Jonathan On Wed, Jun 24, 2009 at 10:33 AM, Ghiban, Cornel <[email protected]> wrote: HI all, This happened to me some time ago on a 32-bit XP with 3.5GB of RAM. I believe it was prior to v1.10. But removing or setting the -Xmx option to a lower value allowed me to start apollo. I hope it helps, Cornel ____________________________________________________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Crabtree Sent: Wednesday, June 24, 2009 10:26 AM To: Ed Lee Cc: [email protected] Subject: [apollo] 1.11.0 fails to run on 64 bit Vista Hi Ed, Here's another interesting fact about the 1.11.0 Apollo release, which is that neither version (bundled JRE + no bundled JRE) works on my 64-bit (AMD) Vista machine. The installation process runs fine but then when I try to start Apollo, either from the command-line or using the Windows Start menu, I get a dialog box that says it failed and something to the effect of "maybe an exception occurred in the main method." (I don't have the machine booted into Vista right now and I can't remember the exact text.) I discovered there's a simple workaround, which is to delete the apollo.vmoptions file in the main Apollo install directory; presumably the -Xmx setting was causing problems (even though it was set to way below the real memory size of the machine). Someone else here tried the install on a Windows XP machine and reported that it worked OK, and they didn't have to delete the apollo.vmoptions file. Anyway, you might want to add a note to the Windows install instructions to try removing apollo.vmoptions if it doesn't work out of the box (and I'd also be interested to hear if you're able to replicate the bug on another Vista machine.) Thanks, Jonathan
_______________________________________________ apollo mailing list [email protected] http://mail.fruitfly.org/mailman/listinfo/apollo
