Well, gone anyway. I just successfully updated from the most recent nodediff with no problems. My guess is the previous update cleared whatever had it convinced there was a missing diff in the chain from nodelist to current diff, even when this did not exist, but without any idea of how xlaxdiff works in the
first place....

Sigh... maybe I should just go check the Standards page and write my own....

--- Msged 6.0.1
* Origin: StormGate Aerie (1:102/524)

Hello, Kay.

On 03 Feb 03 at 15:27, Kay Shapero wrote to All:

Sigh... maybe I should just go check the Standards page and write my own....

That's always an option... and as the saying goes, "If you want something done right, do it yourself." ;)

Later,
Sean

// hausmaus@midnightshour.org | http://midnightshour.org | ICQ: 19965647

--- SBBSecho v2.00-OS/2
* Origin: Midnight's Hour BBS - midnightshour.org (1:11/200)

Well, gone anyway. I just successfully updated from the most recent

nodediff

with no problems. My guess is the previous update cleared whatever had

it

convinced there was a missing diff in the chain from nodelist to current

diff,

even when this did not exist, but without any idea of how xlaxdiff works

in the

first place....

Sigh... maybe I should just go check the Standards page and write my

own....


PMFJI kinda late.. but what version of XLAX are you using? I hardly bother with the diff files. I just grab a full nodelist from the internet about
every 2 weeks or so.
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Try Our Web Based QWK: DOCSPLACE.ORG (1:123/140)