quicktime.txt ================== Ok, I thought I’d take a moment to explain QuickTime for everyone. I know some people already know this stuff, if you do forget the email. I thought this info would be useful for others though. QuickTime has 3 basic formats: QuickTime 16 (the 16 bit version for Win 3.x), QuickTime 32 (the 32 bit version for Win9x), and QuickTime 3.0 (also a 32 bit version for Win9x). Each of these formats has several or more versions. There are a bunch of versions of Qt16, and several of Qt32, and I think just one so far for Qt3.0 Anyhow you can have all three of these formats in a computer at one time. Even though this is the case only one version of each can exist in a computer at once. It’s best to have the latest of each of these formats installed. Once this is the case you don’t want to install Qt anymore for risk of installing an older version of one of these formats. Now backwards compatibility. QuickTime 3.0 is backwards compatible after a fashion. Once a file association is setup it can play Qt files for both the Qt16 and Qt32. Meaning I have Qt3.0, I can double click on a file meant for Qt16 or Qt32 and it will play. While this is true it doesn’t replace the others. Programs are specifically written for one or more of the above. These programs are specifically written to use the movie player (or whatever) of a particular Qt format. So if I have a program that uses Qt16, the program will not use Qt3.0 in place of it. Ok, I know this is probably beating it to death. But some people still don’t seem to know about this. Figured it might be helpful for some people. We all know by now that certain video cards give a fatal exception when trying to play QuickTime. The problem seems to be that the particular video card cannot handle putting out QuickTime video’s in some of the higher defaulted settings it will use. There are several fix’s for this. The best thing to do is tell them to update their drivers. Unfortunately I don’t know if this is always going to be applicable. I’m sure there are some video cards using the TNT chipset that don’t have updated drivers addressing the problem. So you can tell them to update them, but there may not be an appropriate update for the problem and they have to call back. The best solution is to actually get the program working, and then tell them to update the driver. Another solution that has gone out was to lower the hardware acceleration. This solution is an inappropriate one. True it works, but at cost of their other software not working. Dropping the hardware acceleration should not really ever be done, other than for testing purpose’s. It’s a valid fix perhaps when you have done everything else that can be done, but never otherwise. There is an additional fix recently sent out by Eric regarding a QuickTime INI adjustment. This is a valid fix and works, but only for Qt16, it does not work for Qt32. Another method that does work for both of them. Is to have the customer boot into safe mode. This is done by pressing F8 at the proper time during bootup. The proper time is hard to really get for some of them. It’s after the memory test and just after the hdd detection. When getting into safe mode, you will actually be able to open up the QuickTime properties box’s in the control panel. Wherein you can adjust the draw method to Bitmap or Raw Bitmap. This seems to me to be the best solution for the QuickTime issue. Of course along with the Update your video driver when you get a chance line. You can also get into the Quicktime Control Panel, click on MORE, Click on VIDEO, and lower it from there... most of the time you have to lower the graphics acceleration in order to even open the QT Control Panel..... but then you can change it back, and don't have to do the "hit F8-now now now now" dance... [best solution follows: edit the qtw.ini file.] =================== Fatal exception 0E errors caused by Quicktime. Edit the Quicktime INI file (qtw.ini) as follows. Click on Start, Run. In the Run box, put in just "qtw.ini" and click OK. This will open a Notepad file. Look at the first two lines in the file. They will be something like this: [Video] Optimize=Hardware (It may say Optimize=Driver or something else.) Change that Optimize= line so that it says Optimize=BMP Look for any other lines in the file that start with Optimize= and make the same change to them. (There might not be any other lines like it, but just in case.) Click on File, Save to save the file, then File, Exit to exit from Notepad. Try the program again. FATAL OE ERROR and QTW.INI NOT SAVING CHANGES: When you receive a Fatal OE Error and you edit the QTW.INI, please take note to how many lines are under the [Video] section. If the PreferredComponent=C:\WINDOWS\SYSTEM\QTVHDW.QTC appears, the line must be REMed out by placing a semicolon (;) at the beginning of the line. This line, if not REMed out, will negate the changes you made to the QTW.INI once the system is restarted. ***Please Note: This fix does not apply when editing the [Video32] section of the QTW.INI. ============================== Sound is all sped up, like a old-style tape recorder on fast-forward. The JumpStart Spanish needs a version of Quicktime generally called "Quicktime 32-bit." The Quicktime 4 that you have is completely different from it. It is entirely possible to have three different "flavors" of Quicktime on your system at the same time, used by different programs; you would see them all listed in the Control Panel. These would be the 16-bit Quicktime, the 32-bit Quicktime, and the Quicktime 3 (or 4 now) which you already have. To install the Quicktime 32-bit from the JumpStart Spanish CDROM, click on Start, Run, and put in "d:\Support\Winsys\QT32.exe" (where "d:" is your CDROM drive letter) and click OK. Be sure to have it check for existing versions and delete them; it will probably find two copies, and it will not affect your Quicktime 4 at all by removing them. Then it will put in the Quicktime 32-bit, and then your JumpStart Spanish should run properly. ============================== Sound clicking - like a woodpecker HP, Win98, Ensoniq audio PCI. Turned out to be Quicktime32. Deleted it completely, also deleted qt*.* and *.qtc, restarted, reinstalled JSSpan and QT32. Works. Also encountered qt32 caused IPF in kernel32.dll at 017f:bff7a138 when we tried to reinstall QT32. That's why I manually deleted it and reinstalled and did NOT check for existing versions. =============================== "Unable to create Window" error message (Typically because they ran the icon before the install was completely finished.) They need to make sure Quicktime is installed too. Run "d:\support\winsys\qt32.exe" to install Quicktime32. An alterate solution in case that doesn't work: Trying to install it. Says "Unable to create Window." Deleted JSTyping dir. Cleaned CD. Reinstalled it (suspect he didn't let it completely finish installation before). Ran it; works. - - - - - When she tries to run it, it says "unable to create window." Installed QT32 from the CD; it detected an incomplete install from before; had her do it fresh. Got an error: QT32 caused IPF in qt32.exe at 0167:0040ab64. Restarted Win98. Uninstalled all Quicktimes using Add/Remove. Deleted JSTyping dir. Reinstalled it. Ran into same error during the Quicktime installation. Restarted Win98 again (so the files wouldn't be locked); the qt*.* and *.qtc files said access denied; had to reset the attrib on them, then could delete them (finally). Now TRIED to reinstall QT32 again and it STILL says there was an incompleted attempt from before; told it to start a fresh one again; once more got the same error. Best info I could find says: delete all temp files; delete qt*.* and *.qtc from \windows and \windows\system dirs. Beware of other programs like Quicken which sometimes use these names. Called her back. Cleared out the temp files. C: has 3.55 GB free (10 GB total capacity). Used Find to locate all qt*.* and *.qtc files in system; deleted those that weren't part of Adobe Pagemill or Quicken, etc. Ran the QT32 from the CD again; this time it didn't mention prior version. Told it NOT to check for existing versions. It proceeded without errors and finished. Ran JSTyping. It's working (finally). Seems the key here is to NOT have it check for existing Quicktime versions, just skip that portion. ====================================== Program: Reading Blaster Jr. IPF at 015f:00416548. Changed the Optimize to BMP in QT.INI. Works. Fault occured when a QT movie started to play. ========================== Quicktime 4 requirements Mac OS 68020, 68030, 68040, or PowerPC processor (PowerPC processor recommended for effects, 3D, Floating-Point Audio, DV, MPEG, RTP streaming features, or QDesign Music) 680x0-based Macintosh computers must also support Color QuickDraw At least 8MB of RAM recommended for 680x0-based computers; at least 16MB of RAM recommended for PowerPC processor-based computers Mac OS 7.1 or later. QuickTime's RTP streaming works with Mac OS 8.0 or later because it requires OpenTransport 1.2--or later--part of Mac OS 8.0. Windows Intel or compatible processor or any MPC2- compliant PC (minimum 66-MHz 486 processor; also supports Pentium, Pentium Pro, and Pentium II with MMX processors; Pentium processor recommended when using effects, 3D, Sorenson Video, DV, RTP streaming features, or QDesign Music) At least 16MB of RAM Windows 95, Windows 98, or Windows NT 4.0 system software Sound Blaster or compatible sound card and speakers Installation of Direct X version 3.0 or higher is recommended for best performance Installation of DirectDraw and DirectSound drivers is recommended for best performance. ======================