Hello Mark,

I am back after two sailing periods, one for 4 days, and one for 8 days.

LG>>>>  LG> D:\PXW\NODELIST\NODELIST.342
WD>>> Where did you get that one from?
LG>> Wherever I can find them, it's only 3 months old.

ml> it is way ouf of date, though... hell,
ml> these days, one that is two weeks old is out of date...

Not for every node. See below why.

LG>> Is there somewhere I can always find the latest nodelist at?

ml> your NC or RC should have the latest... we've even got daily nodelists
ml> being generated and distributed so you can stay right up to date instead
ml> of being a week or more behind all the time...

A fresh Nodelist (only one week old) is ONLY necessarry when Direct polling or
crash polling is the working mode.
When only receiving or polling the regular UpLink compiling a new NodeList
is not needed.
There may be a difference when using IP,
but when POTS only, the Phone number hardly changes,
it is still the same for very many years at both sides.

When I want to crash poll a Node, I compile a new fresh weekly NodeList
(never the daily ;-), and only then.
Doing it weekly or daily is useless, when almost not craspolling at all.

And beware, automatically updating by diff's can be very dangerous when running
 on autopilot if you are making a trip for more than 7 days long.
History has proven that!
When I read about that errors, I immediately stopped automatically using Diffs.
Manually compiling by Diffs also got difficulties every so often ;-(.
Making crashpolls when not at home in that vacation period can be a bad idea.
So updating is not so urgent when you crash poll very seldomly.
I only crashpoll when I am in a hurry for an answer,
or if hub/host routing does not work normally.

Henri.

---
 * Origin: Connectivity is the Future; UniCorn BBS 31 26 4425506 (2:280/1208)