RE: Helpful hint for javakit and windows XP

Dear Bruce - Re:  "Also, on the topic of Java exe paths you might find these
experiments/musings interesting:
http://www.practicalembeddedjava.com/tools/javapaths.html".

You have some really "odd" stuff going on in your classpath example with
";.;" and ";;"!

See below... Best regards, Kelly Smith

And you should know what my classpath is too:

CLASSPATH=d:\java_lib\commapi\samples\BlackBox\BlackBox.jar;.;D:\java_lib\ut
il\systronix_utils.jar;D:\jakarta-ant-1.5.1\lib;;D:\j2sdk14\lib\comm.jar;D:\
aJile\Runtime_cldc\Rts;D:\tini1.11\bin;.;D:\java_lib\util\systronix_utils.ja
r;D:\jakarta-ant-1.5.1\lib;;d:\java_lib\onewire\OneWireAPI_J2ME.jar;D:\Amule
t\Projects\applets\Widgets.jar;



-----Original Message-----
From: tini-admin-6tN4nzCoH/[email protected] [mailto:tini-admin-6tN4nzCoH/[email protected]]On Behalf Of
Bruce Boyes
Sent: Thursday, April 29, 2004 8:17 AM
To: Andy Page; tini-6tN4nzCoH/[email protected]
Subject: Re: [TINI] Helpful hint for javakit and windows XP


At 03:04 PM 4/28/2004 +0100, Andy Page wrote:
>I had fun this morning getting javakit to work, previously I had no
problems
>running under windows 98.  After sprinkling the java comm bits and pieces
in
>the various jdk/jre directories and still not seeing any serial ports I
>finally discovered that having the java default installation directory as
>C:\j2sdk1.4.2_03 doesn't seem to work properly!  Renaming it to C:\java
>cured the problem and hey presto we have serial ports!  It seems that
>underneath, Windows XP is more like NT/DOS and may work better with short
>file/directory names (8+3 format).

I think some programs use the first period as a delimiter and assume that
what follows is the extension name so in this case the file would be
assumed to be j2sdk1.4 which is not going to work.

Also some multi-platform programs we use, and the Java tools in general,
cannot tolerate whitespace in path names, since whitespace is also a
delimiter between command line arguments. You can pass a name with
whitespace if you enclose the whole string in quotes, for example:
somejavatoolexe "argument with whitespace" argument1 argument2

Also many tools don't accept other punctuation such as dashes/hyphens in
path names.

When you think about it, you can't have whitespace in a URL either, and
slashes are delimiters.

So for your own sanity and portability of your work, follow the Java naming
conventions in filenames, and then your code should run anywhere - Windoze,
Max, Linux, Unix, Solaris, etc. Why do it any other way? (Don't ask me why
Sun uses names like j2sdk1.4.2_03 instead of using underscores or other
versioning conventions).

Also, on the topic of Java exe paths you might find these
experiments/musings interesting:
http://www.practicalembeddedjava.com/tools/javapaths.html

Bruce


------- WWW.SYSTRONIX.COM ----------
   Real embedded Java and much more
www.jrealtime.com and www.tstik.com
+1-801-534-1017  Salt Lake City, USA


_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini


_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini