![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Mindcraft's QuickTime Plug-In Analysis and Fix |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DownloadsQuickTime plug-in fix installer [656KB exe file] |
Microsoft hired Mindcraft, Inc. as an independent test lab with the following assignment:
The technical details of our work are presented in a separate document entitled Detailed QuickTime Plug-In Problems, Analyses, and Solutions [a 168KB PDF file]. For a less technical perspective, look at our Summary QuickTime Plug-In Problems, Analyses, and Solutions [a 62KB PDF file]. Mindcraft tested whether or not Internet Explorer uses the QuickTime plug-in when it encounters an EMBED HTML tag. Our tests used Microsoft-supplied media files with 11 filename extensions that the QuickTime plug-in supports. We found three test failures where Internet Explorer did not invoke the QuickTime Plug-in as expected. Each failure was the result of one or two Apple errors as shown in Table 1. Apple had the knowledge to correct these errors because, as Table 1 illustrates, Apple properly set the information to tell Internet Explorer to use the QuickTime plug-in for 8 of the 11 test files. Table 1: Apple's QuickTime Plug-In Errors
Based on our detailed analysis of the problems, we conclude that Microsoft did nothing malicious to cause the QuickTime plug-in to fail. In addition, we find that Apple has bugs in its QuickTime plug-in and its installer that prevent the plug-in from working properly. |
![]() |