The following patches were applied to the incorrect PKWARE version of
APPNOTE.TXT (dated 15-Feb-96) to produce the correct version. These
patches have been sent to PKWARE.

*** appnote.txt~	Thu Feb 15 02:01:00 1996
--- appnote.txt		Thu Aug  1 17:51:05 1996
***************
*** 50,55 ****
--- 50,56 ----
  
    B.  Data descriptor:
  
+  	data descriptor signature	4 bytes  (0x08074b50)
  	crc-32                          4 bytes
  	compressed size                 4 bytes
  	uncompressed size               4 bytes
***************
*** 223,230 ****
  	  The length of the filename, extra field, and comment
  	  fields respectively.  The combined length of any
  	  directory record and these three fields should not
! 	  generally exceed 65,535 bytes.  If input came from standard
! 	  input, the filename length is set to zero.
  
  
        disk number start: (2 bytes)
--- 224,231 ----
  	  The length of the filename, extra field, and comment
  	  fields respectively.  The combined length of any
  	  directory record and these three fields should not
!           generally exceed 65,535 bytes.  If input came from
!           standard input, the filename is set to "-" (length one).
  
  
        disk number start: (2 bytes)
***************
*** 260,266 ****
  	  should be forward slashes '/' as opposed to
  	  backwards slashes '\' for compatibility with Amiga
  	  and Unix file systems etc.  If input came from standard
! 	  input, there is no filename field.
  
        extra field: (Variable)
  
--- 261,267 ----
  	  should be forward slashes '/' as opposed to
  	  backwards slashes '\' for compatibility with Amiga
  	  and Unix file systems etc.  If input came from standard
!           input, the file name is set to "-" (without the quotes).
  
        extra field: (Variable)
  
***************
*** 819,828 ****
  If the data block is stored with dynamic Huffman codes, the Huffman
  codes are sent in the following compressed format:
  
!    5 Bits: # of Literal codes sent - 256 (256 - 286)
  	   All other codes are never sent.
     5 Bits: # of Dist codes - 1           (1 - 32)
!    4 Bits: # of Bit Length codes - 3     (3 - 19)
  
  The Huffman codes are sent as bit lengths and the codes are built as
  described in the implode algorithm.  The bit lengths themselves are
--- 820,829 ----
  If the data block is stored with dynamic Huffman codes, the Huffman
  codes are sent in the following compressed format:
  
!    5 Bits: # of Literal codes sent - 257 (257 - 286)
  	   All other codes are never sent.
     5 Bits: # of Dist codes - 1           (1 - 32)
!    4 Bits: # of Bit Length codes - 4     (4 - 19)
  
  The Huffman codes are sent as bit lengths and the codes are built as
  described in the implode algorithm.  The bit lengths themselves are
***************
*** 1003,1010 ****
  
  After the header is decrypted,  the last 1 or 2 bytes in Buffer
  should be the high-order word/byte of the CRC for the file being
! decrypted, stored in Intel low-byte/high-byte order.  Versions of
! PKZIP prior to 2.0 used a 2 byte CRC check; a 1 byte CRC check is
  used on versions after 2.0.  This can be used to test if the password
  supplied is correct or not.
  
--- 1004,1012 ----
  
  After the header is decrypted,  the last 1 or 2 bytes in Buffer
  should be the high-order word/byte of the CRC for the file being
! decrypted, stored in Intel low-byte/high-byte order, or the high-order
! byte of the file time if bit 3 of the general purpose bit flag is set.
! Versions of PKZIP prior to 2.0 used a 2 byte CRC check; a 1 byte CRC check is
  used on versions after 2.0.  This can be used to test if the password
  supplied is correct or not.
  
