Hello Paul


 PQ> I found a glitch of some sort with NSET when the line counter
 PQ> exceeds #767, i.e. anything like "NSET /L768 =$0 <
nodelist.299" (or
 PQ> a higher /L[value]) just turns up a blank line. Quite strange.  I'd
 PQ> be interested to hear from any other NSET user if they can replicate
 PQ> that error... or not. :-)

You are right. But it's not a problem of line number, it's one of size.
Running your example above with different files and line numbers, searching
for the first cutted line, deleting the following content and saving the
file i get a fix file size of 62228 bytes. This is near by the size of the
one 64k memory segment a COM file can allocate.


Micha

--- FMailX 1.48b