QuickTime 16Bit Bug

[FLswimmer]

Does anyone out there have a workaround for getting Quicktime 16bit (not the 32bit or 4.0 versions - they work fine) to work with either the 4.51 or 5.13 G200 drivers? Matrox has been aware for many months that running ANY Quicktime 16bit based program would immediately cause the Windows 95/98 Blue Screen of death. I thought Matrox would fix this problem with their 5.13 drivers. But, of course, they haven't. And please don't respond to this message with something like, "Just stop using QuickTime 16bit"...that's not an option!! We are forced to continue using the 4.33C drivers (they work with QT 16bit) until Matrox sees fit to fix this HUGE bug. Anyone out there have a workaround until they do? Thanks!

[Thornogson]

Yes!

FLswimmer, I was pulling my hair out trying to get DK's Enc. of Science 2 to work using Quicktime 16bit and suffering the same dreaded blue screen of death...

What worked for me was to change a line in the QTW.INI file (in the Windows dir). Under the [Video] section, try changing:

Optimize=Hardware

to

Optimize=BMP

This should do the trick - good luck!

[Thornogson]

Yes!

FLswimmer, I was pulling my hair out trying to get DK's Enc. of Science 2 to work using Quicktime 16bit and suffering the same dreaded blue screen of death...

What worked for me was to change a line in the QTW.INI file (in the Windows dir). Under the [Video] section, try changing:

Optimize=Hardware

to

Optimize=BMP

This should do the trick - good luck!

[FLswimmer]

Thank You! Thank You!! Thank You Thornogson!!! That worked perfectly! I can now use QuickTime 16bit with my 5.13 drivers! Even Matrox tech support was unable to solve that one. Thanks again!!!!

[Thornogson]

No problem.

The only thing to keep an eye on is if you install something new that uses QT16, it may overwrite the QTW.INI file. You may need to check that it still has the change after such an install.

[Joel]

So it was a Quicktime problem after all.

Joel

[This message has been edited by Joel (edited 07-04-99).]

[mragsdale]

Hehehe, WeLLLL I'LLLL Be Damned!

[FLswimmer]

Thornogson, thanks again. Yup, I would know what to check for from now on. I'm a Systems Analyst with over 20 years of programming/hardware experience (no kidding). I'm not saying this to brag, but just to let you know that I'm not an inexperienced user Ummm, Joel, HOW ON EARTH can you make the determination that it's a QuickTime bug rather than a Matrox driver problem? It ABSOLUTELY still could be a Matrox driver bug. I'll guarantee you that if Matrox let me at their driver code (wouldn't happen), that I could find the problem and fix the QT issue in their driver. But I'm not going to belabor the point. And it really doesn't matter I'm just extremely happy right now that Thornogson had the solution to my problem! Thanks again bud!! Hopefully I'll be able to help you out in the future with a software/hardware problem that you are having. Now I see why people get discouraged when running their own web sites or posting to forums...instead of Joel being happy for me and saying something positive like "Cool, I'm glad you found a solution to your issue. I'll have to remember that one for future reference", he tries to rub a little salt in a wound. Come on bud be a little more positive Since I have all my outstanding issues solved now, I won't be back to this forum to post (or read posts). Thanks again Thornogson!! I hope you had a great weekend!!!!!

[Ron]

Joel
Some people don't like having their preconceptions questioned. I to have seen the problem with other cards. The last one I can think of was a Trident based card. I think this is simply a case of QT16 being older code which does not comply properly with Windows and therefore doesn't always play nice with all applications.
Ron

------------------
BH6 450A 128MB CW7502B CDR SR8583 DVD SBlive! Value Hollywood + AL320N USR Sportster etc. Oh, 8MB G200 Mystique too!

[Haig]

Swimmer, read my reply to you on the other QT thread.

Read what I have posted there and then look at the fix. this should EASILY tell you what the problem is.

Haig