On Dec 21 21:10, Thomas Wolff wrote:
[resending without attachments which got spam-blocked]
Corinna Vinschen schrieb:
On Dec 18 16:08, Thomas Wolff wrote:
Corinna Vinschen schrieb:
On Dec 18 11:57, Corinna Vinschen wrote:
On Dec 17 17:31, Corinna Vinschen wrote:
I applied a patch which
[resending without attachments which got spam-blocked]
Corinna Vinschen schrieb:
On Dec 18 16:08, Thomas Wolff wrote:
Corinna Vinschen schrieb:
On Dec 18 11:57, Corinna Vinschen wrote:
On Dec 17 17:31, Corinna Vinschen wrote:
I applied a patch which falls back to
On Dec 17 17:31, Corinna Vinschen wrote:
I applied a patch which falls back to opening/creating the file/dir
without WRITE_DAC if the first call failed. That's not quite optimal
but it works. Please check out the latest from CVS and test in your
scenario. For me it works now on the share as
On Dec 18 11:57, Corinna Vinschen wrote:
On Dec 17 17:31, Corinna Vinschen wrote:
I applied a patch which falls back to opening/creating the file/dir
without WRITE_DAC if the first call failed. That's not quite optimal
but it works. Please check out the latest from CVS and test in your
Corinna Vinschen schrieb:
On Dec 18 11:57, Corinna Vinschen wrote:
On Dec 17 17:31, Corinna Vinschen wrote:
I applied a patch which falls back to opening/creating the file/dir
without WRITE_DAC if the first call failed. That's not quite optimal
but it works. Please check out the
On Dec 18 16:08, Thomas Wolff wrote:
Corinna Vinschen schrieb:
On Dec 18 11:57, Corinna Vinschen wrote:
On Dec 17 17:31, Corinna Vinschen wrote:
I applied a patch which falls back to opening/creating the file/dir
without WRITE_DAC if the first call failed. That's not quite optimal
but it
On Dec 17 02:12, Thomas Wolff wrote:
I took an extra drive to the lab this afternoon, with no good results.
[...]
mkdir:NtCreateFile - 0
\??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f
filemanip:NtCreateFile - 0
Corinna Vinschen wrote:
On Dec 17 02:12, Thomas Wolff wrote:
I took an extra drive to the lab this afternoon, with no good results.
[...]
mkdir:NtCreateFile - 0
\??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f
filemanip:NtCreateFile -
On Dec 17 12:17, Thomas Wolff wrote:
Corinna Vinschen wrote:
On Dec 17 02:12, Thomas Wolff wrote:
I took an extra drive to the lab this afternoon, with no good results.
[...]
mkdir:NtCreateFile - 0
On Dec 17 14:09, Corinna Vinschen wrote:
Has the H:\cygwin17 directory been created at all? If so, we should
examine the cacls for this dir just like the cacls for H:\ itself.
Hmm.
[...time passes...]
Hang on, there's another possible reason for STATUS_ACCESS_DENIED.
Mkdir_p calls
Corinna Vinschen wrote:
On Dec 17 14:09, Corinna Vinschen wrote:
Has the H:\cygwin17 directory been created at all? If so, we should
examine the cacls for this dir just like the cacls for H:\ itself.
No, it hasn't. For some ACLs, see below.
Hmm.
[...time passes...]
Hang on,
On Dec 17 14:38, Corinna Vinschen wrote:
On Dec 17 14:09, Corinna Vinschen wrote:
Has the H:\cygwin17 directory been created at all? If so, we should
examine the cacls for this dir just like the cacls for H:\ itself.
Hmm.
[...time passes...]
Hang on, there's another possible
Corinna Vinschen schrieb:
On Dec 11 12:52, Thomas Wolff wrote:
Corinna Vinschen wrote:
#define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL)
#define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL)
However, before the fatal error occurs, it's just
STATUS_ACCESS_DENIED in both
Corinna Vinschen schrieb:
On Dec 11 12:52, Thomas Wolff wrote:
Corinna Vinschen wrote:
#define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL)
#define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL)
However, before the fatal error occurs, it's just
STATUS_ACCESS_DENIED in both
Thomas Wolff wrote:
Current Directory: h:\
User has NO backup/restore rights
Could not open Service control manager
source: network install
root: H:\cygwin17 binary user
filemanip:NtCreateFile - C03A
\??\H:\cygwin17\etc\setup\installed.db
io_stream_cygfile:
On Dec 15 15:33, Dave Korn wrote:
Thomas Wolff wrote:
Current Directory: h:\
User has NO backup/restore rights
Could not open Service control manager
source: network install
root: H:\cygwin17 binary user
filemanip:NtCreateFile - C03A
\??\H:\cygwin17\etc\setup\installed.db
Thomas Wolff wrote:
Dave Korn wrote:
Thomas Wolff wrote:
Selected local directory: H:\cygwin17p1
mkdir:NtCreateFile - C022
mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive
full or read-only?)
So that's coming from here:
status = NtCreateFile (dir,
On Dec 15 15:25, Thomas Wolff wrote:
Corinna Vinschen schrieb:
On Dec 11 12:52, Thomas Wolff wrote:
Corinna Vinschen wrote:
#define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL)
#define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL)
However, before the fatal error occurs,
2009/12/15 Corinna Vinschen:
\?? is a shortcut for the DOS device subdirectory in the native NT
namespace. C:\foo in DOS is \??\C:\foo in native NT speak.
\\server\share in DOS is \??\UNC\server\share.
Shouldn't that be '\\?' rather than '\??' though?
On Dec 15 16:27, Andy Koppe wrote:
2009/12/15 Corinna Vinschen:
\?? is a shortcut for the DOS device subdirectory in the native NT
namespace. C:\foo in DOS is \??\C:\foo in native NT speak.
\\server\share in DOS is \??\UNC\server\share.
Shouldn't that be '\\?' rather than '\??' though?
Dave Korn wrote:
Thomas Wolff wrote:
Selected local directory: H:\cygwin17p1
mkdir:NtCreateFile - C022
mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full or
read-only?)
So that's coming from here:
status = NtCreateFile (dir,
On Dec 11 12:52, Thomas Wolff wrote:
Corinna Vinschen wrote:
#define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL)
#define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL)
However, before the fatal error occurs, it's just
STATUS_ACCESS_DENIED in both cases.
What we need is
On Dec 14 16:21, Thomas Wolff wrote:
Dave Korn wrote:
Thomas Wolff wrote:
Selected local directory: H:\cygwin17p1
mkdir:NtCreateFile - C022
mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full
or read-only?)
So that's coming from here:
status =
I wrote:
Dave Korn wrote:
Thomas Wolff wrote:
Selected local directory: H:\cygwin17p1
mkdir:NtCreateFile - C022
mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is
drive full or read-only?)
So that's coming from here:
status = NtCreateFile (dir,
Corinna Vinschen wrote:
Thomas,
On Dec 7 17:09, Thomas Wolff wrote:
I've tested the network installation with last Saturday's update of
setup-1.7.exe and unfortunately, the problem remains.
However, I can add a screen log after calling setup from mintty for
the case that setup cannot even
Thomas Wolff wrote:
Selected local directory: H:\cygwin17p1
mkdir:NtCreateFile - C022
mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full or
read-only?)
So that's coming from here:
status = NtCreateFile (dir,
Corinna Vinschen wrote:
cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup
CC=gcc-3 configure
make 'CFLAGS=-g'
So I don't need to switch set-gcc-default-3.sh, thanks.
Actually, I already checked out and compiled (after installing a
bunch of dependencies) over night after cgf's
On Thu, Dec 10, 2009 at 08:19:50PM +, Dave Korn wrote:
Corinna Vinschen wrote:
cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup
CC=gcc-3 configure
make 'CFLAGS=-g'
So I don't need to switch set-gcc-default-3.sh, thanks.
Actually, I already checked out and compiled (after
Christopher Faylor wrote:
On Thu, Dec 10, 2009 at 08:19:50PM +, Dave Korn wrote:
Corinna Vinschen wrote:
cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup
CC=gcc-3 configure
make 'CFLAGS=-g'
So I don't need to switch set-gcc-default-3.sh, thanks.
Actually, I already checked
On Dec 8 18:21, Thomas Wolff wrote:
Corinna Vinschen schrieb:
So the fopen calls fail. fopen in setup is actually a call to nt_wfopen
in filemanip.cc. If you could take a look, it's not a very complicated
function. The general idea is to call NtCreateFile with
FILE_OPEN_FOR_BACKUP_INTENT
Corinna Vinschen wrote:
On Dec 8 18:21, Thomas Wolff wrote:
Corinna Vinschen schrieb:
... Build a debug version of setup (you need gcc-3
for that since the -mno-cygwin option is still used), start it under
GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if
an
On Dec 9 11:52, Thomas Wolff wrote:
Corinna Vinschen wrote:
On Dec 8 18:21, Thomas Wolff wrote:
Corinna Vinschen schrieb:
... Build a debug version of setup (you need gcc-3
for that since the -mno-cygwin option is still used), start it under
GDB, and set a breakpoint to filemanip.cc:468.
Thomas,
On Dec 7 17:09, Thomas Wolff wrote:
I've tested the network installation with last Saturday's update of
setup-1.7.exe and unfortunately, the problem remains.
However, I can add a screen log after calling setup from mintty for
the case that setup cannot even store its log anywhere
Corinna Vinschen schrieb:
Thomas,
On Dec 7 17:09, Thomas Wolff wrote:
I've tested the network installation with last Saturday's update of
setup-1.7.exe and unfortunately, the problem remains.
However, I can add a screen log after calling setup from mintty for
the case that setup cannot
On Tue, Dec 08, 2009 at 06:21:00PM +0100, Thomas Wolff wrote:
OK; since setup is not a cygwin package, where would I get the sources
in the first place? And is there a README telling me how to build a
debug version (make debug?)?
If you google setup.exe source code the first hit should answer
I've tested the network installation with last Saturday's update of
setup-1.7.exe and unfortunately, the problem remains.
However, I can add a screen log after calling setup from mintty for the
case that setup cannot even store its log anywhere (attached).
Don't know if that helps. Apparently
Corinna Vinschen schrieb:
On Nov 25 18:30, Dave Korn wrote:
Thomas Wolff wrote:
Corinna Vinschen wrote:
Are you sure the share permissions are sufficient? In contrast to the
1.5 setup, the 1.7 setup tries to create files and directories with
explicit ACLs.
On the H:
ext Corinna Vinschen wrote:
On Nov 24 18:21, Thomas Wolff wrote:
I tried this installation to a network drive on one machine again
with last week's new setup.exe, which didn't solve the problem as
Corinna had assumed, but with more detailed test results:
The machine runs Windows XP
Thomas Wolff wrote:
ext Corinna Vinschen wrote:
Are you sure the share permissions are sufficient? In contrast to the
1.5 setup, the 1.7 setup tries to create files and directories with
explicit ACLs.
On the H: drive, I have full access according to the Windows
properties dialog.
On the
On Nov 25 18:30, Dave Korn wrote:
Thomas Wolff wrote:
ext Corinna Vinschen wrote:
Are you sure the share permissions are sufficient? In contrast to the
1.5 setup, the 1.7 setup tries to create files and directories with
explicit ACLs.
On the H: drive, I have full access according to
Dave Korn schrieb:
...
Say, has anyone checked it's still possible to install to a FAT fs using the
latest setup.exe? I might try digging up a pen drive later tonight and see
what happens.
Works (FAT32 @ USB).
Thomas
Thomas Wolff wrote:
Dave Korn schrieb:
...
Say, has anyone checked it's still possible to install to a FAT fs
using the
latest setup.exe? I might try digging up a pen drive later tonight
and see
what happens.
Works (FAT32 @ USB).
Thanks for testing :)
cheers,
DaveK
I tried this installation to a network drive on one machine again with
last week's new setup.exe, which didn't solve the problem as Corinna had
assumed, but with more detailed test results:
The machine runs Windows XP Professional, drvies H: and T: are normal
Windows mounts or NFTS network
On Nov 24 18:21, Thomas Wolff wrote:
I tried this installation to a network drive on one machine again
with last week's new setup.exe, which didn't solve the problem as
Corinna had assumed, but with more detailed test results:
The machine runs Windows XP Professional, drvies H: and T: are
I wanted to install 1.7 on another machine, target directory
H:\cygwin, but it failed with the attached error.
I had to reinstall 1.5, which I did to the same location and
it worked seamlessly.
Is there a problem installing 1.7 to a network drive?
Thomas
cygwin-install-error.png
Thomas Wolff wrote:
I wanted to install 1.7 on another machine, target directory
H:\cygwin, but it failed with the attached error.
Handy hint for next time: Did you know you can copy and paste most windows
popup error dialogs? Just press Ctrl+C while the dialog is selected, and then
when
46 matches
Mail list logo
