FARR Unable to launch VirtualBox (and perhaps others) in Win7?

[dandersahn]

I've been using FARR with Windows 7 x64(both beta and RC) and have noticed that while for the most part it works just fine, there are certain very rare programs that it can't seem to launch.  The only example that I can provide at the moment (because it's the only one that I use enough to remember) is VirtualBox.  I have no idea why, but when I try to launch the VirtualBox Manager using FARR, either nothing happens (if the "Launch Method" is set to "Method 1 - ShellExecute") or Windows tells me that the path to the .lnk file does not exist (if the "Launch Method" is set to "Method 2 - ShellExcuteEx" [SIC]).  Both the path to the shortcut and the executable exist and the shortcut launches just fine using Explorer.  I can't figure out what is different about this program.  I've tried compatibility modes, security settings, etc.  Seems to be something with the path, but I can't figure it out.  Has anyone else seen anything like this?

[mouser]

are there any spaces in the filename?
if you go look at the shortcut file, and right click on it and view properties, is it one of those shortcuts that doesn't link to an actual location?

[dandersahn]

It's a completely normal shortcut with no spaces in the file name.  The path the the exe is:

"C:\Program Files\Sun\VirtualBox\VirtualBox.exe"

It was originally installed in:

"C:\Program Files\Sun\xVM VirtualBox\VirtualBox.exe"

I thought the "\xVM" might be causing a problem as \x is a hex character code escape sequence in Python (and perhaps other languages), but reinstalling in a different directory didn't help.

[mouser]

thats very strange.. anyone else with virtualbox installed have this problem?

[dandersahn]

Here's another program that does the exact same thing -- Paint.net. The same error is presented: "The specified path does not exist".  The path does exist.  The shortcut works find when launched via Explorer or the start menu.  It's a very standard looking target:

"C:\Program Files\Paint.NET\PaintDotNet.exe"

Only thing remotely notable is the "." in the folder name.

[mouser]

i wonder if indeed that . is the problem.. care to experiment a little by making copies of the program in dif dirs with and without dots in them?

[dandersahn]

Reinstalled in "C:\Program Files (x86)\PaintDotNET\PaintDotNet.exe".  Still no luck.

[dandersahn]

I figured out something out that is fairly bizarre.  If I view the properties for the shortcut by using the right click context menu from within Explorer, the target shows as...

C:\Program Files\PaintDotNET\PaintDotNet.exe

... which is correct.  BUT if I select "shell context menu" from the FARR context menu and then select properties, the target (for the exact same shortcut file) shows as ...

C:\Program Files (x86)\PaintDotNET\PaintDotNet.exe

So something funky is going on for some 64bit programs.  My workaround is to "Ignore item in the future" and have FARR launch the exe directly instead of the shortcut.  This workaround obviously only works if there are no arguments.  I will try running the program in compatibility modes to see if that helps.

[Tekzel]

I have had a similar issue, Win7 RC1 x64 and the one I notice this on is Q-Dir 64bit.  I just figured it was the fact that it was a 64bit program and that had something do with it.  Can't think of any others off hand, but I know I have the issue with at least one other program.

[dandersahn]

I have found that if you change the path by opening the shortcut properties through the FARR (1-right click on the shortcut within the FARR results, 2-"shell context menu", 3-"properties") it will fix the problem.  It's almost as if somehow the shortcut is storing two values - one for 64bit Explorer and one for 32bit FARR.

[Tekzel]

I have found that if you change the path by opening the shortcut properties through the FARR (1-right click on the shortcut within the FARR results, 2-"shell context menu", 3-"properties") it will fix the problem.  It's almost as if somehow the shortcut is storing two values - one for 64bit Explorer and one for 32bit FARR.

-dandersahn (June 22, 2009, 06:40 PM)

Hah, I never even thought to check that, but when I did it for giggles I found that the .lnk FARR was running actually pointed to the PF (x86) folder, and I have the 64bit version installed.  Weird that I didn't get any "File or object not found" kind of message.  Oh well, when I updated the target in the shortcut it works fine now.  Going to keep that one in mind when I run into any other similar issues.