Bugs, Possible Problems and Leftovers with QAZ v3.09c: ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ o QAZ seems to have some problems with certain LAN drivers, and had to be taken offline from one BBS because of that. o QAZ does not show comments (with the -vc option) for HPACK or SQZ archives because the comments are compressed. (In the case of HPACK files, the comments may be GIF or JPEG graphics.) o QAZ cannot list UC2 or PIT (Macintosh) archives because the file- information is encoded. o Some archive formats handled by QAZ are based on hacked information, and possible bugs may be lurking in strange files. If QAZ does not show information such as CRCs or file-attributes, it is for the same reason. o QAZ will choke on some Windows DLL files. Since these are not known to be used for archives, it is not a major problem. o Since all ARJ archives are backward compatible with version 1, that is the version QAZ will report. ARJ uses internal version numbers that do not coincide with release version numbers, so some future ARJ archives may give unusual version numbers. o QAZ cannot properly determine the version number of HA archives, and so will only report 'v0'. o QAZ cannot handle UniCode or EBCDIC filenames in HPACK archives. o QAZ does not show file attributes from HPACK archives. o QAZ can only recognize Level-1 HPACK archives. o Some Amiga LHA files are not compatible with LHArc, and will be re- ported as damaged. o QAZ cannot recognize the security envelopes on PAK archives. Hence the -ra option will not flag this. o QAZ does not always recognize broken Zip archives, and will give a partial listing without noting that the file is damaged. o QAZ does not recognize the AV codes for some PKZip v1.xx archives. This will be the case pending more information. o QAZ does not adjust for time-zones in Zoo archives.