Date:    Tue, 19 Dec 1995 13:08:21 +0100
From:    XXXXX X Xxxxxx <xxxxx@xxxxx.xxx>
Subject: Remove from mailing list

If you can, please remove me from this mailing list. I'd really appreciate
it. Thanks.

>>We are getting ready to put out our first CD which uses more than a little
>>QT.  We are assuming that the end-user does not have Quicktime installed.  I
>>was wondering if anyone had experience distributing the QT run-time files on
>>CD, and how successful this was.
>
>A Director movie can tell whether QuickTime is installed with the
>quickTimePresent keyword.
>
>The actual version can be detected with
>the QTVersion() XFCN (supplied with DFM) or the Gestalt XObject
>from the MediaBook CD, on Macs; on Windows, the version can be
>returned from MCI command strings-- although there seems to be
>a bug in QTW 2.0.3.51. It returns "2.351" as the version number; but
>If this bug is fixed, future QTW versions would be numerically
>lower than older versions! I think you might also be able to get the
>QTW version (bug-free) by using DLLGLUE.DLL (on www.macromedia.com)
>with the MCI dll's, or using (I think) a Windows XObject that
>Paul Farry has made available *somewhere*, which uses C code from
>the QuickTime developers kit.
>
>QTINSTAL.EXE is the one-piece QTW Installer. Its operation can
>be customized with QTINSTAL.INI, as described in Charles Wiltgen's
>QuickTime FAQ. It can be "opened" from Director to install
>QuickTime. However, it will fail when called from Director if
>doing an *update*, rather than a fresh install, because Director
>will still be using the older version of the QuickTime files.
>In these cases, you need to instruct the user to double-click on
>QTINSTAL.EXE themselves, and exit Director.
>
>While QuickTime will work immediately after QTINSTAL.EXE finishes, the
>Lingo quickTimePresent function will not return true until Windows is
>restarted.
>
>
>On the  Mac, QuickTime installation is more complicated. Apple provides
>no installer per se, but counts on users to drag the right extensions
>onto te closed system folder icon.
>
>You can install the QuickTime files there yourself with Lingo, but there
>are a number of pitfalls. Different versions of QuickTime have had
>different names, so it's hard to check for and remove previous versions.
>You need to use the Gestalt XObject from the MediaBook CD to determine
>whether you're on a PPC and need to also install the QuickTime PowerPlug.
>A comprehensive installer would use XObjects to extract the 'vers'
>resource from extension files, check the file names, dates, creator types,
>and sizes to truly remove prior versions. There's also the problem
>that you can't just erase files from the extensions folder; you
>need to move them to the trash if they're currently in use. I believe
>Paul Farry's OSUtil XObject has methods for doing that.
>Finally, you can't use FileIO to copy the new extensions, because
>FileIO only works on the data fork. The MediaBook CD has an Xobject,
>MISC_X, which has a both-fork copy method; it's faster than FileIO, too,
>but not nearly as fast as the Rinaldi FileCopy XCMD.
>
>I have plans to create a single XObject to take care of all of this,
>but as I am very busy lately, I'm not at all sure when I'll be ready
>with it.