LiveCompare Support for 32- and 64-bit Internet Explorer Flavours

LiveCompare uses a number of ActiveX controls to provide its rich interactive - "studio" - user experience. With the rise of the 64-bit architecture and Windows OS flavours that support it, we've had a couple of support requests from users that despite going through the client setup find that they can't login and are prompted again to setup their browser.

Why?

The root cause of the problem is that they were the 64-bit flavour of Internet Explorer which won't use the 32-bit ActiveX controls that we supply with LiveCompare.

Since Windows XP 64-bit edition Microsoft have included 32- and 64-bit versions of Internet Explorer and set the 32-bit version as the default. Windows 8 changes things around a little bit. First there is the "fullscreen" version of Internet Explorer 10. This doesn't support ActiveX controls at all so it can't be used with LiveCompare. Then the 32-bit browser is really a 64-bit browser that cleverly decides what mode to operate in based on the page that you load. And then there's the recently released 64-bit version of IE 10 on Windows 7. This flavour of the browser really doesn't want to work in 32-bit mode, even when you explicitly launch the 32-bit version of the program, making it very difficult to access the LiveCompare studio UI.

Anyway, what everyone wants is a simple setup that just works no matter what flavour of browser is started.

And that's how it works in LiveCompare 3.1. The client setup has gained a few MB as it now contains both the 32- and 64-bit versions of the ActiveX controls.

Client Machine Architecture

What's Installed?

What's Registered?

32-bit

32-bit and 64-bit

32-bit only

64-bit

32-bit and 64-bit

32-bit and 64-bit

Conclusion

LiveCompare 3.1 simplifies the client setup experience in that it "just works" irrespective of machine architecture and browser flavour.

NOTE: The upcoming LiveCompare 3.0 refresh will also include support for 32- and 64-bit flavours of Internet Explorer. Watch for a Support blog post announcing the refresh release.