Hello,
A few things.
1. Are you really coming from Tomcat 4.04?
2. Are you really using Java 18? It's basically dead. Use Java 17 or 21,
which are both Long Term Support (LTS) versions, especially if you are
only going to upgrade once every 20 years.
3. You should not have CLASSPATH set.
4
Thanks for the advice!Did two runs: regular cmd and one with admin
privileges::The cmd window looks good:
C:\tomcat8\bin>startupUsing CATALINA_BASE: "C:\tomcat8"Using CATALINA_HOME:
"C:\tomcat8"Using CATALINA_TMPDIR: "C:\tomcat8\temp"Using JRE_HOME:
"C:\Program Files\Java\jdk-18.0.2.1
On 23/04/2024 03:31, DdC wrote:
I have installed tomcat originally with version 4.04 on winxp andlater on win7,
ubuntu, and another linux box - many times by now.Trouble now with win10 and
version 9.0.88.Yes, there is a jdk, CLASSPATH is set, j2ee.jar is in
lib.Running in a cmd window with
ack. I meant fire off under Eclipse, not tomcat.
if that helps
On Mon, Apr 22, 2024 at 9:03 PM Stephanie Panah
wrote:
>
> Perhaps I am misunderstanding, but if not, I had something similar.
> be sure that tomcat is not running under Services.
> then fire it off under tomcat.
> and, of c
Perhaps I am misunderstanding, but if not, I had something similar.
be sure that tomcat is not running under Services.
then fire it off under tomcat.
and, of course, I may have just said nonsense.
On Mon, Apr 22, 2024 at 7:33 PM DdC wrote:
>
> I have installed tomcat originally with version 4.0
I have installed tomcat originally with version 4.04 on winxp andlater on win7,
ubuntu, and another linux box - many times by now.Trouble now with win10 and
version 9.0.88.Yes, there is a jdk, CLASSPATH is set, j2ee.jar is in
lib.Running in a cmd window with bin startup triggers another cmd win
