Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-13 Thread EXCOFFIER Denis
Hello, This one is a follow-up for http://cygwin.com/ml/cygwin/2011-05/msg00183.html On 2011-05-12 09:47:15 -0600 Keith Christian wrote: This permissions problem has existed for awhile, and I'd like to find a solution. Same for me. CMD.EXE is able to create files inside directories on a

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-13 Thread Corinna Vinschen
On May 13 15:42, EXCOFFIER Denis wrote: Hello, This one is a follow-up for http://cygwin.com/ml/cygwin/2011-05/msg00183.html On 2011-05-12 09:47:15 -0600 Keith Christian wrote: This permissions problem has existed for awhile, and I'd like to find a solution. Same for me. CMD.EXE is

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-13 Thread Keith Christian
I asked our Windows admin to check permissions on the share. They are the same as everyone else's. I tried this entry in /etc/fstab, closed all Cygwin Bash windows, opened a window, unable to create files in /cygdrive/z or subdirectories within. Z: /cygdrive/z ntfs binary,noacl 0 0 Even when

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-13 Thread Corinna Vinschen
On May 13 10:27, Keith Christian wrote: I asked our Windows admin to check permissions on the share. They are the same as everyone else's. I tried this entry in /etc/fstab, closed all Cygwin Bash windows, opened a window, unable to create files in /cygdrive/z or subdirectories within.

CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-12 Thread Keith Christian
This permissions problem has existed for awhile, and I'd like to find a solution. CMD.EXE is able to create files inside directories on a standard Windows share, but from a Bash shell on Cygwin, a permission denied message occurs, and this is in most if not all directories: -bash:

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-12 Thread Larry Hall (Cygwin)
On 5/12/2011 11:47 AM, Keith Christian wrote: This permissions problem has existed for awhile, and I'd like to find a solution. CMD.EXE is able to create files inside directories on a standard Windows share, but from a Bash shell on Cygwin, a permission denied message occurs, and this is in

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-12 Thread Larry Hall (Cygwin)
On 5/12/2011 1:54 PM, Keith Christian wrote: Thank you for the reply, Larry. Requested output is either pasted or attached. Is the getVolInfo output from a network appliance or is it simply an internal disk on another Windows machine? Potential app conflicts: ZoneAlarm Personal Firewall

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-12 Thread Corinna Vinschen
On May 12 09:47, Keith Christian wrote: This permissions problem has existed for awhile, and I'd like to find a solution. CMD.EXE is able to create files inside directories on a standard Windows share, but from a Bash shell on Cygwin, a permission denied message occurs, and this is in most

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-12 Thread Corinna Vinschen
On May 12 15:01, Larry Hall (Cygwin) wrote: On 5/12/2011 1:54 PM, Keith Christian wrote: Thank you for the reply, Larry. Requested output is either pasted or attached. Is the getVolInfo output from a network appliance or is it simply an internal disk on another Windows machine? The flags

Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to

2011-05-12 Thread Corinna Vinschen
On May 12 15:17, Keith Christian wrote: Corinna, the bash.trace output is attached. Thank you for checking into this problem. But I can't really help. The problem is that the Windows call to open tjhe file simply fails: 39 146109 [main] bash 2020 fhandler_base::open: C022 = NtCreateFile