ruben@ut-ngp.UUCP (Ruben Ramirez-Mitchell) (02/08/85)
In reference to the news about NULU11.LBR available now in SIMTEL.
I have been using NULU instead of LU for several months
under CP/M-80, CP/M-816 and MPM-816 with no problems. It is an excellent
program if you use libraries. I am using them even more with a large hard
disk than with a floppy system.
I have noticed only two problems:
- if you use NULU with libraries created with LU you get error messages
indicating that the directory has a CRC error. Just ignore the message.
- the second is a real bug- if you extract a library member and specify a
destination ('du:file.ext'), and you enter the file name in lower case
then you cannot access the file. Directory listings using SD, for instance,
show the file name in lower case. Rename does not work, but you can
rename the file using VFILE, SWEEP, or DISK77.
Ruben Mitchellcem@intelca.UUCP (Chuck McManis) (02/15/85)
> > In reference to the news about NULU11.LBR available now in SIMTEL. > ... > > I have noticed only two problems: > > - if you use NULU with libraries created with LU you get error messages > indicating that the directory has a CRC error. Just ignore the message. I think you have this reversed, NULU version 1.0 does not put CRC's in the library directory whereas LU does, this causes LU to indicate a CRC error when using files created by NULU. NULU Version 1.1 uses CRCs and thus is totally compatible with LU. NULU can also be patched to know about your screen and that makes the output very nice. > > - the second is a real bug- if you extract a library member and specify a > destination ('du:file.ext'), and you enter the file name in lower case > then you cannot access the file. Directory listings using SD, for instance, > show the file name in lower case. Rename does not work, but you can > rename the file using VFILE, SWEEP, or DISK77. > I can see how this one would slip by most people. I for one rarely specify an output file because I want the output to have the same name as it has when it is in the library. I could see though that if you were doing a simultaneous extract (or unsqueeze-extract) and rename by using the =DU:Filename.Typ it would be a problem. There is one patch file out that fixes a couple of other bugs in 1.1 call NULU11F1.ASM. I don't know if it fixes these two above or not. --Chuck -- - - - D I S C L A I M E R - - - {ihnp4,fortune}!dual\ All opinions expressed herein are my {qantel,idi}-> !intelca!cem own and not those of my employer, my {ucbvax,hao}!hplabs/ friends, or my avocado plant. :-}