Could you add "." to the PATH and test again?

(In reply to comment #0)
> Tried to run the Win32 version on XP SP2 and it won't launch (ver 10/16/2008).
> I get a flash of a window, too fast to see anything...then nothing. 
> If I run the fiji exe from a command window I get
> N:\Fiji.app>Could not find fiji-win32.exe in PATH
> The ij.jar runs from my other Java installs but the plugins etc fail because of
> version differences.
> Windows XP Pro Version 2002 Service Pack 2 (Large Corporate Enterprise
> install!)
> AMD Opteron Dual Processor 250 2.4GHz 4 Gig Ram

(In reply to comment #1)
> Could you add "." to the PATH and test again?

Tried to add both . and .\ to PATH but no better luck from ether the direct double click exe run or from the command line

I moved to the directory where the app is and executed .\fiji-win32.exe and got this warning but no action from command line.

N:\Fiji_app>Warning: falling back to System JVM

I am seeing the same behavior on my laptop (Same corporate enterprise install of Win XP) will try on my home computer too.

Oh! That helps a lot. It means that Fiji cannot find the bundled Java Runtime.  Could you run "fiji-win32 --dry-run" and post the output, please?

(In reply to comment #3)
> Oh! That helps a lot. It means that Fiji cannot find the bundled Java Runtime. 
> Could you run "fiji-win32 --dry-run" and post the output, please?

Sorry for all the line breaks this is how it came out of the command window...I tried it on my home computer and it launched fine...hmmmm. I noticed that Fiji attempts to access the internet and act as a server during launch on my home computer (detected by ZoneAlarm), could our corporate firewall be causing problems?? There are also a number of security apps running in the background to prevent mischievious programs from having fun. ImageJ has always worked fine though.

N:\Fiji_app>.\fiji-win32.exe --dry-run

N:\Fiji_app>java -Dpython.cachedir.skip=false -Djava.class.path=N:\\Fiji_app/mis
c/Fiji.jar;N:\\Fiji_app/ij.jar;N:\\Fiji_app/plugins/3D_Distance_Transform.jar;N:
\\Fiji_app/plugins/Analyze_Reader_Writer.jar;N:\\Fiji_app/plugins/BeanShell_Inte
rpreter.jar;N:\\Fiji_app/plugins/bUnwarpJ_.jar;N:\\Fiji_app/plugins/CLI_.jar;N:\
\Fiji_app/plugins/Clojure_Interpreter.jar;N:\\Fiji_app/plugins/Color_Histogram.j
ar;N:\\Fiji_app/plugins/Color_Inspector_3D.jar;N:\\Fiji_app/plugins/Daltonize_.j
ar;N:\\Fiji_app/plugins/Fiji_Updater.jar;N:\\Fiji_app/plugins/ij-ImageIO_.jar;N:
\\Fiji_app/plugins/IJ_Robot.jar;N:\\Fiji_app/plugins/Image_5D.jar;N:\\Fiji_app/p
lugins/Interactive_3D_Surface_Plot.jar;N:\\Fiji_app/plugins/IO_.jar;N:\\Fiji_app
/plugins/Javascript_.jar;N:\\Fiji_app/plugins/JRuby_Interpreter.jar;N:\\Fiji_app
/plugins/Jython_Interpreter.jar;N:\\Fiji_app/plugins/lens_correction.jar;N:\\Fij
i_app/plugins/level_sets.jar;N:\\Fiji_app/plugins/loci_tools.jar;N:\\Fiji_app/pl
ugins/LSM_Toolbox.jar;N:\\Fiji_app/plugins/mpicbg_.jar;N:\\Fiji_app/plugins/Mult
i_Thresholder.jar;N:\\Fiji_app/plugins/M_I_P.jar;N:\\Fiji_app/plugins/register_v
irtual_stack_slices.jar;N:\\Fiji_app/plugins/registration_3d.jar;N:\\Fiji_app/pl
ugins/SplineDeformationGenerator_.jar;N:\\Fiji_app/plugins/Stitching_.jar;N:\\Fi
ji_app/plugins/TrakEM2_.jar;N:\\Fiji_app/plugins/TransformJ_.jar;N:\\Fiji_app/pl
ugins/VIB_.jar;N:\\Fiji_app/plugins/View5D_.jar;N:\\Fiji_app/plugins/Volume_View
er.jar;N:\\Fiji_app/jars/bsh-2.0b4.jar;N:\\Fiji_app/jars/clibwrapper_jiio.jar;N:
\\Fiji_app/jars/clojure.jar;N:\\Fiji_app/jars/edu_mines_jtk.jar;N:\\Fiji_app/jar
s/imagescience.jar;N:\\Fiji_app/jars/itext-1.3.jar;N:\\Fiji_app/jars/jai_codec.j
ar;N:\\Fiji_app/jars/jai_core.jar;N:\\Fiji_app/jars/Jama-1.0.2.jar;N:\\Fiji_app/
jars/javac.jar;N:\\Fiji_app/jars/jcommon-1.0.12.jar;N:\\Fiji_app/jars/jfreechart
-1.0.9.jar;N:\\Fiji_app/jars/jpedalSTD.jar;N:\\Fiji_app/jars/jruby.jar;N:\\Fiji_
app/jars/js.jar;N:\\Fiji_app/jars/jython2.2.1/jython.jar;N:\\Fiji_app/jars/jzlib
-1.0.7.jar;N:\\Fiji_app/jars/postgresql-8.2-506.jdbc3.jar;N:\\Fiji_app/jars/Quic
k3dApplet-1.0.8.jar -Dplugins.dir=N:\\Fiji_app -Xmx1536m ij.ImageJ -icon=N:\\Fij
i_app/images/icon.png -title=Fiji

Okay, I finally figured out that my analysis was totally off.  Took some time, too.

Actually, what happens is this: due to Windows' limitations, it is not always possible to allocate 3/4 of the computer's RAM as heap, and in those cases, Fiji cannot create a virtual machine.

However, Fiji mistook this as a sign that something was wrong with the Java installation, and fell back to calling the default Java of the system.

Unfortunately, this caused
- the error message to be killed right away, together with the console window,
- no error message from the default java, since it was also called as a console process.

The issue should be fixed now (we detect an out-of-memory condition, and handle it more sensibly).  Could you please test again by fetching

http://pacific.mpi-cbg.de/downloads/snapshots/fiji-win32.exe

and running it after dropping it into the Fiji.app folder?

Thank you very much.

Looks like thats got it...worked fine with new exe...thanks!

(In reply to comment #5)
> Okay, I finally figured out that my analysis was totally off.  Took some time,
> too.
> Actually, what happens is this: due to Windows' limitations, it is not always
> possible to allocate 3/4 of the computer's RAM as heap, and in those cases,
> Fiji cannot create a virtual machine.
> However, Fiji mistook this as a sign that something was wrong with the Java
> installation, and fell back to calling the default Java of the system.
> Unfortunately, this caused
> - the error message to be killed right away, together with the console window,
> - no error message from the default java, since it was also called as a console
> process.
> The issue should be fixed now (we detect an out-of-memory condition, and handle
> it more sensibly).  Could you please test again by fetching
> http://pacific.mpi-cbg.de/downloads/snapshots/fiji-win32.exe
> and running it after dropping it into the Fiji.app folder?
> Thank you very much.