Benjamin Coates <[EMAIL PROTECTED]> wrote on 19.4.2001 01:02:40:
>
>>From [EMAIL PROTECTED]
>>>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.
>
>When this gets fixed and tested (I can test if needed), we should release a
>new package for windows, since the current one is broken.
ARRRGG. I hate Windows. I explicitely changed that from -cp to -classpath as it broke
some other
JREs (older versions of Suns Java I think) and I was told that -classpath would be the
standard way to
go. So either way we will be breaking some Java versions.
I really start thinking disabling jview.exe is the way to go now. It would be great if
somebody would
have a look at the C++ JavaFind util (source in CVS Contrib/Wininstall/Source) and do
that before I
get to it. It is just a matter of removing jview.exe from the list of allowed names
and recompiling it.
Sebastian
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
