This is the mail archive of the
mailing list for the Cygwin project.
RE: Certain files in the system32 directory are not listed
- From: "Karl M" <karlm30 at hotmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 07 Jun 2007 21:10:57 -0700
- Subject: RE: Certain files in the system32 directory are not listed
So the danger is near that you run a rootkit cleanup package and it removes
your M$ OS! ;-)
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
an 8-bit operating system written for a 4-bit processor by a two-bit
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
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
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
64-bit program if the O/S fakes us out that the .exe isn't even visible ...
Picture this ? share your photos and you could win big!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html