Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    POINTS    |    Point usage discussion and systems suppo    |    3,070 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,278 of 3,070    |
|    August Abolins to Martin Foster    |
|    oxp: nodediff fails :(    |
|    01 Feb 20 18:53:08    |
      MSGID: 2:221/360.0 5e35acec       REPLY: 2:310/31.3@fidonet e1027b91       PID: JamNNTPd/OS2 1.3 20191227       TID: GE/2 1.2       CHRS: UTF-8 2       TZUTC: 0200       On 01/02/2020 4:46 a.m., Martin Foster : August Abolins wrote:                      AA>> I've been operating with nodelist. 024 all week quite smoothly.        AA>> Along comes the DIFF:               AA>> +- Error ------------------------------------------------------        AA>> | | NODELIST. 024: Wrong version/date of nodelist or nodediff?               MF> Hmmm, never seen that error before???              Hi Martin,              So, all the lock ups I've been having were probably based on this very       issue. :( And maybe it only applies to the Win/32 version, since you run       the Linux version?              BTW, the Z2PNT diffs *are* working, and .024 automatically recompiled to       ..031 just fine.              When I first installed and operated oxp (with a nodelist *and* z2pnt       list installed), I still wasn't signed up to the diff updates.              I probably registered for the pointlist updates first, and witnessed       smooth operations for weeks. But, as soon as I started receiving a new       NODELIST diff, the lockups started.              Could this also be partially related to the nodelist (parsing/search)       issue I discovered a few days ago?                      AA>> WHY isn't the nodediff (to bring me up to. 031) getting        AA>> applied?               MF> Try applying the diff manually and then have a look at your        MF> debuglog.txt and see if there's anything in there that gives a        MF> clue?              I couldn't figure out how to *just* trigger a diff update if the file is       sitting in the /FILES directory. I am sure I tried "recompile" or       something, but the .024 number in the config panel stayed the same.              Instead, I deleted the whole entry, and just pointed oxp to the .031       edition. I'm good until this Friday. :/                     --        Quoted with Reformator/Quoter. Info = https://tinyurl.com/sxnhuxc              --- TB68/Win7 (just keeping things short!)        * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)       SEEN-BY: 1/123 19/10 90/1 154/10 203/0 221/0 1 6 360 227/114 229/426       SEEN-BY: 229/1014 240/5832 249/206 317 400 280/464 5003 288/100 292/854       SEEN-BY: 310/31 317/3 322/757 342/200 396/45 423/120 712/848 770/1       SEEN-BY: 2452/250       PATH: 221/360 1 280/464 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca