Windows 98 can't run Quicktime 7? I'm obsolete for the first time?

:cry:

All I want to do is watch some movie trailers, and I loaded and reloaded the pages, wondered WTF is going on... after about the fifth time trying to load the Da Vinci code trailer, I noticed the little thing saying it required Quicktime 7.

That stinks. A lot. I tried the Quicktime alternative, but that didn't load right. Might try that again. I really want to see that trailer!

it's worth it.

It's pretty sad when I can't even spare a hundred bucks.

I guess it's like expecting Quicktime to make a version for Dos 3.1 or something, LOL!

Which is what I run.

I don't care much for the Tiger interface and later.

LOTS of problems with Macromedia Director based programs and other stuff too. Companies are scrambling to update their products to run with it. Apple sucked on this one.. They knew about the conflicts but simply didn't give a crap. :grr:

The new H.264 compressor is a greedy son of a bitch so far as processor usage is concerned. Older OS's running on older hardware wouldn't do well with it. It's a great compressor, though, making great quality videos at a smaller file size.

The new QuickTime incorporates a lot of new technologies: Core Video, H264, video recording, etc.

I am actuallly a software developer for both Macintosh and Windows platforms. I must say Apple is VERY good at preparing vendors for new versions of their software components... We get alpha and beta versions many months in advance, and and are able to test our code. When we find problems, it is a simple matter of getting rapid response from Apple engineers when an incompatibility is discovered.

Too often, software companies are not particularly proactive so far as making sure their software works with upcoming versions of components such as QuickTime or a new cut of the OS, and they get caught with their pants down. The easiest solution is to blame Apple, but these companies should have been testing their stuff with the pre-release versions and getting these issues ironed out.

6 months ago we released products made with a version of Director that locks up with the new version of QT there is a huge problem for developers that use both tools.

They could have put a bit more effort into that compatability. We dropped QT before and went with Smacker - I see this happening again because of crap like this.

... and it don't work like that. ANY large company, be it Apple, be it Microsoft, etc, will make every possible effort to maintain compatibility. BUT it is unreasonable to expect the company providing the OS to do regression testing on all third-party code, as there are literally thousands of applications out there. The best they can do is inform the developers that stuff is being rearchitected, and provide pre-release versions for the third party vendors to use to test their stuff. If problems were found, the vendors can get back to Apple and say, this doesn't work with my stuff anymore, and a determination can be made whether Apple needs to change something in their code, or if the third party product wasn't using QuickTime correctly anyway.

Third party software companies are quite often rather lax in testing their software with new OS versions. As I said in my earlier post, developers get these things months in advance, there is little excuse for not testing with upcoming versions. I found some issues with Quicktime's font handling in Windows a few months ago, when testing a prerelease of a new version, and how it worked with my software. I got Apple on the phone, and had the issue resolved almost immediately. Because I KNOW shit happens when new versions are about to be released, I make sure the stuff doesn't break my code, and if it does, I know I can contact the engineers and get the problem resolved, or get a work around.

Apple also provided a QuickTime 7 un-install that would remove the thing and put QuickTime 6 back, should it be found that the third party software has not been patched to work with the new QuickTime version.

Macromedia should have tested their shit and gotten a patch out prior to QuickTime 7 being released, like any LARGE and responsible software company interested in not pissing off their customers would have done, especially in light that Apple had the betas for this stuff available for third parties to test with their software some 6 months prior to release.

I checked back on the support issues with their product and QuickTime 7, including some of the compatibility issues. It seems their players and such had problems with QuickTime 7 BETA versions that WERE patched by Apple. Yet when Quicktime went golden, there were some additional issues, for example with quicktime VR stuff that was actually due to Macromedia's screw ups.

I checked back on the support issues with their product and QuickTime 7, including some of the compatibility issues. It seems their players and such had problems with QuickTime 7 BETA versions that WERE patched by Apple. Yet when Quicktime went golden, there were some additional issues, for example with quicktime VR stuff that was actually due to Macromedia's screw ups.

the problem we have is we have apps that were already being sold with Director that now crash because of whatever issue Director has with QT7. We can't expect our customers to not install QT7 just because these apps and other Director based ones aren't working. We've had things to change over the years as technology changes but never had a crash that made our products unusable. It's making my life hell at work.

as of yet.