Bug in launching 64-bit software.

[kli6891]

Hi, I encountered a bug while using FARR on a 64bit Windows 7 PC.

It seems that whenever I try to launch a 64bit application (e.g. Zune, Photoshop, VirtualBox), the launching fails. Also the program icon also doesn't show up.

If I right click on the item and select "Copy Target Path (Ctrl+C)", and paste it somewhere, the path is incorrect; it leads to C:\Program Files (x86)\, when it really should be C:\Program Files.

See screenshots, in case I'm not being clear.

[mouser]

Thanks Kli,

it seems you've confirmed (and explained clearly) the problem that also seems to be at the root of this thread:
https://www.donation...ex.php?topic=18579.0

I'll see if it can't get it fixed this weekend.

[mouser]

If you (or anyone) could find a *small* x64 application that causes this behavior, it would really help testing.

[kli6891]

Off the top of the head, I can think of paint.NET, and locate32 64bit with the installer version. Locate32 is smaller of the two.

[mouser]

Can you try this version and see if it solves the problem:
https://www.donation...AndRunRobotSetup.exe

[kli6891]

Unfortunately, the same problem still exists.

The about screen shows v2.69.01, in case I'm using the wrong version.

[mouser]

this seems to fix the problem on my win xp 64 vmware.
i dont know why the fix wouldn't work on win7 x64.. sigh..
i guess il have to make another vm and try again.. thank you bill gates.

[mouser]

ok i can confirm the problem remains on win7 x64; should have a fix in 10-20 minutes, stay tuned.

[mouser]

ok try again:
https://www.donation...AndRunRobotSetup.exe

[kli6891]

It indeed fixed the problem! Thanks. 

[mouser]

Now i wait for the reports of the things i broke in the process of fixing this

[mouser]

btw the problem seemed to be that there is a flaw in the shortcut resolution in windows 7 (and other x64 OS flavors)..

it seems to return "Program Files (x86)" in the paths of .lnk files when resolved by a win32 app, regardless of the true application directory of the program.. bad show.

so basically farr now checks to see which of the program files directories the file *really* resides in and doesn't trust the .lnk file.

this is relatively straightforward except that it required some changes in the icon display (since previously farr just asked the OS for the icon index of the .lnk file), and more importantly required me to overide the launch options on the General tab and force FARR to not try to launch (.lnk) shortcuts if they are of this type, and instead resolve the shortcut and launch the exe directly in such cases.  pain.