QuickTime Sabotage

[Mitch Stone <mstone@vc.net>]

Another log on the fire. Published today on Macintouch.

http://www.macintouch.com/qtsabotage.html 

QuickTime Sabotage - more info 

Date: Mon, 9 Nov 1998 21:17:45 -0500 
To: jason@osc.edu From: Jason Suitts 
Subject: QuickTime for Windows Sabotage -- more info 

Hello,  

I'm writing in response to articles concerning Microsoft's response to 
QuickTime for Windows "sabotage." I've read the reports from  

http://msdn.microsoft.com/developer/News/quicktime.htm  

and I'm rather disturbed by the claims of the "independent" companies.  

The report from MindCraft contends that there is some huge bug in 
QuickTime. But if you read the entire document carefully, the only thing 
it actually shows is the QuickTime Plug-in doesn't register itself to 
play files with filename extensions ".qt", ".vfw", or ".aifc". But there 
is a simple explanation for this "problem," the filename extensions 
".qt", ".vfw" and ".afic" are not standard filename extensions.  

Files ending with ".qt" are QuickTime movies, but they are supposed to be 
saved with the extension ".mov". Files with ".vfw" are supposed to be 
".avi" and files with ".aifc" are supposed to be ".aiff". QuickTime 
Plug-in 2.0 correctly registers this filetypes. The ".mov" and ".avi" 
name extensions can be verified at:  

http://www.apple.com/quicktime/developers/ffdv.html  

Nobody uses ".qt" or ".vfw" unless they don't follow convention. 
Microsoft Word for Windows doesn't open files with the extension ".mwd", 
so why should QuickTime open ".qt" or ".vfw" files?  

As for other problems with playing QuickTime movies under Internet 
Explorer, well that's why I use a Mac! Also, from my experience, 
QuickTime movies in PowerPoint 97 under NT don't play audio, even with 
all the patches applied.  

~ Jason Suitts 
Ohio Supercomputer Center 
jason@osc.edu 

Mitch Stone
mstone@vc.net