Ooh, it didn't like that. I replaced the contents of the jre directory in c:\program files\jemplode 2.0 with the stuff from the jre directory in the 1.4 installation. Running the executable caused it to not even start. It pops up a dialog saying it couldn't load jvm.dl. I didn't pursue that avenue any farther.

I suppose if I knew a little more, I could leave my installation intact and just modify the jemplode.lax file to point to the right VM. I think I'll just stick with double clicking the jar file directly, though, which presumably is launching the 1.4 VM.

One other question: On my Mac OS X machine, I can't double-click the jar file directly. Presumably, there's no identifiable main class for the OS to launch it with. Is it worth it for you to modify the jar to make it that much easier to run in OS X? Or, is it already too easy to grab your .app file or build your own with MRJAppBuilder?

Really? This is a recent problem then, because I used to run it like this on my OS X box all the time ... In the meantime, you can grab the OS X wrapper that is on jempeg.org and just replace jemplode20.jar inside the app bundle (it's in something like /Resources/Java or something inside the bundle)

Mike

Double clicking on the JAR works fine on my OS X machine! I do have the develper tools installed - don't know if that would make a difference

Are you running the latest OS X with the Java update?

Okay, I haven't tried it recently, and my PowerBook is currently somewhere in transit to be repaired. So, I withdraw all of my comments until such time as I can actually test it again on my machine and make sure I wasn't high.