Re: [freenet-support] Dosn't work
Glenn Fly wrote: I finished downloading Freenet and tried runing all entries from the Taskbar Menu; Desktop; Startmenu. My machine makes a sound like it would recognize the program but nothing happened. I have the following system: Compaq 5000; 128M memory; 40G HD, running Windows ME. Can you help? Do you get the red rabbit in the lower right corner of the desktop? And if you mouse over it what deos the status text say? Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
Re: [freenet-support] Problem
Marius Walter wrote: Hi there I have a problem to run the Freenet 17092001 snapshot version. First I tried the 0.3.. version. No Problem. But when I install the 17092001 the rabbit says: Freenet is having Problems. Check Freenet.log when i try the configure: Could not find the main class. Program will exit. what can i do. Yep, I know of this problem. It occurs only under some circumstances situations and will be fixed in the next snapshot (later this weekend) Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
Re: [freenet-support] freenet prob
Mr.Bad schrieb: FG == Flute Gardener [EMAIL PROTECTED] writes: FG Jun 6, 2001 2:33:02 PM:Error:Inform Connection FG failed:java.net.ConnectException: Operation timed out: connect OK, this is a firewall problem. You need to open up your 80 port for outgoing connections. In fact, you need to open up ALL ports for outgoing connections, and your listenPort (in freenet.ini) for incoming connections. Nope, Zonealarm works on a per-app basis rather than on a port basis. You have to allow Java.exe/Javaw.exe access to the Internet. Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
[freenet-support] Re: error message during start freenet Win release plan
Dave Hooper schrieb: Neither can I (Win 98 and ME) that is really weird. But as -cp/-classpath option does not work for all Java's we have to try to fix it via the CLASSPATH variable. Well, as you know, that fix is already IN. Yep, I know. One issue which remains seems to be that spaces in the JavaExec path don't work with the CLASSPATH approach. We might need to wrap it in 's. But I already said this in a previous mail. :-) You are suspecting me of not using the latest code? :-) :-) Stranger things have happened :-) I take it the 0.3.9.1-2 (shhh!) release uses MY freenet.exe and not your weird one? :-) Absolutely pure CVS code, even build in the CVS directory :). But as David McNab already tested, even the -2 installer didn't work, so hopefully it works with your updated Freenet.exe What I'm doing currently is getting freenet.exe fixed up straight. Compiled without optimisations it seems to work ok with the 'crashing' version of config.dll. This gives us two options: 1The new release *MUST* instead fall back to using the java configurator instead, for the moment (sorry). Therefore the new installer must *DELETE* any traces of config.dll in the intended installation directory That is what I thought as well. If it's crashing (and we lost the updated source), let's fall back to the Java config. Your Freenet.exe does it automatically if config.dll doesn't exist, so it is the easiest thing in the world to do, right? 2The new release uses the binary config.dll (the so-called crashing one) and we cross our fingers and hope it works with the new freenet.exe There is *NO* option 3 , Use the existing config.dll, because it is too incomplete to be of much use. Sorry. So, personally, guess what, I'd go for option 1. Absolutely agreed on, Sir! Java config for the next release. 4) After that release, the very next thing we do is fixing Javafind Yeh, that can wait. Mmh, can't wait too long unfortunately. At least we have to fix up the hang on no Java found, the reverting to the first found entry on search done and the long expected improvement of the registry reading. Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
[freenet-support] Re:error message during start freenet Win release plan
Dave Hooper schrieb: This is true and I am assisting with the release. I'm sorting out some final things and hopefully the release will be this Friday. The weird thing is I'm almost completely sure that the cannot find main class bug was fixed already in the latest (0.3.9.1-1) release, I've certainly not been able to reproduce it here (also Win2000) Neither can I (Win 98 and ME) that is really weird. But as -cp/-classpath option does not work for all Java's we have to try to fix it via the CLASSPATH variable. The latest version does this itself anyway so it shouldn't be necessary. However, if setting CLASSPATH=c:\freenet\freenet.jar (or whatever your path is) gets things working then I think we've found the problem -- if this truly works then it means the 'latest' version of freenet didn't contain the latest code! :-) You are suspecting me of not using the latest code? :-) Actually, I think what we should do is the following: 1) I lost the updated source code of config.dll due to hd crash, so we need to continue from what we have in CVS (Dave would you provide a updated and noncrashing config.dll to CVS if you haven't done it already?) 2) Put out a new release on Friday, with what we have in CVS right now (I changed e.g. some small things in cfgclient and yes, they are in CVS :-). 3) I am sorry but there will be no pre-release testing this way, but it can't get worse at the moment, so we should just push out something ASAP and see if the number of complaints decreases. 4) After that release, the very next thing we do is fixing Javafind Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
Re: [freenet-support] Could not find main class - exiting! Workaround found.
Perks, Graham schrieb: javaexec and javaw were pointing at c:\program files\jre\1.3.01 or similar. I changed the paths to c:\jdk1.3\jre\..., restarted Freenet, and now it works! I suspect the space in the original pathname. Mmh, we had this error already a couple of times connected to spaces in folder names. Dave, I can think of a possible error source now: Do we wrap the Classpath variable in if there are spaces in the path? I think we might need to do that the classpath variable might not allow spaces? What do you think of this? Do you change it and give it a try, or should I (I have very little time at the moment and can't do it before the weekend)? Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
Re: [freenet-support] quick and dirty solution for class not found problem on windows?
ugo pardo schrieb: When running Freenet I got the dreaded Could not find the main class. Program will exit! dialog box. From a quick inspection, it semed to me that the problem was caused by the blank in the Program Files Yes, that is what I suspected as well but great that you tried out for sure. Hope this can be useful for someone. Thanks that was very interesting. I modified the small utility which does the configuration and I hoe it really will work soon (I can put out a new release beginning of next week) Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
Re: [freenet-support] Could not find the main class
The system tray utility has been replaced with a new version and there seems to be a new bug, although I think this appeared mostly when the Microsoft JRE jview.exe was chosen upon install. I will try to release a bug fix version ASAP, for now you can just replace freenet.exe with the file that has been in 0.3.8.1 Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
Re:[freenet-support] Error message on Freenet startup
Roger Harrison [EMAIL PROTECTED] wrote on 29.4.2001 06:46:13: I've just downloaded the JRE (1.3.0_02) from Sun's website, also Freenet ver 0.3.8.1 and installed both (JRE first) on a 120 MHz Pentium laptop running Win98. When double clicking on the Freenet taskbar icon, a message appears: 'http://localhost: 8081' - ERROR: Your browser could not be opened with the address specified above. Please ask [EMAIL PROTECTED] for help. Did the gateway page turn up in the browser anyway? You might want to download the 0.3.9.1 version of Freenet, besides some bugfixes it contains a new implementation of the system tray icon. If I retry running Freenet by running the file 'fserve.exe', it brings up a window titled Freenet node 0.3.8, with two menu headings (File Help), and the words 'Node running' in the window. You don't need to do this is you have the system tray icon (hops) visible in the system tray Sebastian ___ Support mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/support
