Subj : Re: Issues with running makenl for a region To : Alan Ianson From : Dan Clough Date : Wed Mar 05 2025 08:29:52 -=> Alan Ianson wrote to Dan Clough <=- >> That's a Z. At one time it was widely used as an end of file >> marker. >> I suppose you could just remove that last line. > That would likely "break" the CRC value shown on the top line of a > segment. Not sure if that matters, but... AI> I'm not sure if the first and last lines are part of the CRC but they AI> are best left alone. Yes, I agree, but hence my question... > That actually raises a question I've wondered about... Is there > actually a need these days to create segments/nodelists with something > like 'makenl'? AI> My and I suppose most NC's segments are done by hand but processing it AI> with makenl includes the CRC and that's a plus. It's a requirement I AI> think. I'm an NC, and when changing my segment I use a normal text editor, save it, and then process it with makenl. What I'm asking is: Is the "processing" by makenl really needed? All it really does is generate this CRC, and I'm asking if that CRC is actually needed by anything. > I use it, and understand it, but is it really required? AI> RC's and ZC's lives are much easier with makenl. :) Maybe, assuming they set it up with incoming dir's and files, etc... I bet many of them just use the 'data' keyword and have all the entries below that. > Could not the segments just be edited like any other text file, with a > normal text editor? I think the CRC is maybe used in "diff" processing, > but who actually needs/uses a diff file any more? AI> The CRC is a way to make sure you got the file without error, as AI> intended. Yes, I know, but.... if you can't trust your downlink *C, who can you trust? It's not like we have to deal with "line noise" corrupting a file while it's in transit. ;-) .... Gone crazy, be back later, please leave message. === MultiMail/Linux v0.52 --- SBBSecho 3.23-Linux * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115) .