X-Spam-Check-By: sourceware.org
Message-ID: <BAY125-F11FEC27B19D7CFF77C29F5B5250@phx.gbl>
X-Sender: karlm30 AT hotmail DOT com
In-Reply-To: <000d01c7a928$943118a0$2e08a8c0@CAM.ARTIMI.COM>
From: "Karl M" <karlm30 AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Subject: RE: Certain files in the system32 directory are not listed
Date: Thu, 07 Jun 2007 21:10:57 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-IsSubscribed: yes
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

Hi All...

>Subject: RE: Certain files in the system32 directory are not listed
>Date: Thu, 7 Jun 2007 18:23:35 +0100
>
>On 07 June 2007 17:55, John Cooper wrote:
>
> > 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."
>
>   Argh.  I guess we have to extend the old joke: these days, Windows is a
>64-bit file-system redirection on top of a 32-bit patch to a 16-bit shell 
>for
>an 8-bit operating system written for a 4-bit processor by a two-bit 
>company
>without one bit of sense!
>
> > Perhaps something similar should be added to cygwin, as otherwise it's
> > impossible to access any files in the "real" system32 directory.
>
>   Conceivably we could insert a call to
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/wow
>64disablewow64fsredirection.asp
>
>but who knows what it might break?  We'd have to do a lot of testing first.
>
> > Incidentally, would cygwin be able to exec such 64-bit programs?
>
>   Well, if calling CreateProcess works on them the same as it does for 
>32-bit
>programs, it /ought/ to work, but GOK what M$ might or might not have done
>behind the scenes to sabotage us.  For example, cygwin won't be able to 
>exec a
>64-bit program if the O/S fakes us out that the .exe isn't even visible ...
>
So the danger is near that you run a rootkit cleanup package and it removes 
your M$ OS! ;-)

...Karl

_________________________________________________________________
Picture this – share your photos and you could win big!  
http://www.GETREALPhotoContest.com?ocid=TXT_TAGHM&loc=us


--
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/