Post
by aoi_neko » Wed Aug 10, 2005 12:52 am
Just to nitpick here, first let me point out that if a codec crashes or freezes the system, it's never really the codec's fault. The worst a codec ever SHOULD be able to do is to crash the player. If the operating system allows a process gone bad to crash the whole computer, it's a flaw in the operating system. The worst you should ever see is "Process <foo> attempted an illegal operation and is being terminated," or something like it. But we ARE talking about Windows here, and yeah, Windows has some problems in that regard. Windows Media Player especially has problems in that regard, because, like the browser, MS has tried to make it as indivisible a part of the OS as possible. So,if you're using WMP it reallly doesn't shock me all that much that a failure in that drags the system down with it.
People are blaming your computer because when dozens of computers with a wide variety of OS levels and graphics cards all run divx without problems, and yours does not, the codec itself seems like an unlikely cause. That seems even more likely if something besides WMP plays it without problems.
To directly answer the question in the topic, people don't generally use a codec that THEY think is unstable. The assumption is you've got some sort of software conflict so that when you try and play a divx video, something happens on your machine that doesn't happen on ours.
Is the 4CC of the problem files actually DIVX? Or are they something else like DIV3, DIV4, XVID or MPG4? Have you installed anything like avicodec or gspot to see what exactly is handling that specific 4cc??
<i>"Tamago no kara wo yabureneba hinatori wa umarezu ni shin de yuku. Warewa ga hina da. Tamago wa sekai da. Sekai no kara wo yaburaneba warera wa umarezu ni shin de yuku. Sekai no kara wo hakai se yo. Sekai wo kakumei suru tame ni!"</i>
