freeman@WATSUN.CC.COLUMBIA.EDU (Mike Freeman) (06/11/91)
In a recent Info-CPM Digest issue, Steve Graham (steve_graham@ub.cc.umich.edu) reports a problem with EXL putting a spurious character in files extracted from a .LBR-file. This is indeed the case and the problem manifests itself when a file whose uncompressed filetype is a single character (e.g., .Z). Dunno whether a 2-character uncompressed filetype produces the problem. What happens is that instead of filling the remaining two bytes of the filetype with spaces (20H), only the first is so filled, the third byte being set to zero. This causes the file not to be accesible after extraction (though you can rename it with NSWEEP, DISK77 etc.). Am working on a patch now.