none
Has the implementation of the 32-bit Windows Explorer changed in the RC?

    Question

  • When I run

     c:\windows\syswow64\explorer /separate

    the task manager does not show it as being a 32-bit process.

    It was being shown as such in build 7000.

    Is it no longer a 32-bit process?

    TIA
    Wednesday, May 06, 2009 2:54 PM

Answers

  • I've filed a bug on Win7 RC over this issue:

    https://connect.microsoft.com/windows7/feedback/ViewFeedback.aspx?FeedbackID=465910

    Please validate and vote!
    Thomas Lee
    • Marked as answer by Dave English Wednesday, June 10, 2009 12:46 PM
    Wednesday, June 10, 2009 12:07 PM

All replies

  • Do you see two explorer.exe processes in the Resource Monitor? (run 'perfmon /res' )
    Rating posts helps other users
    Mark L. Ferguson MS-MVP
    Sunday, May 10, 2009 5:10 PM
    Moderator
  • So sorry, I missed your reply to my question until now :-(
    Do you see two explorer.exe processes in the Resource Monitor? (run 'perfmon /res' )
    For a while I see three explorer.exe processes.

    Here is what I do:

    1/ Start a cmd
    2/ In cmd, perfmon /res
    3/ Sort perfmon columns on Image
     a) I see only one explorer.exe process, for example PID 844
    4/ Select Platform column be displayed
    5/ In cmd, cd \window\syswow64
    6/ In cmd, explorer /separate
     a/ See a new explorer.exe process, 32-bit platform, for example PID 1364
     b/ See a new explorer.exe process, 64-bit platform, for example PID 2436
     c/ The fresh Explorer Window is on the screen
     c/ At this point there are tree explorers, two 64-bit & one 32-bit
    7/ By now, the 32-bit explorer is being displayed in feint text
    8/ A minute or so later, the 32-bit explore.exe process disappears
     a/ There are now only two explorer.exe processes, both 64-bit platform, PIDs say 844 & 2436
     b/ The fresh Explorer window is still on the screen
    9/ Close the fresh Explorer window
     a/ The fresh Explorer window is no longer on screen
     b/ The explorer.exe PID 2436 now shown in feint text
    10/ A minute or so later, PID 2436 disappears
     a/ There is now only one explorer.exe proess, PID 844

    Is there anything further I can do to diagnose this, please?
    Thursday, May 28, 2009 9:50 AM
  • So sorry, I missed your reply to my question until now :-(
    FWIW, I think I have found that I needed to configure alerts after my e-mail address had been verified, in order for alerts to work.

    Ho, hum
    Thursday, May 28, 2009 10:13 AM
  • Do you see two explorer.exe processes in the Resource Monitor? (run 'perfmon /res' )
    Mark L. Ferguson MS-MVP
    This is not the answer - sadly I can't rate the post down.

    In general, unless the answer really is the answer, MVPs should not be marking their replies as the answer. In this case, there is an underlying problem with Win7 RC and running resource monitor is not the answer.

    Thomas Lee
    • Edited by Thomas Lee Thursday, May 28, 2009 11:13 AM
    Thursday, May 28, 2009 11:10 AM
  • Thomas,

    Although I haven't seen any documentation of this, my explorer.exe also identifies itself as a 64-bit process in the RC, and this wasn't the case in the beta.

    -Alex
    Thursday, May 28, 2009 12:55 PM
  • Mark, why did you mark this answered, please?

    I asked whether the it was no longer a 32-bit process, Alex said he saw the same as me & you marked this answered.  That can't be all that there is to it.

    Regards
    Tuesday, June 02, 2009 5:38 PM
  • Dave,

    Not being in constant contact with the developers, I'd take this at face value - at the time of the beta, Windows Explorer did not yet have a 64-bit implementation, and now does.
    -Alex
    Tuesday, June 02, 2009 6:13 PM
  • Dave,

    Not being in constant contact with the developers, I'd take this at face value - at the time of the beta, Windows Explorer did not yet have a 64-bit implementation, and now does.
    -Alex
    Sorry, but I don't think that you quite understand.  There has been a 64-bit implementation of Windows Explorer ever since Windows XP 64-bit, Windows Vista 64-bit has it, the RC-7000 Beta has it.

    However, all of the 64-bit Windows systems have had 32-bit implementation in syswow64, for compatibility with 32-bit extensions.  It is that I need.  What appears to happen on the RC is that the 32-bit explorer starts, spawns a 64-bit explorer, then dies leaving only the 64-bit explorer.  If that is the "face", then I would need an explanation to understand how I can still have 32-bit compatibility.

    Do you see?
    Tuesday, June 02, 2009 6:50 PM
  • I can verify this.

    I have an icon on my desktop i made with %windir%\syswow64\explorer.exe /separate as the command line.

    In Windows 7 x64 RC and Server 2008 R2 x64 RC it shows up in taskmgr identified as explorer and with the command line c:\windows\explorer.exe /factory,{guid} -Embedding, whether it is started from my 32bit icon, or using Win+E.

    In Vista x64 SP2, Server 2008 SP2 x64, Server 2003 R2 x64, and presumably XP, it shows up with C:\Windows\SysWow64\explorer.exe /separate, and is identified as explorer *32.

    If, in Vista, you double click explorer.exe in the folder C:\Windows\SysWow64 it will open a 64 bit instance of explorer, even if you do it in a 32 bit window.  Go figure.

    Note, I do have desktop process enabled.
    • Marked as answer by axfelix Tuesday, June 02, 2009 11:16 PM
    • Unmarked as answer by Dave English Thursday, June 04, 2009 9:21 AM
    Tuesday, June 02, 2009 7:59 PM
  • If, in Vista, you double click explorer.exe in the folder C:\Windows\SysWow64 it will open a 64 bit instance of explorer, even if you do it in a 32 bit window.  Go figure.
    That is because when you do that, SysWow64\explorer.exe is invoked without a /separate .  In that case the 32bit explorer will get the 64-bit explorer to display a fresh window & then exit.

    You can demonstrate this on Vista SP2 x64 by comparing the effect from the command line of:

    C:\> C:\Windows\SysWow64\explorer.exe /separate

    which opens a 32-bit explorer window as against:

    C:\> C:\Windows\SysWow64\explorer.exe

    which opens a 64-bit one.

    Do you see?


    Thursday, June 04, 2009 9:29 AM
  • I've filed a bug on Win7 RC over this issue:

    https://connect.microsoft.com/windows7/feedback/ViewFeedback.aspx?FeedbackID=465910

    Please validate and vote!
    Thomas Lee
    • Marked as answer by Dave English Wednesday, June 10, 2009 12:46 PM
    Wednesday, June 10, 2009 12:07 PM
  • Thanks Thomas

    Unfortunately I don't think I can't  vote on that myself as I'm not a Beta tester for Windows 7 on Microsoft Connect :-(

    Perhaps others here can?
    Wednesday, June 10, 2009 12:46 PM
  • I see the same thing. A new explorer.exe is created, but it's 64bit - not 32bit.
    I can't vote on the bug report created though as I don't have access. :(

    I came across this when trying to get TortoiseHG to work. http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/f4b5f006-cb83-4adb-8edc-af8ea0ee0c8b
    -Cheers!
    Monday, June 15, 2009 12:02 PM
  • I've filed a bug on Win7 RC over this issue:

    https://connect.microsoft.com/windows7/feedback/ViewFeedback.aspx?FeedbackID=465910

    Please validate and vote!
    Thomas Lee
    Unfortunately, the bug has been closed as 'won't fix'.

    For me, this means I either have to upgrade to new mail/news clients to use Win7, or I have to go back to XP.


    Thomas Lee
    • Edited by Thomas Lee Saturday, October 03, 2009 2:31 PM
    Thursday, June 25, 2009 2:22 PM
  • I wonder if the rest of the people here, that haven't been able to submit a bugreport or data might have had some info that could have changed that... :/

    -Cheers!
    Thursday, June 25, 2009 3:09 PM
  • I can't believe they made such a huge regression without more documentation.  The biggest issue for me is 32bit shell extensions.  There is no way to run them now.  Acrobat PDF thumbnails no longer work (I used to spawn a 32bit explorer to generate them, which is no longer possible).  Boo!
    Saturday, August 15, 2009 7:31 PM
  • Wait I really need 32 bit shell extensions to work as well. So there is no longer a 32 bit window explorer?

    Wednesday, September 16, 2009 8:27 PM
  • Wait I really need 32 bit shell extensions to work as well.

    Sorry to hear that.

    So there is no longer a 32 bit window explorer?

    I suppose we will have to wait for SP1.

    I have read elsewhere that extensions can still work inside the file open dialog of a 32-bit application, if that is of any use to you, but I have not tried it myself.

    Regards

    Thursday, September 17, 2009 7:09 AM
  • Wait I really need 32 bit shell extensions to work as well. So there is no longer a 32 bit window explorer?


    It's there.  But I don't know if it will work for your needs.

    C:\Windows\SysWOW64>filever explorer.exe
    --a-- W32i   APP ENU      6.1.7100.0 shp  2,607,616 04-22-2009 explorer.exe

    C:\Windows\SysWOW64>filever C:\Windows\explorer.exe
    --a-- Wx64 APP ENU      6.1.7100.0 shp  2,858,496 04-22-2009 explorer.exe

    Thursday, September 17, 2009 11:35 PM
  • Yes Brian but you will find that if you launch that 32-bit EXE it will spawn the 64-bit variant and then exit, leaving you with only a 64-bit explorer.exe running.  There doesn't seem to be any way around this.
    Friday, September 18, 2009 2:29 AM
  • I suppose we will have to wait for SP1.

    I have read elsewhere that extensions can still work inside the file open dialog of a 32-bit application, if that is of any use to you, but I have not tried it myself.

    Regards

    Do we know if this bug will get considered for SP1, or even if there is a hot fix available?

    Thomas Lee - EMAIL REMOVED
    Thursday, October 08, 2009 11:23 AM
  • So you're saying you've confirmed that Microsoft does not allow a 32 bit Explorer window to run in Windows 7 x64 and is not planning to fix this?

    Unbelievable!  <shakes head>

    Like you, I prefer the 32 bit Explorer in Vista x64 (and before that in XP x64) to allow me to integrate moderately old extenders (in layman's terms, lots of useful things on the right mouse button, for example).  It also SERIOUSLY separates the Explorer window operations from anything to do with the desktop.

    Have Microsoft lost their minds?  Who's making the decisions to remove this stuff?

    They already had it working in XP x64 and Vista x64, so no one can claim it's hard to do.

    If they think this is a proper way to nudge people to migrate to true 64 bit apps, well, I suppose that's one way to do it.  They might just migrate to OSX or Linux though.

    -Noel
    Friday, October 09, 2009 2:12 AM
  • So you're saying you've confirmed that Microsoft does not allow a 32 bit Explorer window to run in Windows 7 x64 and is not planning to fix this?

    -Noel

    Not even if you start it in a 32-bit cmd prompt window (%SystemRoot%\SysWOW64\cmd.exe, shown in taskmgr as cmd *32).
    Sunday, October 11, 2009 1:18 AM
  • I checked, and sadly "NO", it does not matter if explorer.exe is launched from a 32-bit CMD window.  It still spawns a 64-bit variant.  This stinks!  I do hope they revert back to the previous behavior in a future hotfix or service pack.
    Sunday, October 11, 2009 3:00 AM
  • This is a regression therefore should a bug that can be fixed.

    Besides my original bug post has been removed from Connect (well I can't see it any more!).

    Does Microsoft monitor this forum?
    Thomas Lee - doctordns@gmail.com
    Wednesday, October 21, 2009 2:18 PM


  • Does Microsoft monitor this forum?
    Thomas Lee - doctordns@gmail.com

    Input to Microsoft.url
    Rating posts helps other users
    Mark L. Ferguson MS-MVP
    Wednesday, October 21, 2009 3:24 PM
    Moderator
  • Isn't that just  a black hole?
    Does MS actually read stuff that filters through there?
    It says "Windows 7 RC" so does that apply to the RTM version as well? 
    Because ironically, it *works* in the RC
    But they broke it in the RTM
    Wednesday, October 21, 2009 5:05 PM
  • Isn't that just  a black hole?
    Does MS actually read stuff that filters through there?
    It says "Windows 7 RC" so does that apply to the RTM version as well? 

    A good point
    Because ironically, it *works* in the RC
    But they broke it in the RTM

    Actually it was OK in the Beta, broken in the RC & still broken in the RTM. Tricky stuff, irony ;-)
    Thursday, October 22, 2009 8:14 AM
  • I like it - an MVP with a sense of humour. Totally usefuless as an answer since that is a well known black hole, but still amusing.

    I guess the answer to the question is:

     "No they do not monitor the forums, instead they offer an address for submission that is effectively a black hole (unless you get very lucky)."

    ANd as for rating - how do you rate something as "UnHelpful"?
    Thomas Lee - doctordns@gmail.com
    Thursday, October 22, 2009 8:19 AM
  • This is a regression therefore should a bug that can be fixed.

    Besides my original bug post has been removed from Connect (well I can't see it any more!).
    Do you know whether there is a better handle for the bug than your Connect post ID?

    Perhaps this is something that an MVP could help with!
    Does Microsoft monitor this forum?
    Apparently some engineers at least do follow some some forums:

    http://blogs.msdn.com/e7/archive/2009/08/10/what-we-do-with-a-bug-report.aspx

    "In the meantime, we continue to look through external blogs, forums and other reports of crashes"

    Unfortunately this bug is not a crash.  Though a Windows Explorer fails to run, it is almost certainly not even instrumented
    as an error.  Now there's irony!
    Thursday, October 22, 2009 8:40 AM
  • This is a regression therefore should a bug that can be fixed.

    Besides my original bug post has been removed from Connect (well I can't see it any more!).
    Do you know whether there is a better handle for the bug than your Connect post ID?

    Perhaps this is something that an MVP could help with!
    Does Microsoft monitor this forum?
    Apparently some engineers at least do follow some some forums:

    http://blogs.msdn.com/e7/archive/2009/08/10/what-we-do-with-a-bug-report.aspx

    "In the meantime, we continue to look through external blogs, forums and other reports of crashes"

    Unfortunately this bug is not a crash.  Though a Windows Explorer fails to run, it is almost certainly not even instrumented
    as an error.  Now there's irony!
    I do not speak for MS, but they do obviouly read the answers forum, since the majority of the highly technical answers here are from MSFT. This, on the other hand, is not a technical discussion, It's a query on an error. If you get an error, the best analysis available to you is going to be the 'sysinternals' utility added by 7. perfmon /rel
    Rating posts helps other users
    Mark L. Ferguson MS-MVP
    Thursday, October 22, 2009 12:29 PM
    Moderator
  • This was a major selling point for me when I migrated to 64-bit Windows. Why hasn't Microsoft fixed this critical bug is beyond me. Imagine if they did the same with Internet Explorer so only 64-bit IE would work in 64-bit Windows 7. All my shell extensions are now wasted. I have two choices. Go back to Windows Vista or XP 64-bit or Windows 7 32-bit I won't go back to a 32-bit platform now so bye bye Windows 7 till this is fixed.
    Anonymuos
    Sunday, May 09, 2010 6:51 AM
  • Okay can anyone try this method to see if 32-bit Explorer can't run at all?

    1. Terminate 64-bit Explorer.exe using Task manager.
    2. Start Explorer.exe from Task manager: File menu: New task: C:\Windows\syswow64\Explorer.exe and see if it loads as the shell/taskbar?
    3. If this works, see if launching C:\Windows\syswow64\explorer.exe works (as a file manager this time)?

    Monday, May 17, 2010 1:13 AM
  • According to luckman222, it will still run 64 bit explorer.

    See his post above on Oct. 11, 2009 3:00 AM, after my post of Oct. 11, 2009 1:18 AM.

    Monday, May 17, 2010 1:31 AM
  • All the posts say running 32-bit Explorer.exe using the /separate switch as the file manager when 64-bit Explorer is already loaded as the shell. What I want to be clear about (none of the posts are particularly clear about that) is can you start 32-bit Explorer.exe from Syswow64 folder using Task Manager when no 64-bit process Explorer.exe is running as the shell? Since I don't have access to 64-bit Windows 7 and a machine/enough VM disk space to try that on right now, can any one try that? Terminate all instances of 64-bit Explorer.exe, then start 32-bit Explorer from SysWow and see if the Taskbar appears (it loads as the shell). Then see if starting Explorer.exe from Syswow64 starts the 32-bit Explorer.
    Monday, May 17, 2010 11:50 AM
  • I was one who ran the 32 bit Explorer on 64 bit Vista, but since I switched to the Windows 7 RTM 6 months ago I haven't felt the need for the 32 bit Explorer any more.

    It used to be that running 32 bit Explorer windows facilitated the addition of 32 bit shell extensions, which all old apps seemed to have (as well as a lack of 64 bit shell extensions).  So, for example, for a while you could get right-click WinZip functionality only if you ran the 32 bit Explorer (though they were one of the few companies that embraced 64 bits before being forced to).  In fact, there were a few brave apps (from companies with forward-looking engineers) that migrated to 64 bit, but they were mostly on their own.

    Now that Windows 7 x64 has decided to only run the 64 bit Explorer for file management operations, lo and behold most of the software manufacturers immediately have come out with new 64 bit builds for their shell extensions, and we now have virtually ALL the functionality we once had (assuming we update to the latest apps) again, but this time in native 64 bit builds.

    I questioned Microsoft's reasoning when they forced this change, but now I see it was right on the money.  For whatever reason, developers have to be pushed to do the right things.  I guess most of them are inherently lazy otherwise.

    Sorry, sumone, I can't justify tearing down my 64 bit Explorer on my main system to test whether the 32 bit version will run as the shell.  One of these days I plan to create a 64 bit Windows 7 VM as a test environment.  Then I'll test it for you.

    -Noel

    Monday, May 17, 2010 2:27 PM
  • You do realize right that shell extensions are rare pieces of code (some of them very legacy) and are very unlikely to be updated for native 64-bit. Would you say the same if they did the same in case of IE and "forced" lazy developers like Adobe to create 64-bit Flash player? When software doesn't work, it's the end user that suffers. Any change that's forward looking isn't necessarily a step in the right direction. And since when is terminating or gracefully exitting Explorer.exe=tearing down your system? Are you aware that you can gracefully exit Explorer by right clicking on the Start menu while holding down Ctrl+Shift?
    Monday, May 17, 2010 7:47 PM
  • Rare?  Hardly; there are plenty of new 64 bit shell extensions.  Virtually every application comes with them.  Run ShellExView on a 64 bit system full of brand new software and tell me what you see.  Your terminology is off.

    Shell Extension:  Software added to Explorer to add functionality and enhance the system integration provided by Explorer.  For example, quite a number of Shell Extensions are depicted here:

    Looking forward one sees clearly, albeit in the distance, a pure 64 bit system with no 32 bit legacy code running anywhere.  And 64 bit architected computers that do more in parallel.  It doesn't take a rocket scientist to see that.

    Do you know how easy it really is to build 64 bit Windows software, if one has engineered good structure?  In the best cases (with well structured, clean source code) it's just a recompile.

    If you're not pursuing compatibility with older Shell Extensions, what is it that you're seeking by running the 32 bit Explorer?  How about telling us what you're trying to accomplish, rather than your intermediate steps.  Chances are good someone's already found another way to get there from here.

    -Noel

    Monday, May 17, 2010 10:30 PM
  • All the posts say running 32-bit Explorer.exe using the /separate switch as the file manager when 64-bit Explorer is already loaded as the shell. What I want to be clear about (none of the posts are particularly clear about that) is can you start 32-bit Explorer.exe from Syswow64 folder using Task Manager when no 64-bit process Explorer.exe is running as the shell? Since I don't have access to 64-bit Windows 7 and a machine/enough VM disk space to try that on right now, can any one try that? Terminate all instances of 64-bit Explorer.exe, then start 32-bit Explorer from SysWow and see if the Taskbar appears (it loads as the shell). Then see if starting Explorer.exe from Syswow64 starts the 32-bit Explorer.

    No, even if I stop the 64-bit explorer using task manager, I still cannot start a 32-bit explorer, either with /separate or without.

    In bothy cases, the 64-bit explorer launched does not load as the shell (no Taskbar).

     

    Regards

    Sunday, May 23, 2010 10:40 AM
  • slightly off-topic but it might help some:  for those affected by this issue with respect to the Adobe PDF shell extensions (preview, thumbnail generation, etc) there is a working 3rd party fix available (free) that I have just tested on my Win7 x64 setup and found it to work perfectly.  Check it out:

    http://www.pretentiousname.com/adobe_pdf_x64_fix/index.html#downl

     

     

    Monday, May 24, 2010 2:06 PM
  • Really you think shell extensions only mean context menu extensions? There are dozens of shell extensions which will never be updated (some of the apps work perfectly but development is defunct). Just like 32-bit IE and 32-bit WMP on 64-bit Windows, we need 32-bit Explorer. It was working in the beta up to RC so clearly some moron at MS screwed it up as they have done with the rest of the Explorer.
    Anonymuos
    Sunday, June 06, 2010 3:48 AM
  • @Dave English, thanks for clearing that up. I guess I will now have to stick with XP or Vista.
    Anonymuos
    Sunday, June 06, 2010 3:49 AM
  • It's time to move into the new millenium, Anonymuos.

    I suspect Microsoft elminated the concept of running 32 bit Explorer on x64 systems because it added complexity.  Elsewhere people are crying for a more robust Explorer.

    Funny thing how when Microsoft made it necessary for shell extensions at the release of the 64 bit system to be 64 bit exclusively most of the manufacturers doing active development delivered them in weeks.

    You want old 32 bit software to run like it's on a 32 bit system, then run the 32 bit OS.

    -Noel

    Monday, June 07, 2010 2:06 AM
  • If you want to do it that way went to task manager go to the processes' tab and end the process explorer or even two or more and then begin a new task found on the right site on the bottom in the application tab browse to C:\Windows\SysWOW64\explorer.exeand then you will see in the process tab widows explore 32. And if if you want to go back by the new task type in explorer and hit enter, and it will come back. it takes me 3 hour to fintd it !!!ha!!!

    Sunday, January 02, 2011 6:08 AM
  • It's time to move into the new millenium, Anonymuos.

    I suspect Microsoft elminated the concept of running 32 bit Explorer on x64 systems because it added complexity.  Elsewhere people are crying for a more robust Explorer.

    Funny thing how when Microsoft made it necessary for shell extensions at the release of the 64 bit system to be 64 bit exclusively most of the manufacturers doing active development delivered them in weeks.

    You want old 32 bit software to run like it's on a 32 bit system, then run the 32 bit OS.

    -Noel


    Thanks...

    For the glorious horn tootage, Sir!

    Friday, February 04, 2011 9:29 PM
  • :) I thought the echoes had died down from that blast a long time ago.  :)

    Actually, now looking back at well over a year of usage (considering other than 32 bit shell extensions), 64 bit Windows 7 runs 32 bit apps really well.  Perfectly so, I'd say.  And I haven't found any shell extensions or codecs I need but can't get for 64 bits.

    There are always virtual machines for running 32 bit Explorer I suppose.

    -Noel

    Friday, February 04, 2011 10:17 PM
  • If you want to do it that way went to task manager go to the processes' tab and end the process explorer or even two or more and then begin a new task found on the right site on the bottom in the application tab browse to C:\Windows\SysWOW64\explorer.exeand then you will see in the process tab widows explore 32. And if if you want to go back by the new task type in explorer and hit enter, and it will come back. it takes me 3 hour to fintd it !!!ha!!!


    It doesn't work.  I already tried that.

    I agree with Noel.  I have not had the need.

    Now if Internet Explorer x64 worked as well as Explorer x64 that would be something.  I guess Adobe needs to move into the new millenium so that flash can work in IEx64.

    Saturday, February 12, 2011 11:09 PM
  • There really is no resolution for this unless Microsoft allows once again to default to the 32-bit shell or provides some transition feature in the 64-bit Explorer for 32-bit Explorer. There are 32-bit property sheet handlers, 32-bit AutoPlay handlers, thumbnail preview handlers, icon handlers, infotip handlers NOT JUST CONTEXT MENU handlers to justify this forced move to 64-bit only Explorer.

    Some people are okay with it because the shell extensions THEY USED are now 64-bit so suddenly it's time to move forward. Then let Microsoft remove Wow64 entirely. If they force everything in native 64-bit, developers will again produce native 64-bit apps in weeks. But who would suffer for the millions of legacy 32-bit only apps that are never updated any more? It's the same with shell extensions.
    Monday, February 21, 2011 2:11 PM
  • I agree with you also, Anony.mous.

    Until 64-bit applications are more universal, especially by Microsoft, full 32-bit compatibility should continue.

    • Proposed as answer by Noel Carboni Tuesday, February 22, 2011 4:44 AM
    Monday, February 21, 2011 8:28 PM
  • As one whose needed features are all available to me on my 64 bit system, I'm one of the folks anony.muos is identifying here.

    And I am forced to agree, assuming you want to be able to continue to run applications from yesteryear.

    Computers don't actually HAVE to be like fashion.  Old apps can continue to deliver value.  But the world of software is rich; a lot of solutions are available if something you loved is no longer there.

    -Noel

    Tuesday, February 22, 2011 4:47 AM
  • "As one whose needed features are all available to me on my 64 bit system, I'm one of the folks anony.muos is identifying here.And I am forced to agree, assuming you want to be able to continue to run applications from yesteryear"

    Sadly, the only thing I wanted to run was Font Properties Extension. This is only available as a 32-bit extension for Windows Explorer, and cannot be accessed from a separate submenu (instead it apparently hooks the "Properties" command for a font file).

    See http://www.microsoft.com/typography/TrueTypeProperty21.mspx

    What's ironic, is that this is *Microsoft* software! I don't want some long gone garage software company to create a 64-bit version of their archaic application. I would just like to run this one piece of code, made by the same people who rendered it useless in Win7 64b in the first place.

    Anyone know of a good alternative for FPE?

    -z


    • Edited by zzpazi Wednesday, January 25, 2012 12:28 PM
    Wednesday, January 25, 2012 12:26 PM
  • @zzpapi, I wanted the 64-bit version of FPE for a long time too so I ranted like crazy to some Microsoft font and typography blogs because I loved the FPE. They contacted me and turns out apparently the Font Properties Extension was updated around the Vista timeframe for 64-bit as well but they published the link just for the 32-bit version and didn't publish the 64-bit version because it didn't have an installer! I managed to lay my hands on it. If you want it you can download it from my SkyDrive: here.

    Another "pain reliever" is WOW64Menu which is really a very simple and brilliant idea. It's a 32-bit process that displays the context menu for any item passed to it. e.g. WOW64Menu.exe "%1". Then for that item, you can access it's 32-bit context menu and 32-bit properties (therefore access 32-bit property sheet handler shell extensions). Sadly, there are many other shell extension types (infotip handler, thumbnail handler, icon and icon overlay handlers, metadata handler) and for these, Microsoft has done nothing to ease the transition or pain but simply taken away the ability to run 32-bit Explorer in Windows 7 and later.

    • Edited by xp.client Saturday, April 07, 2012 3:37 AM
    Saturday, April 07, 2012 3:28 AM