From: Steven Noonan <steven@uplinklabs.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Geoffrey Lee <geoffreyj.lee@gmail.com>, git@vger.kernel.org
Subject: Re: Anyone have access to 64-bit Vista?
Date: Tue, 27 Jan 2009 15:01:06 -0800 [thread overview]
Message-ID: <f488382f0901271501y2cf6dd84idc96e14aea1693e5@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0901272350360.3586@pacific.mpi-cbg.de>
On Tue, Jan 27, 2009 at 2:51 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 27 Jan 2009, Geoffrey Lee wrote:
>
>> On Tue, Jan 27, 2009 at 10:24 AM, Stephen Haberman
>> <stephen@exigencecorp.com> wrote:
>> > It kind of works on my Vista 64-bit system--I do not see the shell
>> > extensions in the native Windows Explorer (which is 64 bit), but I do
>> > see the shell extensions in an Explorer replacement I use (Xplorer2)
>> > that is 32-bit.
>> >
>> > I've seen other oddities in 32-bit vs. 64-bit programs--e.g. my alt tab
>> > replacement (Joe), which is 32-bit, works great with 32-bit programs
>> > but cannot remove focus from 64-bit programs (IE, Windows Explorer,
>> > etc.). Ironically, very few of the programs I use are 64-bit, so I get
>> > by with the alt tab replacement.
>> >
>> > - Stephen
>> >
>>
>> Thanks! It seems that 64-bit explorer.exe will not load 32-bit shell
>> extensions. At least now I know I'm not going crazy. :)
>
> How could it? You cannot have 32-bit code and 64-bit code running in the
> same process. At least not with x86_64 (AFAIK).
>
Correct, this is also my biggest gripe with how x86_64 is implemented.
Thank you, AMD!
- Steven
next prev parent reply other threads:[~2009-01-27 23:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 9:30 Anyone have access to 64-bit Vista? Geoffrey Lee
2009-01-27 18:24 ` Stephen Haberman
2009-01-27 22:41 ` Geoffrey Lee
2009-01-27 22:51 ` Johannes Schindelin
2009-01-27 23:01 ` Steven Noonan [this message]
2009-01-27 23:11 ` Johannes Schindelin
2009-01-27 23:15 ` Steven Noonan
2009-01-27 23:59 ` Geoffrey Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f488382f0901271501y2cf6dd84idc96e14aea1693e5@mail.gmail.com \
--to=steven@uplinklabs.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=geoffreyj.lee@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).