This project has moved and is read-only. For the latest updates, please go here.

wrong explorer launched


mismacth with browsers having same name. I've configured 3 browsers: mozilla, ie9 x32, ie9 x64
ie9 x32 path: "C:\Program Files (x86)\Internet Explorer\iexplore.exe"
ie9 x64 path: "C:\Program Files\Internet Explorer\iexplore.exe"
but either I click x32 or x64 icon, browser chooser always starts x32

file attachments


spy1 wrote Jun 11, 2011 at 6:35 PM

Ok, code is not difficult to correct but there is an easier workaround:
create a shortcut to internet explorer 64 bits with a different name (eg iexplore64.lnk) and specify this shortcut in browser chooser, not iexplore.exe

johnlgalt wrote Jun 21, 2011 at 10:39 PM

Duplicate of #6199

wrote Jun 21, 2011 at 10:44 PM

johnlgalt wrote Jun 21, 2011 at 10:44 PM

Also, I may have found another byproduct of the code that is causing this issue.

I have multiple versions of Firefox installed (currently Fx5 in C:\Program Files (x86)\Mozilla Firefox\ and Minefield 7.0a1 in C:\Program Files\Minefield). I've been using BC for a long time now and it has always allowed me to pick which one I wanted to load (as some sites will not load in beta / alpha versions of Fx b/c of the browser version number being unidentified). However, recently, since moving to a purely 64bit version of Minefield on my computer, it will not load the 64bit version at all - and the only thing I can see different is the path.

When I try to load the 64bit Minefield, I get an error as depicted in attached screenshot. I suspect that this is either because 1) BC installed in C:\Program Files (x86) or else something else is amiss.

I'll play with it more, and, Jan, if you want any more feedback or testing, let me know.

johnlgalt wrote Jun 26, 2011 at 5:31 PM

I've found part of the problem.

BC is installed in \Program Files (x86)\ on 64bit versions of Windows, and any browser that is not located in the same directory will simply not load. With my setup, I have a Minefield (nightly version of Firefox) that comes compiled from Mozilla as a 64 bit app installed to \Program Files\ but there is no corresponding installation in \Program Files (x86)\ and I receive the error as noted above.

Rather than creating a shortcut as mentioned by spy1, however, I created a Symbolic Link in \Program Files (x86)\ to the Minefield folder in \Program Files\, and now it works perfectly fine.

Jan, why is it not loading the actual full path of the app, and instead only searching within its installed tree for the app? Or, is there something else that is going on?

johnlgalt wrote Jun 26, 2011 at 5:33 PM

Hmmm, now that I think about it, I wonder if creating a symbolic link of the BC install folder in \Program Files\ would, that should not work, b/c the slink isn't going to allow the program to still be able to peruse the \Program Files\ tree, is it...hmmm....

spy1 wrote Jul 18, 2011 at 10:51 AM

Précision, I create the shortcut on application itself not on the directory of the application (Hoppefully BC doesnt request the selected application to be 'exe' terminated). A shortcut on directory has no reason to work, for the system it's just another directory and same search rules apply. Symbolic links should work same IMO.
The exact problem is that BC is coded so windows searches itself the application (Technically it should be rewritted to use the CreateProcess function)
Note that some other programs have same pb (Note too that BC have another pb showing some icons on windows 7, eg Tor Browser. This seems to be related to sizes of png icons, vista was tolerant with that but windows 7 seems not)

wrote Aug 26, 2011 at 3:04 AM

wrote Feb 24, 2012 at 7:38 PM

wrote Feb 21, 2013 at 11:50 PM