This thead tries to somehow answer the question of how to better view normally unviewable avis in a Mac, asked by... er... someone at this other thread, where it happened to be quite offtopic.
I guess your main concern is with so called DivX avis. First you have to understand that both Windows Media' avis and QuickTime's movs cannot be considered a format in the way you consider an image to be in gif or jpeg format. They would be more appropiately called software platforms or wrappers, since they are simply an envelope in which to hold different kind of media (video, audio, static image, flash, text, hyperlinkable areas...). But simply because of the way it turned out, people kept calling Quicktime and WindowsMedia "formats" (well, Windows' platform never had a distinct trademark until recently AFAIK) and the compressor used to shrink the video or audio "codecs", which stands for compressor-decompressor, and is what in reality would resemble what in a still picture is gif or jpeg as its format (or compressor in fact).
An application which communicates with Quicktime can use all Quicktime compatible codecs installed in the machine that the user is using, and if that application communicates with Windows Media it can use all Windows Media compatible codecs installed too. Take into account that you can stuff, say, an mp3 song into either an avi and a mov, so in essence both files would be the same format internally, but since they use different wrappers only a Windows Media engine would be able to read the mp3 inside the avi and only a Quicktime engine would be able to read the mp3 inside the mov, and not vice versa, since both engines need their own particular codec to decode the mp3. That means, unfortunately, that each one's codec is not interchangeable (Quicktime's engine cannot use Windows Media Player's windowsmediavideo8 codec -microsoft latest video codec-). This also means that having a Quicktime engine does not guarantee that you will be able to read whatever mov, since your Quicktime engine also needs a certain codec to read a certain file. This is why certain movs require that you have a certain version of Quicktime installed, since the codec needed to read the file is only included with the standard installation of that version.
Somewhat fortunate for us Apple included in QuicktimePlayer both a Quicktime engine (of course) and a limited Windows Media engine. But as I said having the engine does not solve all our problems, since you need yet a particular codec for a particular file. Unfortunately the WM codecs included with QT are quite old and nowadays useless. Besides commercial codecs such as Windows Media Video 8 being developed as time passes and becoming somewhat standard in high quality WM sources in the internet, the same as we have Sorenson 3 which requires QT5, the Windows population is so enormously bigger compared to that of the Mac OS, that the percentage of "techno-geeks" (I am not saying this term with any offensive intentions, I hope nobody is offended) trying to go beyond standards burocracies and developing their own higher quality codecs turns into an absolute number much much bigger in the Windows platform than on the Mac OS.
Have you heard about all the fuss about Quicktime 6 and its "innovative" incorporation of MPEG-4. Well, as with most of things lately, rogue techno-geeks are well beyond us the mortals and have been developing powerful and easy to use MPEG-4 encoders and decoders since a long time ago, avoiding license and pattents possible problems, and also, as expected, evolving tools based on unfinished standards which happen to later, sometimes, grow old not so healthy not complying later with agreed standards they tried to pioneer. And of course, this mostly happened in the Windows platform because of the simple reason that most of this "techno-geeks", out of probability, where Windows users. (Ok, this is not completely fair, QT6 does come with an innotive use of MPEG-4 which is its ability to play MPEG-4 broadcasts, which is a somewhat special and different technology than the one needed to play an already downloaded movie)
That's what DivX at the end is: MPEG-4 video in an avi wrapper. It is really only legacy and standard compliant MPEG-4 video in tracks encoded with DivX enconder v4 and on (they are currently on 5). DivX 3, identified by Quicktime as MPEG4v3 in the info window, is not standard compliant MPEG-4, and sure you could argue that they could have just waited for the standards to be more finished, but in the meantime they enjoyed a codec which represented quite a breakthrough in compression-quality ratios compared to what could be normally found at the time (first I saw it is 2 years ago) and we did not. It drove us Apple users nuts simply because, being it a rogue codec, there was no worthy Mac representation of research behind the same goal backed up by the money of a commercial firm (and thus having people on it 8h a day and compensate for the disadvantage). There are however open hearted techno-geeks on the Mac scene too, just not as many, so quite quite later than in Windows we had our own MPEG-4 decoders without the need to wait for the one included with Q6. The one I have tried which works like a pleasure is the 3ivX codec. It was originally another sideMPEG-4 similar but different from DivX AFAIK. The v4alpha version, which currently only decodes can read standard MPEG-4s encoded with whatever other encoder (DivX>3 or Q6) and even non-standard DivX 3. Get it at 3ivX.com.
I guess your main concern is with so called DivX avis. First you have to understand that both Windows Media' avis and QuickTime's movs cannot be considered a format in the way you consider an image to be in gif or jpeg format. They would be more appropiately called software platforms or wrappers, since they are simply an envelope in which to hold different kind of media (video, audio, static image, flash, text, hyperlinkable areas...). But simply because of the way it turned out, people kept calling Quicktime and WindowsMedia "formats" (well, Windows' platform never had a distinct trademark until recently AFAIK) and the compressor used to shrink the video or audio "codecs", which stands for compressor-decompressor, and is what in reality would resemble what in a still picture is gif or jpeg as its format (or compressor in fact).
An application which communicates with Quicktime can use all Quicktime compatible codecs installed in the machine that the user is using, and if that application communicates with Windows Media it can use all Windows Media compatible codecs installed too. Take into account that you can stuff, say, an mp3 song into either an avi and a mov, so in essence both files would be the same format internally, but since they use different wrappers only a Windows Media engine would be able to read the mp3 inside the avi and only a Quicktime engine would be able to read the mp3 inside the mov, and not vice versa, since both engines need their own particular codec to decode the mp3. That means, unfortunately, that each one's codec is not interchangeable (Quicktime's engine cannot use Windows Media Player's windowsmediavideo8 codec -microsoft latest video codec-). This also means that having a Quicktime engine does not guarantee that you will be able to read whatever mov, since your Quicktime engine also needs a certain codec to read a certain file. This is why certain movs require that you have a certain version of Quicktime installed, since the codec needed to read the file is only included with the standard installation of that version.
Somewhat fortunate for us Apple included in QuicktimePlayer both a Quicktime engine (of course) and a limited Windows Media engine. But as I said having the engine does not solve all our problems, since you need yet a particular codec for a particular file. Unfortunately the WM codecs included with QT are quite old and nowadays useless. Besides commercial codecs such as Windows Media Video 8 being developed as time passes and becoming somewhat standard in high quality WM sources in the internet, the same as we have Sorenson 3 which requires QT5, the Windows population is so enormously bigger compared to that of the Mac OS, that the percentage of "techno-geeks" (I am not saying this term with any offensive intentions, I hope nobody is offended) trying to go beyond standards burocracies and developing their own higher quality codecs turns into an absolute number much much bigger in the Windows platform than on the Mac OS.
Have you heard about all the fuss about Quicktime 6 and its "innovative" incorporation of MPEG-4. Well, as with most of things lately, rogue techno-geeks are well beyond us the mortals and have been developing powerful and easy to use MPEG-4 encoders and decoders since a long time ago, avoiding license and pattents possible problems, and also, as expected, evolving tools based on unfinished standards which happen to later, sometimes, grow old not so healthy not complying later with agreed standards they tried to pioneer. And of course, this mostly happened in the Windows platform because of the simple reason that most of this "techno-geeks", out of probability, where Windows users. (Ok, this is not completely fair, QT6 does come with an innotive use of MPEG-4 which is its ability to play MPEG-4 broadcasts, which is a somewhat special and different technology than the one needed to play an already downloaded movie)
That's what DivX at the end is: MPEG-4 video in an avi wrapper. It is really only legacy and standard compliant MPEG-4 video in tracks encoded with DivX enconder v4 and on (they are currently on 5). DivX 3, identified by Quicktime as MPEG4v3 in the info window, is not standard compliant MPEG-4, and sure you could argue that they could have just waited for the standards to be more finished, but in the meantime they enjoyed a codec which represented quite a breakthrough in compression-quality ratios compared to what could be normally found at the time (first I saw it is 2 years ago) and we did not. It drove us Apple users nuts simply because, being it a rogue codec, there was no worthy Mac representation of research behind the same goal backed up by the money of a commercial firm (and thus having people on it 8h a day and compensate for the disadvantage). There are however open hearted techno-geeks on the Mac scene too, just not as many, so quite quite later than in Windows we had our own MPEG-4 decoders without the need to wait for the one included with Q6. The one I have tried which works like a pleasure is the 3ivX codec. It was originally another sideMPEG-4 similar but different from DivX AFAIK. The v4alpha version, which currently only decodes can read standard MPEG-4s encoded with whatever other encoder (DivX>3 or Q6) and even non-standard DivX 3. Get it at 3ivX.com.