Bug 173 : processing 93 won't play sketches
Last modified: 2005-10-16 10:15




Status:
RESOLVED
Resolution:
DUPLICATE of bug 171
Priority:
P2
Severity:
normal

 

Reporter:
st33d
Assigned To:
fry

Attachment Type Created Size Actions

Description:   Opened: 2005-10-14 12:41
Even if the code area is blank I get the following error:

C:/DOCUME~1/Aaron/LOCALS~1/Temp/build/Temporary_9895_8835.java:0:0:0:0:
Semantic Error: The input file
"Files/Java/j2re1.4.2_03/lib/ext/QTJava.zipC:/processing-0093-expert/lib;C:/processing-0093-expert/lib/build;C:/processing-0093-expert/lib/pde.jar;C:/processing-0093-expert/lib/core.jar;C:/processing-0093-expert/lib/mrj.jar;C:/processing-0093-expert/lib/oro.jar;C:/processing-0093-expert/lib/registry.jar;C:/processing-0093-expert/lib/antlr.jar;"
does not have the ".java" extension.

This happens whenever I attempt to run any type of sketch whatsoever.

I downloaded 93 - expert for Windows. I moved the folder from E: to C:, no
change.

There also seemed to be an issue with it letting me select the text, it
flickered on and off.
Additional Comment #1 From fry 2005-10-14 12:49
what do your PATH and CLASSPATH variables look like?
Additional Comment #2 From fry 2005-10-14 15:02
also, what's your QTJAVA variable look like? any funny characters in there?
i'm confused about why there's no semicolon after qtjava.zip in the error
message that you posted above.

also, just to make sure, is this new for 93 or does 92 also have trouble?
Additional Comment #3 From st33d 2005-10-15 06:02
I added semicolons to the environment variables - that didn't work. The
error now had semicolons in. I noticed I had several J2SEs lurking on my
hard-drive because I thought an update would be, well, an update - not an
entirely new bag. I ripped off everything to do with Java and reinstalled.
Still didn't work. I deleted the Quick-time for Java environment variables,
ripped out Quick-time and re-installed (checking QT-Java of course). Joy.

Funny-thing is that the previous versions didn't care about the mess on my
machine. 92 included. It's no longer an imediate problem though. My guess
is that QT-Java doesn't update the environment variables whereas the Java
path is udpated with each new install of J2SE. 93 must be sensitive to this.

It is still almost impossible to select text in the output area. It
requires some sharp caffeine honed reflexes.
Additional Comment #4 From fry 2005-10-15 08:18
again, what's in your PATH, CLASSPATH, and QTJAVA environment variables? i
need to be able to track this down.

for the selection stuff, could you start a new bug for that one? that's
gonna be something completely unrelated, unfortunately.
Additional Comment #5 From st33d 2005-10-15 09:23
Current JAVA_PATH:

C:\Program Files\Java\jre1.5.0_04;

There is no longer a QTJAVA path. I assumed it would write a new one and it
hasn't. Processing and video capture still works. I search my whole machine
for QTJava.zip and I found it here:

C:\WINDOWS\system32

I have tried entering bogus environment variables for CLASSPATH and QTJAVA
but no version of Processing cares.

I think the QTJAVA path may have been

Files/Java/j2re1.4.2_03/lib/ext/QTJava.zip

before I deleted the environment variable and reinstalled Quicktime (6).

I'm sorry I can't offer any specifics, I have wiped most of the contrary
data from the system. I also deleted CLASSPATH before reinstalling and that
seems to have made no difference either.
Additional Comment #6 From fry 2005-10-15 09:41
what do you mean by processing and video capture still works? just that you
can launch processing, and that a separate video capture app also works?

i still need to know your PATH (not JAVA_PATH, just PATH)..
Additional Comment #7 From fry 2005-10-15 09:43
also, are you using run.bat?
Additional Comment #8 From st33d 2005-10-15 16:11
I'm not using run.bat as far as I know. I'm using the shortcut. Assume I
know very little about Java. This is the case.

Under user variables for Aaron (my computer name): PATH

C:\mcc18\mpasm;C:\mcc18\bin;;C:\PICCLITE\BIN;C:\PICCLITE\BIN;C:\PICCLITE\BIN

System variables: Path

C:\Program Files\Microchip\MPLAB
C30\bin;C:\mcc18\mpasm;C:\mcc18\bin;C:\Perl\bin\;C:\PROGRA~1\Borland\CBUILD~1\Projects\Bpl;C:\PROGRA~1\Borland\CBUILD~1\Bin;C:\djgpp\BIN;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program
Files\Common Files\Roxio Shared\DLLShared;C:\mcc\bin;C:\Program
Files\Common Files\Adobe\AGL

I activated the video capture and movie capture inside Processing.

Assume my priority in understanding the machine I'm working with is from
within Processing. When I test things, I use Processing to do so. It is the
scope of my understanding.

There appears to be no other Java related variables under the environment
settings. I'm sorry I'm unable to be more concise. If encounter a hiccup
again I will keep a more thorough record. If a similar problem occurs
please contact me, I will try to reproduce the error to localize the bug.
Additional Comment #9 From fry 2005-10-16 07:42
hm, could you copy and paste the error message that you get now that you've
reinstalled java and quicktime?

i've logged bug #180 which covers the console selection issue. i'll see if
i can get that fixed for 94.
Additional Comment #10 From st33d 2005-10-16 09:30
Sorry I didn't make this clear: All versions of Processing are working
without any error in running sketches after the re-install of Java and
Quicktime.

I inferred this using a three letter word at the end of the first paragraph
on comment #3. I imagine that might have been pretty vague.

For the time being the problem has vanished. 93 works fine (minus selecting
console text, but I'll live).

I'm unsure how to recreate the bug. Suffice to say I'm pretty certain it
was down to having multiple J2SEs installed, QTJava looks like it was
defaulting to a J2SE that was older (1.4.2_03) than what JAVA_PATH was
using (1.5.0_02). Now that I've removed any source of confusion there no
longer seems to be a problem.
Additional Comment #11 From fry 2005-10-16 10:15
ah, ok.. i'll close this and mark it as a duplicate of the other
qtjava/windows stuff

*** This bug has been marked as a duplicate of 171 ***