Do not set the classpath - the run.bat will set it for you. You also do not need to set JBOSS_HOME - run.bat will set that also.
You also need a 1.5 JDK and to set JAVA_HOME. Do not install the JDK into Program Files - many Java libraries tend to have issues with spaces in paths. I installed JDK 1.5 at c:\apps\java\jdk-1.5.0_16, and I set JAVA_HOME=c:\apps\java\jdk-1.5.0_16
If this does not get you running, please post the entire contents on the command prompt window.
You shouldn't have that much trouble running JBOSS.
Make sure JAVA_HOME is set as a System environment variable, and points to a valid JDK.
Shouldn't be necessary, but create a System variable called JRE_HOME which will have the value %JAVA_HOME%
Add %JAVA_HOME%\bin to your System PATH variable
Open a command prompt to start JBOSS
[list]ensure that JAVA_HOME is correctly set, type [/list][list]Ensure that java is in the path by typing [/list][list]Try running JBOSS again, [/list] [ September 10, 2008: Message edited by: Yves Zoundi ]
Wait a minute, I looked a little more closely at your output. You have JAVA_HOME set incorrectly. It is set to an entire path, and not to just the JDK location. Fix your JAVA_HOME setting:
set JAVA_HOME=C:\Program Files\Java\jre1.5.0_02
It looks like you are running with a JRE and not a JDK. You should install a JDK and use that (though a JRE will work). As I mentioned earlier, you should not install the JDK into Program Files - you will run into issues later.
Finally, you are running a very old JRE - I recommend installing the latest 1.5 JDK: 1.5.0_16 [ September 10, 2008: Message edited by: Peter Johnson ]
You still have JAVA_HOME set incorrectly. It appears that there is a semicolon after it - get rid of the semicolon.
Besides the earlier warnings about using a JDK in Program Files, I will add another warning that JDK 6u3 (which you have) has issues and I recommend using a newer version (6u7). Finally, the JBoss Application Server 4.2.2 is NOT supported on JDK 6, you should really use a 1.5 JDK. (Having said that, it seems to work for the most part but if you run into problems you should fall back to JDK 1.5 to make sure it is not a JDK issue.)