BL> I suspect that Linux allocates the read-only bit to "owner" and
BL> leaves "group" out altogether, making group *always* read-only.
BL> Executable becomes the DOS "system" bit.

JB> the umask effects what permissions owner, group, and everyone
JB> else gets. 

 I fear not. umask is over-ridden by the actual Linux permissions.
For isntance, if I mount the drive as root, and then set umask=777 to
give *everyone* total access, it still denies *anyone* but root. To
get access to the windwos drives, I have ot mount them using uid= and
gid=xxx.

JB> in each digit the 1 bit is for execute, the 2 bit foe write and
JB> the 4 bit for read permission. eg: 777 give all permission to
JB> everone, 644 lets only the owner write and everyone may read. I
JB> don't think execute permission effects wethere a windows user
JB> of a samba mount may run the file. (there are other bits but I
JB> forget which does what, and i don';t think they are relevant to
JB> mounting dos filesystems) 

 Samba can only work on what already exists, in both the Linux and
Windows files

Regards,
Bob
.   

--- BQWK Alpha 0.5