[4594] in java-interest
URGENT! Java.exe not using classpath on NT?
daemon@ATHENA.MIT.EDU (David LeBlanc)
Mon Jan 8 16:38:25 1996
Date: Mon, 8 Jan 1996 13:03:35 -0700
To: java-interest@java.Eng.Sun.COM
From: David LeBlanc <dleblanc@thinkertools.com>
Hi;
I've posted this TWICE before with NO response! Please, please HELP!
I have been unable to get *.class files to be executed in most cases on Win
NT 3.51 while using java.exe from the jdk2 release.
My environment is:
HOME=g:\usr\users\davel (contains .hotjava subdirectory)
HOMEDRIVE=g:
HOMEPATH=\usr\users\davel
CLASSPATH=.;e:\java\local\simpledraw;e:\java\local\yassl\parser;e:\java\loca
l\vjv\visjava.zip;e:\java\local\java_cup;e:\java\local\espresso-1.0b\classes
;e:\java\local\dejava\classes;e:\java\classes;e:\java\classes.zip
PATH=e:\java\bin;f:\msdev\bin;l:\spectcl-0.1a
(NOTE that HOMEDRIVE and HOMEPATH are overridden by somebody to:
HOMEDRIVE=D:
HOMEPATH=\users\default (does not contain .hotjava subdirectory)
This is NT's idea of my home directory.. it overrides the settings in the
system settings widget of the control panel. I reset them to "G:" and
"\usr\users\davel" (omitting the quotes) each time I start a new console
(dos box).
)
For applications which are contained in a zip file like visjava.zip, the app
will start.
For apps whose classes are contained in a single directory like SimpleDraw,
the app will start. On the other hand, java_cup is in a single directory,
and when "java -v Main" is executed, it successfully loads a long list of
classes from e:\java\lib\classes.zip, including "[Loaded .\Main.class]" and
then reports: "Can't find class Main".
For ANY app that is in a subdirectory of the CLASSPATH path such as dejava,
where the appropriate command is: "java -v dejava.sys.SystemManager" (where
the CLASSPATH is set to e:\java\local\dejava\classes and there IS an
e:\java\local\classes\dejava\sys\SystemManager.class), java.exe ALWAYS
reports: "Can't find class dejava/sys/SystemManager" and does not even load
the (SystemManager) class specified on the command line. If CLASSPATH is set
to e:\java\local\dejava\classes\dejava\sys, it still won't load the
SystemManager class and fails with "Can't find class SystemManager".
Several questions come up:
Does java.exe use CLASSPATH correctly?
Does "Can't find <class>.class" always mean that (or could it mean "can't
find a version I recognize")?
Do all class paths have to be fully qualified in spite of documentation to
the contrary?
I have tried every possible permutation of minimal environment settings,
uppercase/lowercase, "/" vs "\" etc. that I could think of without a
different result. I have also read every bit of FAQ, newsgroup, java
interest mail, and Java homepage that I could find. What could I be doing wrong?
Thanks in advance for any help you can give....
Sincerely,
Dave LeBlanc
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com