This is occurring with PROCESSING 1.0.3 (REV 0165) under Vista Home Premium x64
Service Pack 1 with all updates and patches. Hardware is a bone stock Dell Inspiron
1545.

Using the debug flag to start processing provides the following information:


CmdLine: C:\Users\Bob\Downloads\processing-1.0.3\processing-
1.0.3\processing.exe --l4j-debug
WOW64: yes
Working dir: C:\Users\Bob\Downloads\processing-1.0.3\processing-1.0.3\.
Bundled JRE: java
Check launcher: C:\Users\Bob\Downloads\processing-1.0.3\processing-
1.0.3\java\bin\javaw.exe (n/a)
64-bit search: SOFTWARE\JavaSoft\Java Development Kit...
Match: SOFTWARE\JavaSoft\Java Development Kit\1.6
Match: SOFTWARE\JavaSoft\Java Development Kit\1.6.0_13
Using 64-bit runtime.
Check launcher: C:\Program Files\Java\jdk1.6.0_13\bin\javaw.exe (OK)
Add classpath: lib\pde.jar
Add classpath: lib\core.jar
Add classpath: lib\jna.jar
Add classpath: lib\ecj.jar
Add classpath: lib\antlr.jar
Launcher: C:\Program Files\Java\jdk1.6.0_13\bin\javaw.exe
Launcher args: -Xms128m -Xmx128m -classpath "lib;C:\Program
Files\Java\jdk1.6.0_13\lib\tools.jar;lib\pde.jar;lib\core.jar;lib\jna.jar;lib\ecj.jar;lib\antlr
.jar" processing.app.Base
Args length: 165/32768 chars
Exit code: 259

Here is the output of %QTJAVA%, %CLASSPATH% and %PATH%
C:\Users\Bob>echo %QTJAVA%
C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip

C:\Users\Bob>
C:\Users\Bob>echo %CLASSPATH%
.;C:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip

C:\Users\Bob>
C:\Users\Bob>echo %PATH%
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files
(x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Common
Files\Roxio Shared\10.0\DLLShared\;C:\Program Files (x86)\QuickTime\QTSystem\

hm, probably issues with x64.. will have to look into it.

I just noticed that some of the path references in the debug output are to items in
C:\Program Files\ while the %QTJAVA%, %CLASSPATH% and %PATH% entries refer to
C:\Program Files (x86)\. Is that causing problems?

very likely, though i'm not sure how Vista re-maps things.. i'll have to
get my hands on a copy of vista 64 (actually the 64-bit windows 7 rc should
probably work, i'll try that).

I tried the following:

"C:\Program Files\Java\jdk1.6.0_13\bin\java.exe" -Xms128m -Xmx128m -classpath
"lib;C:\Program
Files\Java\jdk1.6.0_13\lib\tools.jar;lib\pde.jar;lib\core.jar;lib\jna.jar;lib\ecj.jar;lib\antlr
.jar" processing.app.Base

to force the paths, and the splash screen now comes up! But I then receive an fatal
error message complaining about not being able to find theme.txt.

I don't know if this helps you or not, but there it is.

good to know, thanks, that's helpful. that certainly points to the path
issue being a problem. looks like we need to be smarter with how we read
some registry values.

Forgot one other thing - when I first forced the paths from the command line, I
received the following error:

Exception in thread "main" java.lang.UnsatisfiedLinkError: jnidispatch
(/com/sun/jna/win32-amd64/jnidispatch.dll) not found in resource path

which after some googling, got me to this:

https://jna.dev.java.net/issues/show_bug.cgi?id=59

"The win32-x86 DLL currently shipped in the JAR file won't work if running under
the 64-bit JVM on Windows XP or Vista. An alternative should be included to
make JNA work on this platform."

I downloaded JNA version 3.0.9 and replaced whatever was included in processing-
1.0.3. Then retrying the forced paths is when the splash screen appeared and the
theme.txt error message came up.