On Sun, 14 Mar 2004 15:50:14 -
"Dave" <[EMAIL PROTECTED]> wrote:
> > While ideas are being tossed around for the Windows installer and/or
> > configurator, which if either of them generates the default.ini and
> > freenet.ini files that appear during installation?
>
> Dude... neither... The
> While ideas are being tossed around for the Windows installer and/or
> configurator, which if either of them generates the default.ini and
> freenet.ini files that appear during installation?
Dude... neither... The autogenerated config scripts are generated (as your
image states!) by Freenet.s
On Sat, 13 Mar 2004 17:08:24 +
Toad <[EMAIL PROTECTED]> wrote:
> So what can we do about this? We can certainly detect config files that
> have been generated by old versions of the config tool, as it labels
> them...
While ideas are being tossed around for the Windows installer and/or
config
On Sat, Mar 13, 2004 at 04:50:15PM -, Dave wrote:
> > A lot of the problem actually is due to users running nodes with old
> > config files generated by the windows configurator, which forces all
> > settings (doesn't write %'s), so they run with old settings such as 50
> > node routing tables,
> A lot of the problem actually is due to users running nodes with old
> config files generated by the windows configurator, which forces all
> settings (doesn't write %'s), so they run with old settings such as 50
> node routing tables, which mean that the unix nodes run a lot better
> than the wi
A lot of the problem actually is due to users running nodes with old
config files generated by the windows configurator, which forces all
settings (doesn't write %'s), so they run with old settings such as 50
node routing tables, which mean that the unix nodes run a lot better
than the windows ones
I would imagine that the problem is a lot of users running nodes with older,
incompatible releases. If part of the content is only stored on such nodes, the
chance of a user with the new release being able to retrieve is very slim. If
everyone was up to date, I don't think there would be a pro
On Mon, 2004-03-08 at 04:00, [EMAIL PROTECTED] wrote:
> Send Support mailing list submissions to
> [EMAIL PROTECTED]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
> or, via email, send a message with subj
