New
#11
There are 32 bit and 64 bit context menus in Windows 7 x64. The file manager FreeCommander - freeware file manager has a simple fix for its .ini file which enables both 32 bit and 64 bit context menus. Just hold the Win key while right clicking to see the 32 bit version. Look for a description in the release notes of the latest version.
I'm not inconvenienced by this.
I was only adding my speculations. :)
Thanks for those links.
I'll check them out after I finish TAFE today.
I am using Windows 7 (64 bit).
With the exceptions of AVG and VMware Workstation, all of my other programs only offer 1 installer, which also works in XP SP3 (32 bit).
I use FreeCommander (for mass file renaming).
Has a new version come out?
I tried Logo + right clicking on a couple of files, but I didn't notice any differences.
Yes that's right.
If you check with Glary's own context menu handler - you will see the entries are there for Glary - but you don't see the context menu entries in windows 64 bit.
Nothing you can do about it.
You might see them if you replace windows explorer with a 32 bit explorer - such as freecommander.
I have Win 7 X64. I have winrar, 7zip, with context menus. Please check that you downloaded the X64 versions. Well on 2nd thought if you tried to install a 32bit flavor, it shouldn't work, usually.
I do have many X86 (32 bit) programs installed all with contesxt menus.
flash Get
Weatherbug
FLV Player
DivX
Malwarebytes
Norton
etc.
What does the Windows 7 Manager do that Win 7 doesn't? Maybe causing this problem.
No, Micrsoft has not disabled context menus.
It makes sense to ask this question. I'm not familiar with W7M, but given its shell customization features (particularly the context menu customization) and registry cleaning features, I'm immediately suspicious. I would:What does the Windows 7 Manager do that Win 7 doesn't? Maybe causing this problem
1) Create an image backup of the drive.
2) Completely uninstall W7M with Revo or similar
3) Reinstall a few of those programs whose context menu items are missing to see if they now appear.
Could be a waste of time, but given the nature of the program and the nature of the problem, I'd have to eliminate it as a possibility early on.
James
There are two different questions in this thread.
1. Lehnerus says some apps. context menus worked when he had XP - they now don't work in his 64 win7.
He gave Glary as an example.
That is because Glary shell extension is 32 bit and does not work on 64 bit o/s.
There are many apps. like that.
2. The OP had a different question - in his case apps. which do have 64 bit shell extensions are not showing up for him.
They still do not show up after he applies them manually via the program's own interface.
Something seems to be interfering - it may well be another program - possible Yamisoft.
The latest Full release of FreeCommander is 2009.02b released in Sept 12, 2010
The release notes contain the following:
- New: 64 bit context menu will be showed on Windows 64 (XP, Vista, 7)
- You can now control 64 bit context menu with the following line in the freecommander.ini:
[Form]
ShowContextMenu64Bit=1
AutoCloseTimeContextMenu64Bit=10
- You can call 64 bit context menu with right click
- For calling 32 bit context menu use LeftWin+RightClick
- If you prefer to see for right click always 32 bit context menu: define ShowContextMenu64Bit=0; with LeftWin+RightClick you can call then 64 bit context menu
You have to make this change for the 64-bit context menus to work correctly.
There is also a Beta version of FreeCommander if you are interested.
Last edited by JC Zorkoff; 06 May 2011 at 08:38. Reason: Fixed release date
Sorry I seem to have complicated the issue.
I wasn't actually asking a question, merely stating my experience (actually I did ask about FreeCommander).
I wasmerelystating that some programs (which appear to be 32 bit) do add their context menu entries in Windows 7 (64 bit), whereas others don't.
As near as I can tell most of my programs are 32 bit.
During installation they suggest that they be installed in C:\Program Files (x86).
Last edited by lehnerus2000; 10 May 2011 at 00:10. Reason: Correction