Hello Janis.

04 Nov 02 14:39, you wrote to me:


 >>> No :)  From what I understand, the dos version is very bad and
 >>> doesn't process segments correctly, and I've heard that it drops
 >>> regions.

 >> Were you able to figure out what causes it to "act" funny?

 JK> No, not at all.  The only reason I thought to try touching the files
 JK> in the Update and master directory was because I'd remembered seeing
 JK> someone's comment that this had resolved the problem for them :)  I
 JK> carried the idea a bit further by importing the new segments into the
 JK> Update directory just before the zone list, and nodediff run.

Hmmm.....



 >> 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?

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

 JK> The big differnce between the two runs was that on the second run, I
 JK> removed all the *.305 files and re-imported the segments :) It could
 JK> 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. Deleteing the
"old" files could point 
to a corrupt file some where, but then what caused it to become corrupt in 
the first place?



 >>> So.. it can be flukey.. I'll be watching it very carefully in the
 >>> next few weeks 

 >> Very strange......

 JK> Yes, that's true.

Definitely......

Russell

--- GoldED+/LNX 1.1.4.7