Date   : Sun, 07 Oct 1984 11:21:00 MDT (Sun)
From   : Keith Petersen <W8SDZ@Simtel20.ARPA>
Subject: NULU10 - a machine language alternative to LU

A machine language alternative to LU (the Library Utility program that
makes .LBR files) is now available from SIMTEL20.

Filename                       Type     Bytes   CRC

Directory MICRO:<CPM.CPMLIB>
NULU10.COM.1                   COM      14336  63C1H
NULU10.DOC.1                   ASCII    40770  91E0H
NULU10.HEX.1                   ASCII    34899  255BH

...and the whole package for those who can FTP ITS-binary files:
NULU10.LBR.1                   COM      38272  D7CEH

Here is an excerpt from the author's .DOC file:

NULU  is  offered  as a complete replacement for LU  and  LSWEEP.  
Weighing  in  at 14k,  it includes nearly all  features  of  both 
programs and then some.  It features:

       Two operation modes with a full menu for each
       Viewing  and printing of member files,  unsqueezing  when
                necessary
       Extraction of member files with an option to unsqueeze
                where appropriate
       Bigger libraries, up to 800 members or more depending on
                available memory
       Automatic member sorting, all members kept sorted at all
                times
       Faster reorganization
       Enhanced error handling
       Access to deleted members
       Optional read only mode
       General compatibility with LU and NSWEEP syntax
       Numerous user patches

I  am aware of only one thing that LU does that NULU does not do.  
LU  maintains  a  CRC for each member file and  for  the  library 
directory  as a whole.   NULU doesn't do this at all.   In  fact, 
NULU changes these CRC bytes to 00 as soon as it gets the chance.  
In case you still want or need to run LU on a library modified by 
NULU, LU will simply regard it as a library created by an earlier  
LU version and will promptly set CRC's for the various members.

To the best of my knowledge,  NULU will run on any system running 
CP/M  2.x  or  higher,  however it has only been  tested  on  the 
Osborne  1  and the Osborne Executive computers.   It is  written 
entirely in 8080 assembly language.

--Keith