Hello mark,

 ML> i have a question that may be helpful to you guys...

 ML> instead of faffing about with nodediffs, can you simply replace the
 ML> nodelist with a daily nodelist and the tool will automatically see the
 ML> nodelist is different and recompile its indexes?

Sounds interesting.  I wasn't aware that there even was a daily version of the
whole of fidonet until I did a file-req for NODELIST and my boss delivered the
current daily version.

(I thought file-req for NODELIST would give me the official WEEKLY version
only.)


 ML> that'd sure be a lot easier than trying to deal with nodediffs... i
 ML> wouldn't even carry/distribute nodediffs if it weren't for some of my
 ML> links wanting them... my system uses a new full nodelist every day as
 ML> soon as it arrives... no muss, no fuss ;)

In OXP, once the config is done, there is "no muss, no fuss" too, and
everything is automatic.    

But in my case, in my very early use of OXP, I entered the filenames for the
Z2PNT diff files (the archived name and the unarchived name incorrectly.) 
After I fixed that, OXP seemed to hum along very nicely.  

Then, along the way, I incorporated a "new" nodelist because something else
caused a glitch here (which has since been fixed in the newer version of OXP). 


By then, I stopped processing the Z2 DIFF files again, and thought I don't
really need those. OXP hummed along quite nicely, and incorporated the weekly
updates well.

Later at some point I wanted to reintroduce the pointlist.  I made a mistake in
the config and had to start from scratch.  I did not realize that another "new"
nodelist that I pulled in manually was one of the full DAILY versions. (I had
file-reg'd NODELIST from my boss system.) From that point onward, the weekly
DIFF file did not know how to work with that, I guess.   And/Or, maybe I missed
processing one of the diffs manually.

Around the same time (probably the same day when the new diffs arrived from my
boss system), I had to roll back my Win XP system to an earlier restore point -
something I hadn't needed to do in over 10 years!  That's when the lock up
started, again.  :(

But now, I have the nodelist freshly configured with the latest weekly version.
I am now confident that the Z2PNT config is good and ready for the next sync.  

Plus, after getting rid of any latent nodelist files lurking in the incoming
directories, OXP polled properly and has not locked up.  

OXP seems to be very sensitive on nodelist configuration for regular
operations. Even the PKT processing stops and the messages never get tossed. :(
  

Meanwhile, it is good to have a couple of other reader options (nntp and
WinPoint) so that I don't have to miss anything.



--- WinPoint Beta 5 (359.1)