Re: Problem start JSWAT

Mark,

Re-installation, especially repeated re-installation, is nothing but a
superstitious response to an undiagnosed problem.

You should stop and think about the pattern of symptoms--you came so
close to a meaningful hypothesis when you observed that Java programs
with GUIs are the ones that are failing but failed to follow through
with hypotheses centered around the differences between applications
with GUIs and those without them.

If you'd checked the JSwat list archives, you'd see that there
have been several problems related to video drivers and Java
applications with GUIs. (The problems tended to affect multiple
applications, so one can probably find similar reports on many
applications' user and developer lists. I'm aware of problems with my
Matrox G400MAX and jEdit and Forte / NetBeans as well as JSwat.)

I recommend you update the driver for your computer's video card and
see if that helps with your crashing Java GUIs.

Randall Schulz


Mark Arnold wrote:

> I still have the same problem... I first thought it was JSwat and
> uninstalled and reinstalled JSwat and also the JDK1.4.2 numerous
> times. Since nothing helped, I also uninstalled all the other
> JDKs/JSDKs, removed the "JavaSoft" tree under "CurrentMachine" in
> the windows registry and installed 1.4.1_05 - still the same
> problem I then tried to run NetBeans (versioon 3.5.1, downloaded
> this week) and it has the same problem. The only thing it does is
> show the java engine version if I add -showversion to the java
> engine parameters, that's it - nothing after that. It just gets
> stuck. It doesnt crash but it also doesnt do anything else...
> 
> Strangely, Tomcat (4.1.12) is still running fine, no problem here,
> with the same JVM (the only one on my system in the meantime). It 
> looks like any java application that uses a GUI gets stuck... I
> have a fast machine (almost 2GHz, 512 MB RAM), so that should not
> be an issue...
> 
> Any ideas? I'm almost about to reinstall the whole system...
> 
> Thanks,
> 
> MARK
> 
> P.S.: The exact same setup that doesnt work on my machine does work
> on another freshly installed XP system...