InstaAlert and Vista

[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.

[richm]

Hi Brian,

Do you have the auto-reconnect to server every x setting enabled? I would think the re-tries would eventually get you in.

In IE's settings (tools | internet options) on the programs tab, is the check next to IE should check to see whether is is the default browser set?

HTH,

Rich

[craigbrass]

As this is a bug, please submit it at http://bugs.kayako.com so that the developers see it and get it fixed.

[EPCal]

Originally Posted by rixm

Hi Brian,

Do you have the auto-reconnect to server every x setting enabled? I would think the re-tries would eventually get you in.

In IE's settings (tools | internet options) on the programs tab, is the check next to IE should check to see whether is is the default browser set?

HTH,

Rich

Yes, it is set to retry. I guess since it never initially connects (but shows a connection error), it never tries again.

Yes, Internet Options settings does not show IE as the default browser.

[Digital Mayhem]

Odd cause I have Windows Vista Ultimate and InstaAlert Pro installed and never had this issue...

[Ryan Lederman]

EPCal, would you please submit this as a bug report?

[EPCal]

Submitted as a bug yesterday.

FWIW, this is a new installation (using upgrade DVD but performing a clean install) of Vista Home Premium.

[Ryan Lederman]

EPCal,

What's the value in your registry under HKEY_CLASSES_ROOT\\http\\shell\\open\\command ?

[EPCal]

"C:\Program Files\Internet Explorer\iexplore.exe" -nohome

(Sorry for not responding sooner... I'd given up on Vista and went back to XP.)

[Chris Boulton]

The networking functionality in Kayako apps needs to be redeveloped.

This is annoying to say the least - especially when you have machines coming in and out of standby and drifting out of a wireless network connection.

The apps need to be designed that if they detected a connected/available network connection (as in marked as connected in Windows) that they only attempt to connect then.

[Ryan Lederman]

Originally Posted by Chris Boulton

The networking functionality in Kayako apps needs to be redeveloped.

This is annoying to say the least - especially when you have machines coming in and out of standby and drifting out of a wireless network connection.

The apps need to be designed that if they detected a connected/available network connection (as in marked as connected in Windows) that they only attempt to connect then.

We agree, and we will be researching automatic connection in the near future. You may expect this to be part of the network functionality in the next release of the add-ons.

[Chris Boulton]

Excellent.

Thanks.

[Ryan Lederman]

Originally Posted by EPCal

"C:\Program Files\Internet Explorer\iexplore.exe" -nohome

(Sorry for not responding sooner... I'd given up on Vista and went back to XP.)

The reason IA is opening IE is that's because it is what is registered in the system as the default browser. FF is not properly registering itself I suppose.

[craigbrass]

Have you got the latest version of FireFox (2.0.0.4). This is supposed to work better with Vista.

[Ryan Lederman]

Originally Posted by Chris Boulton

The networking functionality in Kayako apps needs to be redeveloped.

This is annoying to say the least - especially when you have machines coming in and out of standby and drifting out of a wireless network connection.

The apps need to be designed that if they detected a connected/available network connection (as in marked as connected in Windows) that they only attempt to connect then.

I'm scouring the web for ways to be notified when the connection is available, and the only thing I've come across is InternetGetConnectedState() in the WinINet API. I wonder if there's anything I am missing...