URLs don't use default browser
 

I have Firefox as my default browser but links in the text of info items, such as www.page.co.uk, always open in IE. Typing that URL into the Run box opens properly in Firefox. I'm using Vista.

How can I get the links to work properly in UR?

In my tests w/ UR Pro v3.2.6 and Firefox v2.0.0.9 (configured as the default browser) on Windows Vista Ultimate, links in UR opened externally load in Firefox. Are you opening the link via Shift+click or some other way? What happens when you download the attached file, extract, and double-click in Explorer? When viewing ultrarecall.exe in Task Manager (Ctrl+Alt+Del, Start Task Manager) Processes tab, is it running under your User name?

Thanks for getting back to me. I'm creating a link by typing "www.page.co.uk" (without the quotes) into an info item. UR underlines it and turns it into a hyperlink. I activate the link just by clicking on it; however, right-clicking and choosing Open Shortcut also results in the link opening in IE rather than Firefox.

Double-clicking on the file you sent opens the page in Firefox.

The UR process is running under my user ID.

Normally, clicking a link or choosing Open Shortcut will open a URL like that in UR's internal browser (which is in fact embedded IE). Do you have UR configured to open links external by default, and is the page opening in an external instance of IE?

What happens if you import test.vbs into UR and launch it from there (Ctrl+J)?

Yes, I've got the option to launch shortcuts in external browser ticked, and the page opens in an external instance of IE.

Importing test.vbs and launching it from there also results in it opening in an external instance of IE.

It must be a Vista thing (Home Premium) because I've just tried it on the XP machine I was using for UR up until a few weeks ago and the link opens in Firefox on that PC.

Since that test file opens in Firefox when run directly but opens in IE when run from within UR (and other URLs opened from UR also open in IE), there is apparently something different about the Ultra Recall process environment/configuration that is resulting in the different behavior (as I mentioned, it works as expected in our tests on Vista Ultimate, but I haven't tried Vista Home Premium, so it could be something specific to that version of Vista or something funky about your configuration).

Is UR being "run as administrator" (on Vista, even admin users don't run as admin ["elevated" in Vista parlance] by default), or is there any software installed that might somehow be affecting what a ShellExecute call does for a given process?

I've tried setting compatibility mode to XP SP2, and it still opens the link in IE. It won't let me check run as administrator in the compatibility settings (perhaps it's already running that way?), but if I start UR by choosing RUn as adminstrator from the context menu on the shortcut, it still opens the link in IE.

I don't think I've got anything intercepting the ShellExecute command; the software on the Vista PC is pretty much the same as on the XP machine. I opened an info item that has a hyperlink in the text externally in Jarte and control-clicked on the link, and it opened correctly in Firefox.

I suspect this has something to do with Vista's "Default Programs" feature:

http://tech.groups.yahoo.com/group/w.../message/56252

http://www.google.com/search?q=vista...ult%20programs

Alas, not in this case. I'd already found that applet and tried it, but no matter how I set Firefox as the default, Internet links from UR (and so far no other software) always open in IE.

It's Vista, not UR, that is deciding to launch IE rather than Firefox (Item | Open Document [Ctrl+J] or shift+clicking a URL in a text item causes UR to call ShellExecuteEx, passing the URL -- it doesn't specify the browser to use). I don't know why Vista would single out UR for that behavior on your computer; maybe there is a bug in the Default Programs feature.

Yes, I think it must be a problem here as it doesn't happen under XP and no one else has reported the problem.

Thanks for researching the additional information.

Whatever the problem was, it's been fixed by installing Firefox 3 beta!