As far as I remember, the winstaller actually checks that the 1.4.x JVM is installed. If you have the 1.5.x JVM, I believe the winstaller will still point fred to use the 1.4.x JVM.... (I could be mistaken of course because I've not even looked at any of the installer code for over a year)
> "You've missed the point completely. The error message was "Could not find > the main class." A java programmer knows this to be not an error with the > virtual machine, but more of a classpath issue (the VM cannot find the > class; it never actually *ran* anything). > > Recommending that the user upgrade their VM is bad advice since that > clearly > isn't the issue. It's not too much to ask those who wish to contribute by > answering support questions that they actually understand the nuances of > Java." > > "Recommending that the user upgrade their VM is bad advice since that > clearly isn't the issue." is a prime example of spicious reasoning: it > does > not follow, because it's not the main issue, that it is bad advice. At > most, > if the advice was not wrong on itself and if no other recommandations were > made, it would constitute inadequate advice. > > I didn't miss the point, but you mix two things: the recommandation that > he > uses another JVM, and the recommandation that he should just auto-install > the stuff, and not put it manually in a folder. That installing a new JVM > is > probably not a main issue under XP was made clear enough by my words: > 'besides', 'mostly for linux', 'preferably', etc. > > The fact that it couldn't find the path IS probably due to him installing > stuff manually in a folder. Under windows, with the webupdate and all, you > can auto-install JVM as well as freenet 'out of the box', without any > manual > moving around afterwards, as I've said. In fact, your comment about him > installing it manually and that he will discover his error, hints at this > as > well. But since I think it's more difficult to find the right file(s) and > move it to the right folder, or adapt the path; the most easy thing to do > is > auto-installing a new JVM. I have done exactly the same more then once, > also > under windows, and I've never encountered classpath problems, so IMHO, the > recommandation was not 'bad'. > > Using another JVM like the 1.5.x build is an extra recommandation, for the > reasons I already said in earlier posts (and to which you do not agree, I > know). Maybe your interaction with users is vastly more elaborate then > mine, > but *I* didn't see much bugreports with as cause the 1.5.x build, > certainly > not compared to the 1.4.2 build. And, as you indicated, Toad himself has > recommended it already too. > > _______________________________________________ > Support mailing list > [EMAIL PROTECTED] > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at > http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:[EMAIL PROTECTED] > _______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
