Re: [freenet-support] Windows 7

[Bill Shutt]

Hi Matthew

After several attempts i managed to install Freenet (Kaspersky eventually came 
up with a solution - disable their programme during the d/l and install!). It 
has had an immediate effect on the performance of my laptop, slowing it down 
considerably and causing it to hang often. i am hoping this will eventually 
resolve itself (i seem to recall similar problems when running under XP and 
Vista a year or more back which did improve, although the computer performance 
was decidedly slower while Freenet ran).

My laptop is HP Pavilion9000 with Intel Core2 Duo CPU 2.2GHZ, 4GB RAM, 300GB 
HDD (although i am running Freenet on my dedicated Kingston 4GB USB drive) 
under Windows 7

Any advice you can offer to improve performance while Freenet is running as i 
would prefer to leave it running all the time. i recall when running it in the 
past i had to shut it down when i was d/l or working on large drawing files (i 
am an engineer)

Your kind help is much appreciated, and many thanks for getting me back on 
Freenet

Best regards

bill

From: t...@amphibian.dyndns.org
To: support@freenetproject.org
Date: Mon, 23 Aug 2010 13:31:29 +0100
CC: biza...@hotmail.com
Subject: Re: [freenet-support] Windows 7

On Saturday 21 August 2010 18:43:17 Bill Shutt wrote:
 
 Have you any idea when Freenet will work with Win7 please? When i try to 
 install i get an error and i see on the website you expect a fix shortly
 
Please try:
https://checksums.freenetproject.org/latest/FreenetInstaller-alpha.exe
 
Let us know if it works. Let us know if it doesn't work. It *is* an alpha, so 
it may not be perfect, in particular it does not have a manual update script, 
but that is only necessary in emergencies anyway, normally Freenet will update 
itself.
 
 many thanks in advance
 
Thanks for trying Freenet, and even more thanks if you try the above test 
installer!
 
 bill

___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
  ___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

[freenet-support] Windows 7

[Bill Shutt]

Have you any idea when Freenet will work with Win7 please? When i try to 
install i get an error and i see on the website you expect a fix shortly

many thanks in advance

bill
  ___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

[freenet-support] Freenet 0.7 build 1189

[Bill Shutt]

Many, many thanks for all the hard work you guys put into this project. i only 
wish i had skills to help you, sadly i do not. i will certainly contribute as 
and when i can affpord it, but that will have to wait until January with the 
holiday season looming

kindest regards, and grateful thanks

bill

> From: toad at amphibian.dyndns.org
> To: devl at freenetproject.org; support at freenetproject.org
> Date: Sat, 6 Dec 2008 14:49:14 +
> Subject: [freenet-support] Freenet 0.7 build 1189
> 
> Freenet 0.7 build 1189 is now available. Please upgrade, it will be mandatory 
> on Tuesday. Changelog:
> - Another new version of the connection setup protocol which hopefully will 
> be 
> the last for some time, which should fix the current disconnections problems 
> by negotiating whether to reuse the retransmission data and thus avoiding one 
> side choosing to reuse it and the other side not reusing it, resulting in a 
> disconnection.
> - Fix a bug causing us to fail to connect to nodes with DNS addresses (e.g. 
> darknet peers on dyndns) in some cases.
> - Various other improvements to the connection setup layer, especially error 
> handling.
> - Fix a serious bug in opennet, which was causing us to treat handling a 
> packet from an old opennet peer (or which was not identifiable at all) as 
> sending a connection offer, resulting in way too few connection offers being 
> sent.
> - Fix some bugs relating to ARKs.
> - Refactoring, clarify a string.
> 
> Also, XMLSpider and XMLLibrarian (the searching code) have been updated to 
> deal better with non-english languages (as long as they have spaces between 
> words i.e. not chinese yet), and a minor fix to KeyExplorer.
> 
> Thanks to:
> p0s
> sdiz
> toad
> 
> Please upgrade, and report any bugs you find on the bug tracker:
> https://bugs.freenetproject.org/
> 
> With regards to disconnections, please wait until Tuesday, then restart your 
> node. If you get any disconnection notices on the web interface after that, 
> please report them, it means we still haven't solved the problem.
> 
> Thanks for using Freenet! Sorry for all the problems lately, we are working 
> to 
> stabilise it...

_
Get Windows Live Messenger on your Mobile
http://clk.atdmt.com/UKM/go/msnnkmgl001001ukm/direct/01/
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-support] Freenet 0.7 build 1189

[Bill Shutt]

Many, many thanks for all the hard work you guys put into this project. i only 
wish i had skills to help you, sadly i do not. i will certainly contribute as 
and when i can affpord it, but that will have to wait until January with the 
holiday season looming

kindest regards, and grateful thanks

bill

 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]; support@freenetproject.org
 Date: Sat, 6 Dec 2008 14:49:14 +
 Subject: [freenet-support] Freenet 0.7 build 1189
 
 Freenet 0.7 build 1189 is now available. Please upgrade, it will be mandatory 
 on Tuesday. Changelog:
 - Another new version of the connection setup protocol which hopefully will 
 be 
 the last for some time, which should fix the current disconnections problems 
 by negotiating whether to reuse the retransmission data and thus avoiding one 
 side choosing to reuse it and the other side not reusing it, resulting in a 
 disconnection.
 - Fix a bug causing us to fail to connect to nodes with DNS addresses (e.g. 
 darknet peers on dyndns) in some cases.
 - Various other improvements to the connection setup layer, especially error 
 handling.
 - Fix a serious bug in opennet, which was causing us to treat handling a 
 packet from an old opennet peer (or which was not identifiable at all) as 
 sending a connection offer, resulting in way too few connection offers being 
 sent.
 - Fix some bugs relating to ARKs.
 - Refactoring, clarify a string.
 
 Also, XMLSpider and XMLLibrarian (the searching code) have been updated to 
 deal better with non-english languages (as long as they have spaces between 
 words i.e. not chinese yet), and a minor fix to KeyExplorer.
 
 Thanks to:
 p0s
 sdiz
 toad
 
 Please upgrade, and report any bugs you find on the bug tracker:
 https://bugs.freenetproject.org/
 
 With regards to disconnections, please wait until Tuesday, then restart your 
 node. If you get any disconnection notices on the web interface after that, 
 please report them, it means we still haven't solved the problem.
 
 Thanks for using Freenet! Sorry for all the problems lately, we are working 
 to 
 stabilise it...

_
Get Windows Live Messenger on your Mobile
http://clk.atdmt.com/UKM/go/msnnkmgl001001ukm/direct/01/___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

[freenet-support] Sorry to have to report bad bug in 1180

[Bill Shutt]

Many, many thanks for all your kind help. i reinstalled Freenet which now 
appears to be working OK

warmest regards

bill

> Date: Mon, 24 Nov 2008 18:54:18 -0500
> From: juiceman69 at gmail.com
> To: support at freenetproject.org
> Subject: Re: [freenet-support] Sorry to have to report bad bug in 1180
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> 
> On Mon, Nov 24, 2008 at 7:32 AM, Matthew Toseland  wrote:
> > On Monday 24 November 2008 07:26, Juiceman wrote:
> >>
> >> On Sat, Nov 22, 2008 at 9:54 PM, Juiceman  wrote:
> >> > -BEGIN PGP SIGNED MESSAGE-
> >> > Hash: SHA1
> >> >
> >> >
> >> >
> >> > On Sat, Nov 22, 2008 at 7:08 PM, Dennis Nezic  wrote:
> >> >> On Sat, 22 Nov 2008 16:54:58 +0100, guido
> >> >> wrote:
> >> >>
> >> >>> Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic:
> >> >>> > >> > WARNING - The Wrapper jar file currently in use is version
> >> >>> > >> > "3.3.1"
> >> >>> > > while the version of the Wrapper which launched this JVM is
> >> >>> > > "3.2.3".
> >> >>> >
> >> >>> > That looks strange.
> >> >>>
> >> >>> I have got that exact same warning in my logs as well. It has been
> >> >>> like this for quite some time.
> >> >>
> >> >> Well, first of all, all of freenet's dependencies, including this
> >> >> wrapper utility, are bundled "conveniently" in freenet-ext.jar. So you
> >> >> likely originally launched it with the "older" 3.2.3 wrapper, and later
> >> >> one freenet-ext got updated. Restarting the wrapper should get rid of
> >> >> this message, though I don't think it's anything serious, since my
> >> >> installation is still using 3.2.3.
> >> >
> >> > Actually the installer installs 3.3.1 iirc, but we don't have a way
> >> > currently to update old installs.  I manually did mine.
> >>
> >> Correction.  I just checked and the installer is loading the old
> >> version.  Nextgens should update this as there is a bugfix dealing
> >> with wrapper restarts.  Seems like we went thru this a few months
> >> ago...  yup: https://bugs.freenetproject.org/view.php?id=2564
> >> I wonder if the old versions got put back on the website somehow?
> >
> > The new version of the wrapper binary is known to fix the problem???
> 
> - From my original bug ticket:
> "You may remember I changed the Windows update.cmd script to loop
> during stop until the service was down because the node would not
> quite be stopped even though the wrapper thought it was. This led to
> corruption, hence the need for looping.
> 
> I see in the changelog for one version older than current:
> 
> "Version 3.3.0: Changes and bug fixes:
>   Fix a problem on Windows where the Windows Service Manager was
> not waiting the full configured time of the wrapper.jvm_exit.timeout
> and wrapper.shutdown.timeout properties. This was leading to the net
> stop command timing out and the system shutting down without the java
> application having fully stopped. Bug #1582568."
> 
> This may be the culprit for the occasional datastore corruptions,
> auto-update failures and the wrapper sometimes not being able to
> successfully restart the node after a crash/oom"
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.7 (MingW32)
> Comment: http://getfiregpg.org
> 
> iD8DBQFJKz6r4esu1mlKOs8RAt14AJ9a4vtJsmzFcznnltcCz44Fq4LvcwCghe3W
> 2VfxXzPMTJtLL1YD7Ecg90U=
> =siDv
> -END PGP SIGNATURE-
> ___
> Support mailing list
> Support at freenetproject.org
> http://news.gmane.org/gmane.network.freenet.support
> Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
> Or mailto:support-request at freenetproject.org?subject=unsubscribe

_
Win ?1000 John Lewis shopping sprees with BigSnapSearch.com
http://clk.atdmt.com/UKM/go/117442309/direct/01/
-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [freenet-support] Sorry to have to report bad bug in 1180

[Bill Shutt]

Many, many thanks for all your kind help. i reinstalled Freenet which now 
appears to be working OK

warmest regards

bill

 Date: Mon, 24 Nov 2008 18:54:18 -0500
 From: [EMAIL PROTECTED]
 To: support@freenetproject.org
 Subject: Re: [freenet-support] Sorry to have to report bad bug in 1180
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 
 
 On Mon, Nov 24, 2008 at 7:32 AM, Matthew Toseland  wrote:
  On Monday 24 November 2008 07:26, Juiceman wrote:
 
  On Sat, Nov 22, 2008 at 9:54 PM, Juiceman  wrote:
   -BEGIN PGP SIGNED MESSAGE-
   Hash: SHA1
  
  
  
   On Sat, Nov 22, 2008 at 7:08 PM, Dennis Nezic  wrote:
   On Sat, 22 Nov 2008 16:54:58 +0100, guido
   wrote:
  
   Am Mittwoch, 19. November 2008 05:32:18 schrieb Dennis Nezic:
  WARNING - The Wrapper jar file currently in use is version
  3.3.1
 while the version of the Wrapper which launched this JVM is
 3.2.3.
   
That looks strange.
  
   I have got that exact same warning in my logs as well. It has been
   like this for quite some time.
  
   Well, first of all, all of freenet's dependencies, including this
   wrapper utility, are bundled conveniently in freenet-ext.jar. So you
   likely originally launched it with the older 3.2.3 wrapper, and later
   one freenet-ext got updated. Restarting the wrapper should get rid of
   this message, though I don't think it's anything serious, since my
   installation is still using 3.2.3.
  
   Actually the installer installs 3.3.1 iirc, but we don't have a way
   currently to update old installs.  I manually did mine.
 
  Correction.  I just checked and the installer is loading the old
  version.  Nextgens should update this as there is a bugfix dealing
  with wrapper restarts.  Seems like we went thru this a few months
  ago...  yup: https://bugs.freenetproject.org/view.php?id=2564
  I wonder if the old versions got put back on the website somehow?
 
  The new version of the wrapper binary is known to fix the problem???
 
 - From my original bug ticket:
 You may remember I changed the Windows update.cmd script to loop
 during stop until the service was down because the node would not
 quite be stopped even though the wrapper thought it was. This led to
 corruption, hence the need for looping.
 
 I see in the changelog for one version older than current:
 
 Version 3.3.0: Changes and bug fixes:
   Fix a problem on Windows where the Windows Service Manager was
 not waiting the full configured time of the wrapper.jvm_exit.timeout
 and wrapper.shutdown.timeout properties. This was leading to the net
 stop command timing out and the system shutting down without the java
 application having fully stopped. Bug #1582568.
 
 This may be the culprit for the occasional datastore corruptions,
 auto-update failures and the wrapper sometimes not being able to
 successfully restart the node after a crash/oom
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.7 (MingW32)
 Comment: http://getfiregpg.org
 
 iD8DBQFJKz6r4esu1mlKOs8RAt14AJ9a4vtJsmzFcznnltcCz44Fq4LvcwCghe3W
 2VfxXzPMTJtLL1YD7Ecg90U=
 =siDv
 -END PGP SIGNATURE-
 ___
 Support mailing list
 Support@freenetproject.org
 http://news.gmane.org/gmane.network.freenet.support
 Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
 Or mailto:[EMAIL PROTECTED]

_
Win £1000 John Lewis shopping sprees with BigSnapSearch.com
http://clk.atdmt.com/UKM/go/117442309/direct/01/___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]