Wrong links in Outlook Express x64

janlafata · #1 (**permalink**) 16-07-2008, 06:33 PM

I have Windows XP Pro x64. Because of that stupid problem with there being no Adobe flash avaiable for the x64 Internet Explorer, I use the x32 IE.

Problem is Outlook Express is x64 bit and when I go to open up an Internet Explorer link, it opens up with the x64 Internet Explorer.

How do I get it to open up with the x32 Internet Explorer?

Thanks

jephree · #2 (**permalink**) 17-07-2008, 12:27 AM

OE will open links in the Default Browser.

You need to make IE x32 the Default Browser.

start > Set Program Access and Defaults

janlafata · #3 (**permalink**) 17-07-2008, 02:22 AM

jephree

I tried it but it didn't work. In XP I opened up Program Access and Defaults, then I clicked on Custom where it says "Choose a default Web Browser. It was set on "Use my current browser" (see attached) but I changed it to Internet Explorer.

I saw no mention though of any option to choose between x64 and x32 IE. So then I clicked on OK, a brief, small little window came up and I thought that was that. But then when I opened a link in Outlook Express, it still opened with x64 IE.

When I went back into to Program Access and Defaults to check it, it was still set back on "Use my current browser" even though I had tried to change it.

I don't know if x64 Vista Basic has more of an option to change that, because I may be switching to that soon, but I'd still like to know if it's possible to do on XP x64.

Thanks

jephree · #4 (**permalink**) 17-07-2008, 02:27 AM

I have XP x64 on my gaming machine although I never use the internet on it.

However next time I fire it up (later tonight) I will see if I can change the options.

But anyway the OE behavior in itself cannot be changed. OE will open the Default browser. You could for example set it to Firefox if you were so inclined or any other browser.

I will post back if I find anything in my Default settings in x64.

jephree · #5 (**permalink**) 17-07-2008, 02:38 AM

On a quick search I find this:

Quote:

Why are there two Internet Explorers in Windows XP Professional x64 Edition?

Windows XP x64 includes a native 64-bit Internet Explorer and the 32-bit version of Internet Explorer. The 32-bit version of IE is for compatibility with 32-bit plug-ins like Macromedia and Java. Internet Explorer requires a plug-in to be the same "bitness" so a 32-bit plug-in can not be executed by the 64-bit Internet Explorer. As 32-bit plug-ins are the norm, Microsoft has made the 32-bit version of Internet Explorer the default. The 64 bit version of Internet Explorer must be manually executed.

jephree · #6 (**permalink**) 17-07-2008, 02:52 AM

Just some further notes found although they address why OE opens rather than Outlook:

Quote:

Actually, this doesn't surprise me. OE is 64-bit, Outlook is 32-bit. When
64-bit programs indirectly call other programs, they seem to always get the
64-bit version if there is one. I'm not sure what the workaround is, but I
suspect your best bet is to ask over on one of the developer groups.

Quote:

While inside a 32-bit program, you call 32-bit DLLS which is why Outlook
starts.
While inside a 64-bit program, you call 64-bit DLLS which is why Outlook
Express starts.
See this link: I think this is what you are running into:
http://msdn.microsoft.com/netframewo...t/default.aspx
NO loading 32-bit DLLs into 64-bit processes
NO loading 64-bit DLLs into 32-bit processes
NO loading 32-bit COM InProc servers into 64-bit processes
No loading 64-bit COM InProc servers into 32-bit processes
Remote procedure calls (RPC) ARE SUPPORTED between 64-bit and 32-bit
processes (both on the same computer and across computers)

The quoted link no longer works... sorry

But if the above holds I see no alternative here.

Of course if you have Office you can default Outlook rather than Outlook Express as your e-mail program.

Outlook being 32 bit would open the default 32 bit IE.

In addition as the above quote notates this is a process of .NET Framework verify that you have SP2 as well as all Updates from Windows Updates including the latest .NET Framework. Perhaps they have written in a fix.

...