
	    3D Blaster Common Questions and Answers
	    =======================================

This file contains a list of some common problems faced and the
solutions to those problems.  Please read the sections below if you
encounter a problem.  If your problem is not described below,
you can call our Technical Support at (405) 742-6622.  

---------------------------------------------------------------------

Problem:
   Quicktime Movie Player crashes at times.

Cause:
   The Quicktime Movie Player detects hardware every time it is
   started from Windows to use the maximum capabilities of the
   hardware.  This is recorded in the QTW.INI file in the Windows
   directory.  Unfortunately, at this time the detection process is
   not detecting the 3D Blaster hardware, thus giving rise to the
   problems.

Solution:
   1)  Edit the QTW.INI file.
   2)  In the Video section (add one if it does not exist) add the
       following line:

       [Video]
       optimize=driver

   3)  Save the QTW.INI file.

   This forces Quicktime to use the installed Windows display
   driver and thus use the 3D Blaster drivers.

   However, if Quicktime crashes in this manner (without the above
   line added), especially in 1024x768, the only way to resolve this
   is to switch resolutions (down to 640x480 or 800x600), start the
   Quicktime Movie Player and change back to 1024x768.

   Note: Viewing the Quicktime readme file (uses readme.exe which
   comes with Quick Time) WILL cause this to happen every time even
   with the modified INI file.  To recover, use the method
   described in the paragraph above.

   This problem is not strictly related to the 3D Blaster and does
   happen with many other video cards.



Problem:
   When installing the 3D Blaster, after the install program reboots 
   your machine, the DOS error, "Invalid System Disk" or
   "Non System Disk" is displayed.

Cause:
   The system is trying to boot from the floppy disk in drive A:,
   which is not a system bootable disk.

Solution:
   Eject the disk in drive A: and press <ENTER>
 


Problem:
   Windows 95 does not recognize the 3D Blaster.  Running "SETUP.EXE"
   executes "CMPATCH.EXE", and after rebooting, Device Manager still
   does not have 3D Blaster under the list of recognized display
   drivers.

Cause:
   Installing Windows 95 with the 3D Blaster in the system causes
   Windows 95 to add 3D Blaster to its list of recognized hardware.
   Since 3D Blaster is "recognized", Windows does not ask for the
   drivers disk when rebooting after running CMPATCH.EXE

Solution:
   In Windows 95, follow the procedure listed below: 
    *  Select "START", "SETTINGS", then "CONTROL PANEL"
    *  Open the "SYSTEM" icon from the "CONTROL PANEL" window.
    *  Select the "Device Manager" tab in the "SYSTEM PROPERTIES"
       window.
    *  Click on the plus sign next to the "UNKNOWN" device. 
       (represented by a question mark icon.)
    *  Double click on the "Creative Labs 3D Blaster" icon.
    *  Select the "DRIVER" tab.
    *  Press the "CHANGE DRIVER" button.
    *  Press the "HAVE DISK" button.
    *  Select the drive that the 3D Blaster Windows 95 drivers are 
       located on. (Typicaly "A:")
    *  Press "OK"
    *  Run "READHELP.EXE" from the 3D Blaster Windows 95 drivers
       disk.
    *  Follow the listed procedures to disable your previous display
       drivers and configure the 3D Blaster display drivers.

  

Problem:
   When running in a Windows GUI environment the display is normal.
   When using DOS based programs from within a Windows environment
   the display is not stable (can not view the image).
  
Cause:
   The Pass-Through cable may have come loose.

Solution:
   Check to ensure that the Pass-Through cable is firmly connected
   to the video card and the VGA input connector on the 3D Blaster.



Problem:
   READHELP.EXE starts with the description of how to disable existing
   display drivers.

Cause:
   READHELP.EXE is intended for use with the 3D Blaster installation
   procedure.
   
Solution:
   For the full 3D Blaster help file, open README95.HLP


		 ==========  End of CQA.TXT  ==========

