X-Spam-Check-By: sourceware.org
X-IronPort-AV: E=Sophos;i="4.16,395,1175468400";     d="scan'208";a="9788475"
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Certain files in the system32 directory are not listed
Date: Thu, 7 Jun 2007 17:54:37 +0100
Message-ID: <DD74FBB8EE28D441903D56487861CD9D097177C5@lonpexch01.citrite.net>
In-Reply-To: <DD74FBB8EE28D441903D56487861CD9D097177C4@lonpexch01.citrite.net>
From: "John Cooper" <john DOT cooper AT eu DOT citrix DOT com>
To: <cygwin AT cygwin DOT com>
Cc: "John Cooper" <john DOT cooper AT eu DOT citrix DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l57GtFnJ006339

Dave Korn wrote:

> > (could that fact that I'm using x64 be contributing to the problem?)
>   Unlikely to be related.

It turns out that x64 is indeed causing the discrepancy.
From http://msdn.microsoft.com/msdnmag/issues/06/05/x64/default.aspx :

"File activity from a Win32 process that would normally go to the
System32 directory instead goes to a directory named SysWow64."

.. so accessing c:/windows/system32' in 32-bit cygwin (zsh or bash)
actually gets silently redirected to the c:/windows/syswow64 directory.
By default, cmd.exe runs in 64-bit mode and `dir' then displays the
contents of the "real" c:/windows/system32 directory. (in fact, running
cmd.exe from zsh invokes cmd in 32-bit mode and `dir' is then redirected
to the syswow64 directory.)

It seems the MKS tools turn off this redirection by default, and
provides an env variable (TK_WOW64FSREDIR_ON) for enabling it:
http://www.mkssoftware.com/docs/man5/envvar.5.asp

Perhaps something similar should be added to cygwin, as otherwise it's
impossible to access any files in the "real" system32 directory.
Incidentally, would cygwin be able to exec such 64-bit programs?

Thanks,

    --- John.

-----Original Message-----
From: John Cooper 
Sent: 07 June 2007 12:13
To: 'cygwin AT cygwin DOT com'
Cc: John Cooper
Subject: Certain files in the system32 directory are not listed

Some files that exist in the C:/WINDOWS/system32 directory are not
listed when running `ls' or `echo' from a cygwin bash or zsh shell.
Examples include mstsc.exe and iisapp.vbs.

These files are both listed when running 'dir' in a Windows cmd prompt -
they also do not seem to be "hidden" according to `attrib' and `dir /a'.

Cygwin `ls' lists 1757 files in this directory whereas cmd's `dir' lists
1804.
Does anyone know what might be causing this?

I'm running on Windows Server 2003 SP1 (x64) and appear to have Cygwin
1.5.24-2.
(could that fact that I'm using x64 be contributing to the problem?)

Thanks,

    --- John

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/