On Saturday 14 July 2007 01:38, Juiceman wrote:
> On 7/13/07, bbackde at googlemail.com wrote:
> > Ok so I will update manually to 1043. I have one problem with the
> > manual update on WinXP: each time the freenet-ext.jar (which I had in
> > version 13) is downdated to version 12. After the node
Means you're connected to a buggy node (a node running a certain recent
build). Trunk will identify this and report a different connection error.
On Friday 13 July 2007 08:07, bbackde at googlemail.com wrote:
> Since yesterday my node shows the following critical message:
>
> Build too old
> This
Means you're connected to a buggy node (a node running a certain recent
build). Trunk will identify this and report a different connection error.
On Friday 13 July 2007 08:07, [EMAIL PROTECTED] wrote:
> Since yesterday my node shows the following critical message:
>
> Build too old
> This node's
On Saturday 14 July 2007 01:38, Juiceman wrote:
> On 7/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Ok so I will update manually to 1043. I have one problem with the
> > manual update on WinXP: each time the freenet-ext.jar (which I had in
> > version 13) is downdated to version 12. Afte
On 7/13/07, bbackde at googlemail.com wrote:
> Ok so I will update manually to 1043. I have one problem with the
> manual update on WinXP: each time the freenet-ext.jar (which I had in
> version 13) is downdated to version 12. After the node startup the
> node complains ("A new stable version of F
On 7/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Ok so I will update manually to 1043. I have one problem with the
> manual update on WinXP: each time the freenet-ext.jar (which I had in
> version 13) is downdated to version 12. After the node startup the
> node complains ("A new stable v
Ok so I will update manually to 1043. I have one problem with the
manual update on WinXP: each time the freenet-ext.jar (which I had in
version 13) is downdated to version 12. After the node startup the
node complains ("A new stable version of Freenet is available
It seems that your node isn't runn
Means you're connected to a buggy node (a node running a certain recent
build). Trunk will identify this and report a different connection error.
On Friday 13 July 2007 08:07, bbackde at googlemail.com wrote:
> Since yesterday my node shows the following critical message:
>
> Build too old
> This
Since yesterday my node shows the following critical message:
Build too old
This node's software is older than the oldest version (Build #1041)
allowed by the newest peers we try to connect to. Please update your
node as soon as possible as you will not be able to connect to peers
labeled "TOO NEW
Ok so I will update manually to 1043. I have one problem with the
manual update on WinXP: each time the freenet-ext.jar (which I had in
version 13) is downdated to version 12. After the node startup the
node complains ("A new stable version of Freenet is available
It seems that your node isn't runn
Means you're connected to a buggy node (a node running a certain recent
build). Trunk will identify this and report a different connection error.
On Friday 13 July 2007 08:07, [EMAIL PROTECTED] wrote:
> Since yesterday my node shows the following critical message:
>
> Build too old
> This node's
Since yesterday my node shows the following critical message:
Build too old
This node's software is older than the oldest version (Build #1041)
allowed by the newest peers we try to connect to. Please update your
node as soon as possible as you will not be able to connect to peers
labeled "TOO NEW
12 matches
Mail list logo
