1.7 installation failed (on network drive?)

[Thomas Wolff]

I took an extra drive to the lab this afternoon, with no good results.

Corinna Vinschen schrieb:
> 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)0xC000003AL)
>>>> #define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC000003BL)
>>>>
>>>> However, before the fatal error occurs, it's just
>>>> "STATUS_ACCESS_DENIED" in both cases.
>>>>
>>>> ...
>>>> Starting cygwin install, version 2.662
>>>> filemanip:NtCreateFile -> C000003B
>>>>         
>>> This one might be the actual problem.  What's the actual path given
>>> to NtCreateFile (in uname)?  Does it contain slashes maybe?
>>>       
>> There is "\??\/var" and occasional double and triple backslashes; ...
>>     
> ...
>
> Try the below patch, please.  I installed to an H:\cygwin directory
> fresh from scratch and it worked fine for me.  ...
>   
I did and the path name problems are gone, however, that's apparently 
not the problem. See log files.

Dave Korn wrote:
>   Nah, here's what to do.  You have no problem creating directories on this
> share otherwise, right?
Right. So why actually should setup not just use libc mkdir here?

>   So start up sysinternals filemon, set it to filter on
> "cygwin17", then in a cmd.exe shell window run "mkdir \?\H:\cygwin17p2", then
> run setup.exe and let it try and create H:\cygwin17p1, then let's compare the
> logs for those two events and see what flags each call was using.
Unfortunately, filemon needs to be started with admin rights. The system 
administrator even kindly did that (with runas), but thanks to MS weird 
concept of having mounts user-specific, the network drives were not 
mounted for admin so the tool did not trace them.
Grumble!
The system administrator did not feel like helping me futher out (e.g. 
starting a full admin session or even giving me the password...).
I'm very sorry about this; any alternative debugging idea?
I'm thinking about making a setup version that takes flags from an 
environment variable, so a number of options could be tried out more 
quickly, but this Nt function has so many parameters and options...
Any suggestion to get quicker results than a brute-force test is welcome.

Thomas
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: setup.log.rootdir-on-net
URL: <http://cygwin.com/pipermail/cygwin-apps/attachments/20091217/d48a484a/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: setup.log.packdir-on-net
URL: <http://cygwin.com/pipermail/cygwin-apps/attachments/20091217/d48a484a/attachment-0001.ksh>