InstaAlert and Vista

[Ryan Lederman]

This build uses ShellExecute directly and doesn't make an attempt to read the default browser from the registry.

The reason we were doing that, FYI, is because we wanted to preserve any special flags you had set in your command-line for opening the browser.

I suppose MS knows better than us though!

http://hotfix.kayako.com/instaalert/...E-3.1.2.22.exe

Edit: In hindsight, MS should've made it so that when a default browser was chosen through the GUI (Control Panel -> Default Programs) or programmatically, it should automatically update the legacy registry key so that apps designed for <= XP wouldn't have this problem. (of course only Administrators could change the HKEY_CLASSES_ROOT hive)

[EPCal]

Awesome! Thanks!

[wtz]

Originally Posted by Ryan Lederman

http://hotfix.kayako.com/instaalert/...E-3.1.2.22.exe

New version works for me in Vista and opens links properly in Firefox now! Thanks you very much!

Also, your explanation for reading the registry makes sense. MS definitely should have made it to update the legacy registry keys. I think Firefox is/was planning to do that on their own according to notes in their Bugzilla.

[craigbrass]

I think Firefox is/was planning to do that on their own according to notes in their Bugzilla.

Thats what I read too. Aparently should be sorted in the next release.

[Ryan Lederman]

Originally Posted by EPCal

When booting InstaAlert in Vista when it's set to start and log in at boot time, it seems to try to log in before my network connection has finished and it never connects until I manually tell it to log in.

Can a delay be added to wait X seconds before attempting to log in?

Secondly, everything else works correctly, but InstaAlert insists of opening in IE instead of FireFox. Any ideas? Everyone thing else such as shortcuts, other programs, etc. open FireFox as it is set as the default browser.

I've tried uninstalling and reinstalling IA and FF to no avail.

InstaAlert should try up to 20 times before giving up on connecting. Are you still experiencing this problem?