but another problem: on x64 OS FARR cannot start any .lnk (from %MYSTARTMENU%|%COMMONSTARTMENU%)
for build-in/system Windows application from "%windir%\System32\" that doesnt have corresponding x32 analog in "%windir%\SysWOW64\"
on windows 7 x64 you cannot execute:
"Sound Recorder", "Snipping Tool" and other.
maybe FARR, when resolve *.lnk target to %windir%\system32\* can try to find it in %windir%\sysnative too ?
-lordmuzer
I am new to FARR, although have used Launchy and Executor for some years (but am considering switching to FARR because it is so much better :)). This is also a problem for me (and part of the reason I am looking at alternative launchers), as it is with both Launchy and Executor - although there is an unofficial Launchy x64 version.
I use regedit32 a lot, and often switch between the 32bit (sysWOW32 folder) and the 64bit (System32 folder) so I can see the HKLM\Software tree either in real mode or in the virtual redirected mode that the 32 bit version provides. There are other x64 apps I also use including nbtstat (doesn't exist in SysWOW32), and cmd.exe (need to run the x64 version to get access to nbtstat and also to manage network shares if the admin/normal networks aren't linked).
After lots of experimenting I think the following is the cause:
- x86 apps cannot see the System32 folder, or any of the files therein. Any reference to Sstem32, including in shortcuts is redirected to the SysWOW32 folder.
- x86 apps can call and use x64 apps that are not in the system32 folder, as it is the only one that is completely redirected.
To confirm this I use a x86 file explorer (Xplorer2) to look at the C:\Windows\System32 folder and it is exactly the same as the C:\Windows\SysWOW32 folder, and if I run C:\Windows\System32\regedit.exe I get the 32bit version (from SysWOW32 folder) and cannot see the real HKLM\Software\WOW3264node tree.
If I use a x64 version of Xplorer2 then I can see the real contents of C:\Windows\System32, and can start x64 apps from the System32 folder and x86 apps from SysWOW32 folder.
I think the only way to get access to apps (and consoles) in the C:\Windows\System32 is to do so from a x64 app. I have found that I can copy the apps out of the System32 folder and then they can be run fine.
One way I have got around this is to create a junction to the C:\Windows\System32 folder, and then I can access all the x64 app from the System32 folder by using the junction path. But this is a bit of a kludge and needs either Xplorer2 or link shell extension.
Sorry for long winded reply, but I think the only way to access the System32\apps I want is for a 64bit version of FARR.