This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
First, I want to thank all for their patience. I'm not really retardedstupid, just very very green. Second, is their an easy way to test whether I have my path variable right? I think I may have mistakenly set it in both the system and the user section. Third, about the classpath variable:
The Java2 for Dummies says this: "Okay, you've set your PATH variable. Now what? The next thing you do is to tell your system wherre you plan to put your Java programs. To do this, you set something called a CLASSPATH variable."
"The good news is, after you've followed the instructions to set the PATH variable (earlier in this section), then setting the CLASSPATH is the same story all over again. In fact, it's even easier, because you don't have to know the name of any directories. Just follow the steps described above for setting a variable on your particular operating system. When you get to the point where you're actually filling in a value for the CLASSPATH, make sure the value contains a single dot (that's right, a period). C:\jdk\classes;."
Is that really all there is to it?
For those of you who think me too lazy to use the FAQ. I've spent countless hours wandering around in there and often times come out of it even more confused and disillusioned.
Thanks to all for their help and more importantly their patience.
On the more recent versions of Java, there is usually no need to have a system classpath at all. Any advice given to set a system classpath is rather out of date, but at least Barry Burd only tells you to add .; which can never do any harm.