RE: Cygwin 3.1.X Fatal Errors - add_item ("\??\C:", "/", ...) failed, errno 22

2020-01-14 Thread Ken Turner
Thanks to Marco for the advice, and special thanks to Henri for additional support. As noted on https://cygwin.com/ml/cygwin/2020-01/msg00129.html, my problem was due to installing Cygwin in the drive root. I was forced to do this some years ago because of a third-party package that required Cy

Cygwin 3.1.X Fatal Errors - add_item ("\??\C:", "/", ...) failed, errno 22

2020-01-12 Thread Ken Turner
This is related to https://cygwin.com/ml/cygwin/2020-01/msg00045.html. I have now tried the same update on two other systems. Cygwin 3.0.7-1 32-bit works fine on three different systems: one Windows 7 64-bit, two Windows 10 64-bit. However, Cygwin 3.1.1-1 and 3.2.1-1 fail to install cleanly on the

Cygwin 3.1.X causes fatal errors

2020-01-06 Thread Ken Turner
I have Windows 10 64-bit, but am using the 32-bit version of Cygwin for historical reasons. I seem to have the same problem noted in https://www.mail-archive.com/cygwin@cygwin.com/msg162929.html. That is, installation of Cygwin 3.1.X fails in post-processing. The setup log shows (in part): 2020/01

Cygwin 3.1.X causes fatal errors

2020-01-05 Thread Ken Turner
I have Windows 10 64-bit, but am using the 32-bit version of Cygwin for historical reasons. I seem to have the same problem noted in https://www.mail-archive.com/cygwin@cygwin.com/msg162929.html. That is, installation of Cygwin 3.1.X does not work properly. The setup log shows (in part): 2020/01/0

w32api-runtime-4.0.2-1 fails to install

2015-05-25 Thread Ken Turner
w32api-runtime-4.0.2-1 fails during installation with "unable to extract /pypy-c.exe.stackdump". Clicking Retry causes a repeat of the same message, and clicking Continue causes setup to hang. This appears to be due to a stray file "pypy-c.exe.stackdump" at the top level of the package. Removing t

RE: Mapping of Windows Domains?

2008-07-23 Thread Ken Turner
| >>> It turns out that these files are being served up with a fake domain | >>> name "D1" (because our Unix server isn't part of a Windows domain). | >>> When I log in I am authenticated against a real domain "D2". As a | >>> result, "D2\kjt" cannot access files whose permissions are set for | >>>

RE: Mapping of Windows Domains?

2008-07-23 Thread Ken Turner
| > It turns out that these files are being served up with a fake domain name | > "D1" (because our Unix server isn't part of a Windows domain). When I log | > in I am authenticated against a real domain "D2". As a result, "D2\kjt" | > cannot access files whose permissions are set for "D1\kjt". The

Mapping of Windows Domains?

2008-07-23 Thread Ken Turner
I've posted on this problem before (http://www.cygwin.com/ml/cygwin/2006-11/msg00568.html) but now have a better idea of what's going wrong. (I haven't supplied "cygcheck" output as my question is generic.) Our Unix file server uses the TAS program to deliver files via SMB to Windows clients. Up t

Re: Cygwin > 1.5.18-1 fails on network and removable drives

2006-11-29 Thread Ken Turner
Thanks for the suggestion about running strace. My home directory is accessed as a Windows share (drive H:) via SMB from a Unix server (TAS). Here is a typical sequence using the latest version of all Cygwin components: kjt:/c cd /h kjt:/h echo $CYGWIN ntsec nosmbntsec kjt:/h ls ls: reading dire