Logged In: YES 
user_id=21627

I looked at the "compatible with DOS" issue again, and I
think the story is this:

The low-order byte of the external file attributes are the
DOS bits (read-only, hidden, system, directory); one can
claim compatibility if these bits have the right values. The
Unix bits are the higher 16 bits, and can have indepedent
values.

InfoZIP (on Unix) will use the Unix bits as is-if the
creator system is UNIX, VMS, ACORN, ATARI, ATHEOS, BEOS,
QDOS or TANDEM. For FAT (0), it will use the Unix bits if
they are "consistent" with the DOS bits. In all other cases
(including NTFS and MAC), it will use the DOS bits.

"consistent" is defined wrt. the U bits: the DOS directory
bit must be the same as the u+x bit, and the u+w bit must be
the negated read-only bit.

If only the DOS bits are used, they are used to synthesize
POSIX bits: u,g,o get all the same bits, the w bits are
derived from read-only, and the x bit is derived from the
subdir bit.

As for -X (restore UID/GID): They come from the PK Unix
extra field (0x000d), the InfoZip Unix extra field (0x5855)
or the InfoZIP Unix2 extra field (0x7855). We currently
don't create any of these, so this option in unzip won't
have any effect.