The Best of Select: Games Special 3/cd.iso/wingames/fury3/readme.txt

Text File | 1995-09-14 | 33KB | 921 lines

------------------------------------------------------------
   Microsoft Fury3 Trial Version README
   September 1995
------------------------------------------------------------
   (c) Copyright Microsoft Corporation, 1995

   This document contains important information specific
   to the Microsoft Fury3 Trial Version.

   The Microsoft Fury3 Trial Version has the full
   functionality of the retail version  of Fury3 with these exceptions:
   - The Trial Version does not support the "Show Videos" option in
     the Game options dialog box, so videos do not play.
   - You can only fly one mission.
   - You cannot save or resume games.
   - Graphics in the Trial Version's online Help are 16-color,
     and therefore are not as high-quality as the Windows 95
     Help graphics in the retail version of the game.


   ----------------
   CONTENTS
   ----------------

A. Installation Notes

   >  License Agreement
   >  Installing the Fury3 Trial Version
   >  Minimum System Requirements for the Fury3 Trial Version
   >  Recommended System Features for the Fury3 Trial Version
   >  Minimum System Requirements for the Fury3 Retail Version
   >  Recommended System Features for the Fury3 Retail Version
   >  Troubleshooting Microsoft Fury3 Setup
   >  Installing Fury3 from a Third-Party
      Shell (Windows 3.1 only)
   >  Using a Clean Boot to Resolve Setup Conflicts
      (Windows 3.1 only)
   >  Resolving Setup Freezes During Installation
      (Windows 3.1 only)
   >  Starting Fury3 if You Are Using the PC Tools
      Desktop (Windows 3.1 only)

B. Hardware and System Compatibility

   >  Optimizing Performance on Minimum-Configuration
      Machines
   >  Other Performance Issues
   >  Setting Up Programmable Joysticks (ThrustMaster,
      Gravis)
   >  Increasing the Size of Your Swap File
      (Windows 3.1 only)
   >  Growstub Error (Windows 3.1 only)
   >  EMM 386 Exception Error (Windows 3.1 only)
   >  Win32s Error (Windows 3.1 only)

C. Video Driver Notes

   >  Changing the Video Display to 256 Colors
   >  Unhandled Exception Error for the S3 Video Driver
      (Windows 3.1 only)
   >  Using an ATI mach32 or mach64 Display Driver
      (Windows 3.1 only)

D. Sound Card Notes

   >  Troubleshooting Sound Cards

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

-----------------------------------------
  A.  INSTALLATION NOTES
-----------------------------------------


   -------------
   >  License Agreement
   -------------
By copying or using this Fury3 Trial Version, you indicate
your agreement to the terms of this license agreement.  If
you do not agree to the terms herein, you are not authorized
to copy or use the Trial Version.

The Fury3 Trial Version,  including any images, photographs,
animations, video, audio, music and text incorporated in the
Trial Version, is owned by Microsoft or its suppliers and is
protected by United States copyright laws and international
treaty provisions.   Except to the extent expressly licensed
herein, all rights are reserved to Microsoft and its suppliers.
You may not reverse engineer, decompile, or disassemble the
Trial Version.

Limited Warranty and Limitation of remedies:
NO WARRANTIES.  To the maximum extent permitted by applicable
law, Microsoft expressly disclaims any warranty for the Fury3
Trial Version.   The Trial Version and any related
documentation is provided "as is" without warranty of any kind,
either express or implied, including, without limitation, the
implied warranties of merchantability or fitness for a
particular purpose.  The entire risk arising out of use or
performance of the Trial Version remains with you.
Microsoft's entire liability and your exclusive remedy, at
Microsoft's option,  shall be the cost of the Trial Version
or its replacement with another copy of the Trial Version.
To the maximum extent permitted by applicable law, in no event
shall Microsoft or its suppliers be liable for any damages
whatsoever (including, without limitation, damages for loss of
business profit, business interruption, loss of business
information, or any other pecuniary loss) arising out of the
use or inability to use this Microsoft product, even if
Microsoft has been advised of the possibility of such damages.
Because some states/jurisdictions do not allow the exclusion
or limitation of liability for consequential or incidental
damages, the above limitation may not apply to you.


   -------------
   >  Installing the Fury3 Trial Version
   -------------
If you installed the Fury3 Trial Version from a
CD sampler, no further installation is required.

If you copied the Fury3 Trial Version directly from
an online service or from disks, please note the
following instructions.

   To run the Fury3 Trial Version under Windows 95,
   run Fury3x.exe.

   To install the Fury3 Trial Version under Windows 3.1
   or Windows for Workgroups:

   1. Run setupx.exe.
   2. Exit Windows and restart your computer.
   3. Run Fury3x.exe.

NOTE: The Fury3 Trial Version requires additional
utilities (win32s, wing, dispdib.dll) to run under
Windows 3.1 and Windows for Workgroups. During
installation you may be prompted to install each one.


   -------------
   >  Minimum System Requirements for the Fury3 Trial Version
   -------------
*486DX/66 MHz or higher processor
*8 MB of RAM
*EITHER:
   -Microsoft« Windows 95« operating system
   OR
   -MS-DOS« operating system version 5.0 or later with
    Microsoft« Windows« operating system version 3.1 or
    later
*Available hard disk space:
   -For Windows 95, 15 MB of available hard disk space
   -For Windows 3.1, 17 MB of available hard disk space,
    plus a 10 MB swap file if you have less than 12 MB
    of RAM
*Local bus SVGA video, 256-color display
*Sound board plus speakers or headphones to hear audio


   -------------
   >  Recommended System Features for the Fury3 Trial Version
   -------------
*Joystick or other flight control
*Microsoft Mouse or other pointing device


   -------------
   >  Minimum System Requirements for the Fury3 Retail Version
   -------------
*486DX/66 MHz or higher processor
*8 MB of RAM
*EITHER:
   -Microsoft« Windows 95« operating system
   OR
   -MS-DOS« operating system version 5.0 or later with
    Microsoft« Windows« operating system version 3.1 or
    later
*Available hard disk space:
   -For Windows 95, 15 MB of available hard disk space
   -For Windows 3.1, 17 MB of available hard disk space,
    plus a 10 MB swap file if you have less than 12 MB
    of RAM
*Local bus SVGA video, 256-color display
*Sound board plus speakers or headphones to hear audio


   -------------
   >  Recommended System Features for the Fury3 Retail Version
   -------------
*Joystick or other flight control
*Microsoft Mouse or other pointing device


   -------------
   >  Troubleshooting Microsoft Fury3 Setup
   -------------
Below are some common errors encountered while
installing Microsoft Fury3 and explanations of the
errors:

* Fury3 requires at least a 486 processor.
You must either upgrade to an Intel 486 or higher
processor, or switch to a computer with an Intel 486 or
higher processor.

* This application requires a newer version of
Microsoft Windows.
Fury3 requires Microsoft Windows version 3.1 or later.
To purchase a Windows upgrade, see your local retailer.

* Windows is running in standard mode. Win 32S can only
run in 386 enhanced mode.(Windows 3.10 only)
If you have 8 MB of RAM, as required by Microsoft Fury3,
and are unable to run Windows in enhanced mode, you may
need to reconfigure your computer. You can determine if
Windows is running in standard or enhanced mode by
clicking About on the Help menu.

NOTE: If you are unsure how much RAM your computer has,
you can run Microsoft Diagnostics (MSD), or check with
the manufacturer of your computer. For more information
about running MSD, see your Windows User's Guide.

If your computer has the necessary 8 MB of RAM and you
are an advanced computer user, you may try removing some
TSRs from your AUTOEXEC.BAT file and editing your
CONFIG.SYS file to make more memory available to Windows.

Below are examples of clean boot AUTOEXEC.BAT and
CONFIG.SYS files that should make enough memory
available for Windows to run in enhanced mode.

IMPORTANT: Use the File Manager to copy and rename your
AUTOEXEC.BAT and CONFIG.SYS files in case you need to
restore your current configuration.

Example for a clean boot AUTOEXEC.BAT file:
Path=c:\;c:\dos;c:\windows
Prompt $p$g
Set Temp=c:\temp(make sure it points to a valid temp
directory)
Include any command lines necessary for sound cards,
CD-ROM drives, or hard disk compression utilities.

Example for a clean boot CONFIG.SYS file:
Device=c:\windows\himem.sys
Files=65
Buffers=20
Stacks=9,256
Shell=c:\dos\command.com c:\dos\ /p /e:256
Include any command lines necessary for sound cards,
CD-ROM drives, or hard disk compression utilities.


   -------------
   >  Installing Microsoft Fury3 from a Third-Party
      Shell (Windows 3.1 only)
   -------------
If you can disable the shell through the shell's
configuration/Setup utilities, please do so. Otherwise,
follow these instructions if you are having trouble
installing Microsoft Fury3 from a shell program such as
Packard Bell Navigator, Xsoft TabWorks, or Norton
Desktop.

IMPORTANT: Use the File Manager to copy and rename the
SYSTEM.INI file before following this procedure. For
your protection, do not make changes to the original
SYSTEM.INI file in case you need to restore it later.

1. In the Accessories group, double-click Notepad.
2. On the File menu, click Open.
3. In the File Name box, type:  system.ini
4. Click OK.
5. Under [Boot], locate the 'Shell=' line.
6. Insert a semicolon at the front of the 'Shell=' line.
   This remarks out the line.
7. Create a new line under 'Shell=' and type:
   Shell=Progman.exe
8. On the File menu, click Save.
9. On the File menu, click Exit.
10.Restart Windows, and install Microsoft Fury3.

After you've installed Microsoft Fury3, follow steps
1 - 5 above and then remove the semicolon from the first
'Shell=' line. Place a semicolon in front of the
'Shell=Progman.exe' line you added to remark out
the line.

   -------------
   >  Using a Clean Boot to Resolve Setup Conflicts
   (Windows 3.1 only)
   -------------
If you are unable to install Microsoft Fury3, you can
edit your AUTOEXEC.BAT, CONFIG.SYS, and WIN.INI files
and use a clean boot to make more memory available to
Windows.

IMPORTANT: Use the File Manager to copy and rename the
AUTOEXEC.BAT, CONFIG.SYS, and WIN.INI files before
following this procedure. For your protection, do not
make changes to the original files in case you need to
restore them later.

1. In the Main group, double-click the File Manager.
2. Double-click the Windows directory.
3. Open the AUTOEXEC.BAT, CONFIG.SYS, and WIN.INI files
   and edit out unnecessary command lines. Refer to the
   following examples for what to leave in the files.
4. On the File menu, click Save.
5. On the File menu, click Exit.
6. Restart Windows, and install Microsoft Fury3.

Examples:

AUTOEXEC.BAT
Path=c:\;c:\dos;c:\windows
Prompt $p$g
Set Temp=c:\temp (make sure it points to a valid temp
directory)
Include any command lines necessary for audio cards,
CD-ROM drives, or hard disk compression utilities.

CONFIG.SYS
Device=c:\windows\himem.sys
Files=65
Buffers=20
Stacks=9,256
Shell=c:\dos\command.com c:\dos\ /p /e:256
Include any command lines necessary for audio cards,
CD-ROM drives, or hard disk compression utilities.

WIN.INI
Insert a semicolon in front of the 'Load=' line and the
'Run=' line in the 'Windows' category to remark out the
lines.

NOTE: Remarking out the lines only has to be done if
there are commands on the lines.

Rename the Startup group in Program Manager if any
programs are being loaded through it.

   -------------
   >  Resolving Setup Freezes During Installation
   (Windows 3.1 only)
   -------------
If Setup stalls during installation, and you are running
MS-DOS 6.0 or later, run Scandisk followed by Defrag /f.
For information about these two commands, see the MS-DOS
User's Guide. After the commands are completed, restart
Windows and install Microsoft Fury3.

If you are not running MS-DOS 6.0 or later, you can use
the Chkdsk /f command.
You can then use a defragmentation utility such as PC
Tools or Norton Desktop.

   -------------
   >  Starting Microsoft Fury3 if You Are Using the PC
   Tools Desktop (Windows 3.1 only)
   -------------
If you are using PC Tools Desktop as your Windows shell,
you will need to restart Windows after installing
Microsoft Fury3 by exiting Windows and typing Win at
the prompt.

------------------------------------------
  B.  HARDWARE AND SYSTEM COMPATIBILITY
------------------------------------------

   -------------
   >  Optimizing Performance on Minimum-Configuration
   Machines
   -------------
If you have a computer with a 486/66 processor and 8 MB
of RAM, the following steps may improve performance:
* Be sure that you are not logged on to a network.
* Close any open applications.
* Run Fury3 in Full Screen, Panoramic format.
* Modify options in the Graphics Options dialog box:
  1. On the Fury3 Options menu, click Graphics Options.
  2. Select None in the Shadow Detail box.
  3. Select Normal Quality in the Image Quality box.
  4. Select Low Detail in the Texture Detail box.
  5. Select Off in the Debris box.
  6. Make sure the Show Sky Texture check box is cleared.
When you reduce the detail levels, you affect the
appearance of Fury3 -- do the above only if speed is the
primary consideration.

* (Windows 3.1 only) Increase the size of your swap file
(see the README topic Increasing the Size of Your Swap
File).

* (Windows 3.1 only) Use the clean boot configuration
(see the README topic Using a Clean Boot to Resolve
Setup Conflicts).
Tailor the clean boot so that it:
- Loads the minimal number of memory resident drivers
  and programs needed to run Windows.
- Does not enable expanded memory (EMM386 should be
  configured for NOEMS).
- Does not load SmartDrive (this becomes a tradeoff
  between more memory and slower hard drive
  performance -- on some systems this may lead to slower
  game play).

* (Windows 3.1 only) Install more memory in your machine
to speed up Microsoft Fury3. 10 MB of RAM is recommended.

   -------------
   >  Other Performance Issues
   -------------
* If you are using a CH Flightstick Pro, a Gravis
Phoenix/Firebird, or compatible joystick: When two
joystick buttons are pressed simultaneously, the
joystick interprets the multiple presses as a Hat
Switch action. To prevent this, press only one joystick
button at a time.

* Users of slower machines may experience a delay in
game play when entering and exiting tunnels. This may
also happen when Fury3 is loading game data. Please do
not restart your computer if this occurs.

Modify options in the Graphics Options dialog box:
  1. On the Fury3 Options menu, click Graphics Options.
  2. Select None in the Shadow Detail box.
  3. Select Normal Quality in the Image Quality box.
  4. Select Low Detail n the Texture Detail box.
  5. Select Off in the Debris box.
  6. Make sure the Show Sky Texture check box is cleared.

* (Windows 95 only) Fury3 only recognizes Joystick 1 in
the Joystick Properties box. Be sure that the joystick
you are using with Fury3 is connected to your computer's
first game port.

* (Windows 3.1 only) You may experience drift or
instability when using a joystick. This may be caused by
background processes, such as running Fury3 with other
applications open, networking, or reformatting a large
document in a word-processing program. If you are
running your joystick through the game port on your
sound card, you can improve performance by using a
dedicated game card.

   -------------
   > Setting Up Programmable Joysticks (ThrustMaster,
   Gravis)
   -------------
Fury3 provides separate files for use with 4
ThrustMaster joystick configurations:
(a) ThrustMaster F-16 FLCS alone: FFURY3.B50
(b) ThrustMaster F-16 FLCS and TQS: QFURY3.B50
(c) ThrustMaster F-16 FLCS and Mark II WCS: MFURY3.B50
(d) ThrustMaster (P)FCS and Mark II WCS: FURY3.ADV

Fury3 also provides separate files for use with the
Gravis Phoenix: FURY3.PHX and the Gravis Firebird:
FURY3.FBD

Using programmable ThrustMaster joysticks under
Windows 95:
To set up your ThrustMaster joystick:
  1. From Windows 95, start an MS-DOS window.
  2. Run the ThrustMaster joystick configuring utility.
     Please refer to your ThrustMaster Owner's Manual
     for instructions. Note: If you do not download the
     appropriate file (see files above) to your joystick,
     it will function as a 2-axis, 2-button joystick.
  3. Once your joystick is programmed, exit MS-DOS to
     return to Windows, open Control Panel, and double-
     click the Joystick icon.
  4. In Joystick Properties, select "2-button flight
     yoke w/throttle" from the Joystick selection box
     if you are using joystick  type (b), (c), or (d)
     above. If you are using (a) (ThrustMaster F-16
     FLCS alone), select "2-axis, 2-button joystick."

Using the Gravis Phoenix or Firebird under Windows 95:
To set up your Phoenix or Firebird joystick:
  1. From Windows 95, start an MS-DOS window.
  2. Run the Phoenix/Firebird joystick configuring
     utility. Please refer to your Phoenix/Firebird
     User's Guide for instructions. Note: If you do not
     download the appropriate file (see files above) to
     your joystick, it will function as a 2-axis,
     2-button joystick.
  3. Once your joystick is programmed, exit MS-DOS to
     return to Windows, open Control Panel, and double-
     click the Joystick icon.
  4. In Joystick Properties, select "2-button flight
     yoke w/throttle" from the Joystick selection box.

Using programmable ThrustMaster joysticks under Windows
3.1:
To set up your ThrustMaster joystick:
  1. From Windows 3.1, start an MS-DOS window.
  2. Start the ThrustMaster joystick configuring utility.
     Please refer to your ThrustMaster Owner's
     Manual for instructions. Note: If you do not
     download the appropriate file (see files above) to
     your F-16 FLCS, it will function as a 2-axis,
     2-button joystick.
  3. Once your joystick is programmed, exit MS-DOS and
     return to Windows.
  4. Load Fury3, and then click Flight Control Options
     on the Options menu.
  5. Click Joystick or Joystick with Throttle,
     depending on the joystick you have.
  6. Click Calibrate and follow the directions on the
     screen.

Using the Gravis Phoenix or Firebird joystick under
Windows 3.1:
To set up your Phoenix or Firebird joystick:
  1. From Windows 3.1, start an MS-DOS window.
  2. Start the Gravis Phoenix or Firebird joystick
     configuring utility. Please refer to your
     Phoenix or Firebird User's Guide for instructions.
     Note: If you do not download the appropriate file
     (see files above) to your joystick, it will
     function as a 2-axis, 2-button joystick.
  3. Once your joystick is programmed, exit MS-DOS and
     return to Windows.
  4. Load Fury3, and then click Flight Control Options
     on the Options menu.
  5. Click Joystick with Throttle.
  6. Click Calibrate and follow the directions on the
     screen.

   -------------
   >  Increasing the Size of Your Swap File
   (Windows 3.1 only)
   -------------
In Windows 3.1, Microsoft Fury3 requires at least 8 MB
of RAM, plus a 10 MB swap file if you have less than
12 MB of RAM. Be sure that the swap file is set for a
minimum of 10 MB. Increasing the swap-file size may
improve the performance of Microsoft Fury3.

Follow this procedure to increase the swap file if your
computer has enough available disk space:

1. In the Main group, double-click the Control Panel.
2. Double-click the 386 Enhanced icon.
3. Click Virtual Memory.
4. Click Change.
5. Increase the size of the swap file.

Follow this procedure to increase the swap file if your
computer is low on disk space and you are running
MS-DOS 6.0 or later:

1. In the Main group, double-click the Control Panel.
2. Double-click the 386 Enhanced icon.
3. Click Virtual Memory.
4. Click Change.
5. Under New Swapfile Settings, enter None in the Type
   box.
6. Click OK in both dialog boxes.
7. Close Windows.
8. From the MS-DOS prompt, run Scandisk, and then
   Defrag. For information about these two commands, see
   the MS-DOS User's Guide.
9. Once these commands are completed, restart Windows.
   Increase the virtual memory using the previous
   procedure.

NOTE:  If you are unable to create a 10 MB swap file
using this procedure, you can remove files from the hard
disk, and then try the procedure again.

If you are not using MS-DOS 6.0 or later, you can use
the Chkdsk /f command to check your swap file size. You
can then use a defragmentation utility such as PCTOOLS
or Norton.

   -------------
   > Growstub Error (Windows 3.1 only)
   -------------
Use the following procedure if you get a growstub error
message.

IMPORTANT: Use the File Manager to copy and rename the
WIN.INI file before following this procedure. For your
protection, do not make changes to the original WIN.INI
file in case you need to restore it later.

1. Click the Accessories group, and then double-click
   Notepad.
2. On the File menu, click Open.
3. In the File Name box, type:  win.ini.
4. Locate the 'Load=' line under the 'Window' category.
5. Delete 'Pointer.exe' from the 'Load=' line.
6. On the File menu, click Save.
7. On the File menu, click Exit.
8. Restart Windows, and then restart Microsoft Fury3.

   -------------
   >  EMM 386 Exception Error (Windows 3.1 only)
   -------------
Follow this procedure if you get an EMM 386 exception
error.

IMPORTANT: Use the File Manager to copy and rename the
WIN.INI file before following this procedure. For your
protection, do not make changes to the original WIN.INI
file in case you need to restore it later.

1. Click the Accessories group, and then double-click
   Notepad.
2. On the File menu, click Open.
3. In the File Name box, type:  win.ini.
4. Click OK.
5. Locate the 'Load=' line under the 'Window' category.
6. Remove the 'Pointer.exe' command from the 'Load='
   line.NOTE: For some Packard Bell computers, you may
   also need to remove the 'Mapiappi.exe' command from
   the 'Run=' line.
7. On the File menu, click Save.
8. On the File menu, click Exit.
9. Restart Windows, and then restart Microsoft Fury3.

   -------------
   >  Win32s Error (Windows 3.1 only)
   -------------
To resolve this error, you need to create a larger swap
file. See the README topic Increasing the Size of Your
Swap File for instructions.


------------------------------------------
  C.  VIDEO DRIVER NOTES
------------------------------------------

   -------------
   >  Changing the Video Display to 256 Colors
   -------------
Your computer must display 256 colors to run Microsoft
Fury3.

To display 256 colors in Windows 95:
1. Click the Start button, and then point to Settings.
2. Click Control Panel.
3. Double-click the Display icon.
4. Click the Settings tab.
5. Under Color Palette, click 256 Color.
6. Click OK.
7. Reinstall Microsoft Fury3.
NOTE: If you don't have the necessary 256-color driver,
or if you aren't sure that your video card supports 256
colors, contact your video card manufacturer.

(Windows 3.1 only) IMPORTANT: Use the File Manager to
copy and rename the SYSTEM.INI file before using the
following procedure. For your protection, do not make
changes to the original SYSTEM.INI file in case you
need to restore it later.

To display 256 colors in Windows 3.1:
1. In the Main group, double-click Windows Setup.
2. On the Options menu, click Change System Settings.
3. In the Display list, click a 256-color display driver
suited for the video card in your computer. (If you are
not sure which video driver to select, contact your
video card manufacturer.) NOTE: You must use a minimum
display resolution of 640 x 480.
4. Click OK.
5. Restart Windows, and install Microsoft Fury3.

If you have a video card that uses the S3 chip set and
are having trouble with Microsoft Fury3, contact
Microsoft to obtain S3 chip set Super VGA drivers. See
the README topic Unhandled Exception Error for the S3
Video Driver (Windows 3.1 only) for information.


   -------------
   > Unhandled Exception Error for the S3 Video Driver
   (Windows 3.1 only)
   -------------
Some S3 video drivers (in particular Dell S3 drivers)
can cause unpredictable crashes when running Microsoft
Fury3 under Windows 3.1. Contact your video card
manufacturer to make sure you have a compatible video
driver.

IMPORTANT: Use the File Manager to copy and rename the
SYSTEM.INI file before following this procedure. For
your protection, do not make changes to the original
SYSTEM.INI file in case you need to restore it later.

1. Double-click the Main group, and then click Windows
   Setup.
2. On the Options menu, click Change System Settings.
3. In the Display list, click Super VGA or a newer
   256-color display driver suited for the video card
   in the computer.
4. Click OK.
5. Restart Windows, and then restart Microsoft Fury3.

To obtain  S3 chip set Super VGA drivers (Windows 3.1
users only): Download the SVGA drivers from the
Microsoft Download Service (MSDL). These drivers work
correctly on many video cards. The number for the MSDL
is [phone]. This service is available 24 hours a
day, 7 days a week. The highest download speed available
is 14,400 bits per second (bps). Each file is a
compressed, self-extracting file. To download the file,
use the filename SVGA.EXE. After you download the file,
run it in an empty directory to extract the files it
contains. You can also obtain this file on CompuServe in
the Microsoft Software Library (type "go msl" [without
the quotation marks] and download the file SVGA.EXE.)

   -------------
   >  Using an ATI mach32 or mach64 Display Driver
   (Windows 3.1 only)
   -------------
Prior to installing Fury3, please ensure that you are
using an ATI display driver released after May 1995 for
mach32 products and after June 1995 for mach64 products.
Earlier versions of the mach32 and mach64 Windows
drivers may cause difficulties in full screen modes.

If you find that your present ATI mach32 driver was
released before May 1995 or your mach64 driver was
released before July 1995, the updated drivers are
provided on this CD in the ATI directory. The drivers
contained on the CD are current as of July 1995 and are
identical to the drivers available on the ATI BBS at
the time.

To determine the date and version of the ATI driver on
your system, follow the procedure below. For ATI
products that use the ATI Desktop (all mach64 and
Graphics Wonder):
  1. Double-click the ATI Desktop icon.
  2. Select HELP from the Title Bar.
  3. Select ABOUT... from the drop down list.
  4. Ensure that the date is later than June 1, 1995.

If your ATI product uses the FLEXDESK Control Panel (all
mach32 except the Graphics Wonder):
  1. Double-click the mach FLEXDESK Control Panel icon.
  2. Select HELP from the Title Bar.
  3. Select ABOUT... from the drop down list.
  4. Ensure that the FLEXDESK Driver build is 2.6 or
     higher.

ATI is continually improving their drivers. The latest
versions of all ATI drivers are available from the
ATI Download BBS at [phone], via ATI's forum on
CompuServe at GO ATITECH, or from the ATI FTP site at
ftp://ftp.atitech.ca
If you require further assistance, please contact ATI at:
Customer Support Fax: [phone] (24 Hours)
Download BBS: [phone] (24 Hours)
ftp Download: ftp.atitech.ca (24 Hours)
CompuServe: GO ATITECH (24 Hours);
General Inquiries: 76004,3656
Technical Support Inquiries: 74740,667

------------------------------------------
  D.  SOUND CARD NOTES
------------------------------------------

   -------------
   >  Troubleshooting Sound Cards
   -------------
Use the following list of troubleshooting suggestions
if Microsoft Fury3 does not play sound properly:

* Be sure you are using the latest sound driver
available. Contact your sound card manufacturer to
obtain the latest sound driver.

* Be sure that your system's volume control is not
muted and is turned up.

* Verify that Windows 95 can play .WAV files:
  1. Click the Start button, and then point to Settings.
  2. Click Control Panel.
  3. Double-click the Sounds icon.
  4. Try to play a .WAV file.

* Verify that Windows 3.1 can play .WAV files:
  1. Click the Main group, and then double-click
     Control Panel.
  2. Double-click the Sound icon.
  3. Try to play a .WAV file.

* If Windows cannot play a .WAV file:
Check to see that you have an audio card. If you don't
have an audio card, contact your equipment
dealer to obtain one.

* If you are able to play a .WAV file:
  1. Start Microsoft Fury3.
  2. On the Options menu, click Sound Options.
  3. Verify that the Play Sound Effects and Play Music
     check boxes are checked, and that Volume for both
     is 100%. If the volume is turned up, then click
     Advanced.
  4. Verify that Fury3 recognizes an audio driver by
     looking at the Sound Card Detected line.
  5. Click Test to see if Fury3 will play a sound file.

*If you are having trouble hearing sound in Fury3, it
may be related to the type of sound card you have. Use
the list of sound cards and settings below to adjust
settings for your sound card.
  1. On the Fury3 Options menu, click Sound Options. In
     the Sound Options dialog, click Advanced.
  2. In the Number of Buffers box, select the number
     that correlates to the number of buffers for
     your sound card in the list below. Then select the
     appropriate number for Buffer Size.
  3. Click Test to listen to the results of your
     changes. Click Default to return the numbers to
     their original values.

Sound Cards and Settings:

-------------
Windows 95 Sound Settings:
-------------
Sound Card: Aztech Sound Galaxy Pro 16, FCC: I38-MMSN810
Driver:  Win 95 SB Pro
# of Buffers=3
Buffer Size=2304

Sound Card: Creative Labs Sound Blaster, CT 1350B
Driver: Win 95 SB
# of Buffers=3
Buffer Size=2304

Sound Card: Turtle Beach Monte Carlo
Driver: Win 95 SB Pro
# of Buffers=3
Buffer Size=4096

Sound Card: Creative Labs Sound Blaster 16 SCSI, CT 1770
Sound Card: Creative Labs Sound Blaster 16, CT  2230
Driver: Win 95 SB 16 / AWE 32
# of Buffers=3
Buffer Size=4096

Sound Card: Creative Labs Sound Blaster 16 SCSI-2
Driver: Win 95 SB 16 / AWE 32
# of Buffers=3
Buffer Size=3072

Sound Card: Creative Labs Sound Blaster 16 Value Card,
CT 2770
Driver: Win 95 SB 16 / AWE32
# of Buffers=5
Buffer Size=2560

Sound Card: Creative Labs Sound Blaster 16-ASP Card
(Advanced Signal Processor), CT 1790
Driver: Win 95 SB 16 / AWE32
# of Buffers=4
Buffer Size=2048

Sound Card: Creative Labs Sound Blaster AWE32 Card,
CT 2760
Driver: Win 95 SB 16 / AWE32
# of Buffers=3
Buffer Size=3584

Sound Card: Sound Galaxy NX Pro 16
Driver: Win 95 MS Windows Sound System Compatible
# of Buffers=3
Buffer Size=3072

Sound Card: Turtle Beach Monte Carlo
Driver: Win 95 MS Windows Sound System Compatible
# of Buffers=4
Buffer Size=1536

-------------
Windows 3.1 Sound Settings
-------------
Sound Card: Aztech Sound Galaxy Nova 16,
FCC: I38-MMSN815
# of Buffers=4
Buffer Size=3072

Sound Card: Creative Labs Sound Blaster Pro, CT 1330A
Driver: Creative Labs Sound Blaster 1.5
# of Buffers=3
Buffer Size=3072

Sound Card: Creative Labs Sound Blaster w/2.0 DSP,
CT 1320C
Driver: Creative Labs Sound Blaster 1.5
# of Buffers=4
Buffer Size=1024

Sound Card: Creative Labs Sound Blaster v2.00, CT 1320A
Driver: Creative Labs Sound Blaster 1.0
# of Buffers=5
Buffer Size=2048

Sound Card: Creative Labs Sound Blaster 16, CT 1740
Driver: Creative SB 16 Wave and Midi v.3.01
# of Buffers=5
Buffer Size=1536

---------------------------------------------------------------------
Thank you for choosing Microsoft Fury3. Watusi!
---------------------------------------------------------------------