I've just now modified and recompiled the 'findjava' program. It's checked back into CVS, along with the findjava.exe binary
Changes are: 1) 'jview.exe' is no longer recognised as a java interpreter 2) no windows directory will be searched for java interpreters 3) The 'update settings' button is disabled until the directory scan completes. David ----- Original Message ----- From: "Sebastian Sp?th" <[email protected]> To: "Freenet" <devl at freenetproject.org> Sent: Thursday, April 19, 2001 8:21 PM Subject: FW:RE: [freenet-devl] Windows installer - best not recognise Windows java > Benjamin Coates <coates at windmail.net> wrote on 19.4.2001 01:02:40: > > > >>From Sebastian at SSpaeth.de > >>>I tried to look into the installer, but couldn't make heads or tails of it; > >>>does anyone know what bit of code writes out the initial freenet.ini? > >> > >>Freenet.ini is created by running "Freenet.scripts.Setup.java freenet.ini > >-silent". This used to work just fine > >>and if something is broken Setup.java needs to be fixed. > >> > >>Sebastian > > > >Ok, the problem is that jview is being launched using -classpath, which > >java/javaw accept but jview/wjview don't (they return an error message). Both > >of them accept -cp, so if you switch it in flaunch.ini (which is created > >somewhere by the installer, since the one created by the installer DOES NOT > >match the one in CVS (freenet/Contrib/wininstall/Freenet/FLaunch.ini), jview > >should work again. > >
