Hi Russell,

>>> So it has been running fine for a year, then in all likely hood,
>>> there arn't problems with NLMAKE, but possibly with what it gets
>>> fed?

>> NLMaint, not NLMAKE :)  Again, if this were true, why did the 2nd run
>> work ok? The 2nd run created a completely new (and correct as far as I
>> could see) zone1 list, and correct nodediff, without the errors the
>> first one had shown.

>> The big differnce between the two runs was that on the second run, I
>> removed all the *.305 files and re-imported the segments :) It could
>> be that the original segments were corrupted I suppose..

> It did not like something, that is obvious, but what, and why should
> "touching" the files "fix" the problem.

Being a bit tired after midnight that night, I wasn't in the mood to
trouble-shoot the problem the way I might have .. I knew I had to
catch all the tics and files that had been generated, and still do the
second run and check it .  Touching the files made a big
difference in the previous month's errors.. why, I have no idea.  I found
the C source on my system and will be taking a look at it this week (I hope
).

> Deleteing the "old" files could point
> to a corrupt file some where, but then what caused it to become corrupt in
> the first place?

It would have to be within a very short time period that this happened..
the exact same files were copied into the pertinent directories before the
first run.. In the second run, the files were deleted and then re-copied to
'force' a regeneration..

Take care,
Janis

--- BBBS/LiI v4.01 Flag-4