Re: How to downgrade to an earlier version of QuickTime?
- From: dempson@xxxxxxxxxxxxx (David Empson)
- Date: Sun, 2 Dec 2007 14:12:19 +1300
Don Bruder <dakidd@xxxxxxxxx> wrote:
In article <1i8f1s6.1qjr1wpl95vnN%dempson@xxxxxxxxxxxxx>,
dempson@xxxxxxxxxxxxx (David Empson) wrote:
Which version of QuickTime did you install which triggered the problem,
and which earlier version were you running which did NOT have the
problem?
That's part of the problem... I'm not really sure. Since switching to
Panther back in January, I've taken any and all updates that SU offers
me without any particular concern. I honestly don't have the first clue
about exactly when the breakage happened, or which version of QT I was
at before and after it showed up.
According to the modification datestamp on the bundle, near the end of
July I had no problem compiling a long-time pet project of mine that
links against QuickTime. That one got put on the back burner for a
non-QT project, and by somewhere around the middle of August, I was up
to my armpits in alligators with a project that didn't use QT. I was
concentrating on that, so I wasn't really noticing much else. Sometime
after that - I honestly can't say for sure when - Sometime in late
September to mid October? - when I finished working on that one, I
turned to another project - trying to add .PNG recognition to the
"EtherPeg" code. That's when I first got the link failure complaining
about HIPointConvert being missing.
So it seems that some time between July and October, you installed a
QuickTime update which introduced the problem.
Looking through Apple's support downloads, I see that QuickTime 7.1.6
was released on 1 May, QuickTime 7.2 was 11 July, and QuickTime 7.3 was
5 November. (I downloaded QT7.3 on 1 November, so the dates on Apple's
support pages may be due to a later change to the description.)
This suggests that QuickTime 7.2 might be the problem, but only if you
delayed installing it, or your "late July" build managed to avoid the
problem somehow, perhaps because it only compiled some files in the
project.
There was also a "Compatibility Update for QuickTime 7.2" on 11
September. This supposedly made changes which improved things for iLife.
This is right within your window of the problem appearing, so seems the
most likely cause.
It might also be due to updated developer tools installed during the
timeframe in question. I can't see any of which I have archive copies.
Pacifist is a shareware utility which lets you open up an installer
package and examine its contents, including extracting or installing
individual files.
Yep, I've been looking at it.
Trying to do this by hand is likely to be tricky, especially if you
aren't familar with them.
What, if any, harm is likely to come from turning it loose to install
the whole darn thing, and to hell with any "leftovers" that might get
left laying around? Beyond the obvious "Well, you're wasting disk space"?
You are likely to end up with an unstable system, because a newer
version of QuickTime may have modified a larger set of files than the
old version. The additional files will NOT be restored to their previous
version, and they could be attempting to make use of data or code in
other files which are supposed to be from the same version of QuickTime.
If those other files have been downgraded then the expected data or code
may not exist or may be incompatible, which could result in crashes or
data corruption.
If you are a registered developer (even online, which is free), you can
file an official bug report at http://bugreporter.apple.com. You will
need to provide detailed information about the problem, but it provides
a means for Apple to give you some feedback if they decide to do
anything about it, and you can examine the status of your bug report to
see if anything has happened.
I'll give that a go. Can't hurt anything, I guess, and this definitely
qualifies as a major "bug"...
I can understand, and even agree with, the idea of improving QuickTime.
But something is wrong when the improvement, whatever it is, will allow
existing code to run, but won't permit new code to be built, there's
something wrong.
At the very least, I'd like to see the HIPointConvert() dependency in QT
either removed, or resolved internally - but that's just me...
HIPointConvert() is only available on 10.4.x and later, yet whatever
version of QT it is that the dependency appears in runs just fine on
10.3.9. Which indicates to me that HIPointConvert() IS NOT critical to
QT operation - Or if it is, it's somehow dealt with in the new,
dependent code. But no new code can be linked on 10.3.9 because QT
depends on something that's only available in 10.4.x. What doesn't add
up here?
Can you tell exactly which library is triggering the problem?
As far as I can see, Compatiblity Update for QuickTime 7.2 only modified
/System/Library/QuickTime/QuickTimeComponents.component. This seems less
likely to be a cause for the problem you are describing.
--
David Empson
dempson@xxxxxxxxxxxxx
.
- Follow-Ups:
- Re: How to downgrade to an earlier version of QuickTime?
- From: Don Bruder
- Re: How to downgrade to an earlier version of QuickTime?
- Prev by Date: Re: Giving Up on Leopard
- Next by Date: Steinberg Xphraze, The Music Box, VSL VIENNA SYMPHONIC LIBRARY, INSTRUMENTS I, II, and EWQLSO, COLOSSUS, RA, CHOIRS, East West Quantum Leap Symphonic Orchestra library
- Previous by thread: Re: See whose connected to Airport?
- Next by thread: Re: How to downgrade to an earlier version of QuickTime?
- Index(es):
Relevant Pages
|
