-
Toruwatanabe
May 17, 2007 at 4:03 pmEmbarrassingly, I guess I don’t know how to properly uninstall the latest Quicktime version.
I just downloaded QT 7.1.6 when my problems started, and I tried removing the necessary files to get back to QT 7.0.1—but the G4 keeps telling me I’m running 7.1.6. I know Quicktime is a bit different from most programs, in terms of where the files are kept, etc.
So I very sheepishly would ask now how to step-by-step go back to the old QT??? -
Toruwatanabe
May 17, 2007 at 4:06 pmWord, totally agreed… at this point I am a little stuck in my dense caveman brain about how to revert Quicktime back to the earlier version (which would be 7.0.1).
-
Arthur Dent
May 17, 2007 at 4:26 pmAh Quick Time…. Apple has to write a ‘re-installer’ or something like that to roll back to a previous version (why would they want to make it easy?)… so Rolling back to a previous version of QT is harder than it sounds, and I don’t think they’ve writen a QT re-installer in a while.
if you have the auto software update manager turned on, turn that thing off now and save yourself future head aches…
My $.02
A.D. -
Andrew Mehta
May 18, 2007 at 6:46 amApologies if reverting to an earlier quicktime is easier said than done.
All I meant was, to try the free suggestions before paying for tech support. I use OS9 more than OSX, so I may have been out of my depth, although you may find some help on Apple’s Quicktime support page:
https://www.apple.com/support/quicktime/If reverting to an earlier quicktime is proving problematic, how about setting up a new login and seeing if M100 will run via that? That was the other suggestion someone made, that should be easy to try out.
If neither approach works, I’d give Dave an email.
-
Kieran Matthew
May 18, 2007 at 12:40 pmHi ToruWatanabe,
At the risk of becoming another voice in this thread, I just thought I’d chip in with some observations. Apologies if this has been covered already (it’s a long thread!)
I’m currently running two media 100i suites and both are using the current quicktime versions without any issue. Although on the surface it seems that the QT update is to blame, I reckon there’s more to this.
Couple of things. When did you last repair permissions on your OS drive? Weird happenings can sometimes be attributed to permission issues.
Secondly, do you have the software codecs installed, and the media100-codec component removed? This is just wild guessing, but the codec component especially used to cause compatibility issues.
HTH
K -
Toruwatanabe
May 19, 2007 at 7:44 amFor what it’s worth , here’s some stuff from the crash log that stands out—I don’t understand this, but here goes:
“Failure at call to HAL_ABORT_OUTSTANDING_JOBS
bad status in Remote_HAL_Abort_Outstanding_Jobs -19308
Failure at call to HAL_ABORT_OUTSTANDING_JOBS
bad status in Remote_HAL_Abort_Outstanding_Jobs -19308
Looking for devices matching vendor ID=1193 and product ID=8718
Looking for devices matching vendor ID=1193 and product ID=8717
Frame Engine 1 is active 180f200
Open Frame Engine in a release 1
Failure at call to HAL_ABORT_OUTSTANDING_JOBS
bad status in Remote_HAL_Abort_Outstanding_Jobs -19308”The HAL part matches something I’ve seen in earlier Media 100s when they didn’t open…
Reply to this Discussion! Login or Sign Up