28
Possible fix for Windows QuickTime 7 bug?
Posted by | Posted in Bugs | Posted on 11-28-2005
We’re not sure how we missed the solution back on November 14th, but here’s a link to the thread:
Keynote QuickTime Issues on Windows QT 7
The solution is near the end of the thread.
So what’s the big deal?
It seems that when Internet Explorer is set as the default browser in Windows, Interactive QT movies made from Keynote don’t work properly in QuickTime 7. The solution up to this point was to go back to using QT 6.5.2. User gillettebl found a better solution, which is to change the default browser to something else (in this case Firefox).
Here’s a quote from his post:
“Yup, the error manifests when IE is the default browser… but not if using Firefox. Try this: Start…Set Program Access and Defaults (or Start…Control_Panel…Add or Remove Programs; choose the lowest tab on the left), and tell it to use Firefox as the default browser.”
Another user points out that this is still a problem since most of the world won’t know to change their default browser, but at least it’s a good start to getting full interactive functionality on a Windows machine.
Changing the default browser to Firefos doesn’t fix the problem. Running a Keynote-generated Quicktime slideshow with either browser as the default browser will demonstrate the bug, but in different ways. Firefox launches and gets in the way immediately, while IE brings up an alert, then comes into view after you dismiss the alert. Apple: Is there any work going on to actually fix it?
I confirm all that Alan has written. There are many persons whom they use iTunes for windows and that they have installed QuickTime 7.
I also need a solution to this problem. Created a great interactive presentation for my boss to take on a trip, but he uses a Windows PC. At first I was glad he had QT7 because I like to output in H.264. Then I discovered this bug. Going back to QT6 could be an option – but too late for this trip, since I would have to recompress and output everything again.
Elated at the first part of this thread: thought I found a solution that showed Windows was at fault and could be fixed (by changing default browser). Now it seems as though it is a QT fault, since interactive hyperlinks in QT6 apparently work as intended. So, yeah, what’s the deal Apple – I am trying to win my boss over.