                              A Help File Covering
   Tips, Troubleshooting, Diagnosing, Utilizing, Optimizing, and Enjoying SGA
 (SGA=Sound, Graphics, Aircraft upgrade for FS4, published by Mallard Software)
                                        
              Original Author: Mike Barrs, Assoc.SysOp 76702,1706.
     Extensively Updated by: Robert M. MacKay 71641,2321 on March 9th, 1992.
                 CompuServe Flight Simulation Forum (GO FSFORUM)


                                TABLE OF CONTENTS
                                -----------------
                                        
I.   INTRODUCTION
II.  GENERAL INFORMATION
     A.   HOW MUCH MEMORY IS ENOUGH
     B.   MEMORY MANAGEMENT TIPS USING A 386/DOS 5
     C.   NOT ENOUGH UMB SPACE TO LOAD EVERYTHING?
     D.   SGA/ASD COMBINATIONS
     E.   THE ULTIMATE MEMORY SOURCE
     F.   INSTALLATION PROGRAM ABORTS
     G.   FLIGHT SIMULATOR 4.00 and 4.0A INCOMPATIBILITY
III. SOUND RELATED INFORMATION
     A.   SOUNDS DROPPING OUT
     B.   SOUND LOSS, FS IN SLOW MOTION
     C.   LOW ALTITUDE WARNING HORN
     D.   TIRE CHIRP/SCREECH SOUND
     E.   ENGINE SOUND CUTS IN AND OUT
IV.  SPEECH RELATED INFORMATION
     A.   SBTALKER (for Soundblaster owners)
     B.   CANNOT GET SBTALKER TO WORK
V.   AIRCRAFT RELATED INFORMATION
     A.   CONCORDE
     B.   P-51D MUSTANG
VI.  VIDEO RELATED INFORMATION
     A.   640x400 MODE
     B.   TSENG 4000 GRAPHIC CARDS
     C.   ATI ULTRA VIDEO DRIVER (BETA)
     D.   VIDEO-7 VRAM II
VII. MISCELLANEOUS PROBLEMS
     A.   JOYSTICK INTERFERENCE WITH SOUNDBLASTER (AND PRO)
     B.   BOBBING
     C.   MAP DISPLAY
     D.   640x480 INSTRUMENT PANEL
     E.   OVERLAPPED 3D-WINDOW OR GAUGES
     F.   SCREEN FLASHES
     G.   SCREEN GOES BLANK
     H.   SCREEN ROLLS IN 800x600 MODE
     I.   FRAME RATE SLOW DOWN WITH 800x600 MODE
     J.   LOCKUPS WHEN CHANGING MODES OR USING POSITION SET
     K.   DMA CAUSED LOCKUPS WITH GEAR ACTIVATION
     L.   CHANGING YOUR DMA TO 0
     M.   CHANGING YOUR IRQ TO 10
VIII.     FOR FURTHER ASSISTANCE
IX.  CREDITS



I.INTRODUCTION

     The SGA upgrade for Flight Simulator 4.0 adds several great new features,
     but getting the most out it requires freeing up as much memory as you can.
     FS4 doesn't support expanded or extended memory. So the new sound and
     graphics drivers must compete with ASD and any other FS4 add-ons for memory
     under the DOS 640K limit.
     
     If you don't use the Aircraft and Scenery Designer (ASD) you won't have too
     many problems. If you do use ASD with a large memory allocation for loading
     large scenery files, you'll have to work harder to squeeze everything into
     the available memory. The NFL (subLOGIC's New Facilities Locator) and JFL
     (TekMate's Jiffy Facility Locator) utilities also take up memory space. You
     might need to remove them to see the new SGA goodies and then add them back
     in once you decide which SGA features to hang on to (if you can afford the
     memory).  Mallard's FLIGHT PLANNER (previously known as RMMFP and RMMFP/w)
     does not affect FS4, ASD, or SGA since it is a stand alone product (you
     run/use it before starting up FS4).
     
     *****  N O T I C E  ****
     There are several sets of patches that have been written by a user(s) *not*
     affiliated with FSFORUM or any FS related company.  These patches are not
     supported nor endorsed by BAO or Mallard Software especially.  They are
     provided here simply because this text file is an attempt to get you what
     ever information is available related to SGA.  You are at your own risk in
     using the patches.


II.    GENERAL INFORMATION

  A.HOW MUCH MEMORY IS ENOUGH

     If you have ASD installed, you should try to set up your system for at
     least 620,000 bytes free conventional memory. If you can push it to 635,000
     or more, that's even better.
     
     You will solve many potential problems by upgrading to DOS 5.0 if you
     haven't already (in fact, this should almost be a system requirement!). You
     will also need to load all the TSR's and drivers that you use into high
     memory (provided they fit of course), using the DEVICEHIGH/LOADHIGH
     functions of either DOS 5.0 or QEMM386 (or equivalent memory manager). Not
     everyone will be able to get 635,000 bytes free, but if your machine allows
     loading TSR's and drivers high, it shouldn't be too difficult. If you can't
     use DOS 5.0's DOS=HIGH command to load DOS into high memory, you'll have to
     settle for fewer SGA features. Try making a minimum configuration floppy
     disk to boot from, with as few drivers as possible in the CONFIG.SYS and
     AUTOEXEC.BAT.
     
     For 386 machines, Mallard recommends creating a boot disk with the
     following CONFIG.SYS and AUTOEXEC.BAT files (this assumes you are using DOS
     5.0):
     
     CONFIG.SYS -
       DEVICE=C:\DOS\HIMEM.SYS
       DEVICE=C:\DOS\EMM386.EXE 256
       DOS=HIGH,UMB
       BUFFERS=30
       FILES=30
     
     AUTOEXEC.BAT -
       LH C:\DOS\MOUSE /Y
       C:
       <<Change to your Flight Sim directory and load Flight Simulator>>
     
     If you need more help in freeing up conventional memory, leave a message
     requesting such in CompuServe's FSFORUM section 13 (Hardware) or in the
     IBMSYS forum.

  B.MEMORY MANAGEMENT TIPS USING A 386/DOS 5

     Because memory availability is continuing to be an issue for Flight
     Simulator users, here's a sample 80386/DOS5 boot-up routine that will yield
     maximum conventuional memory.  All this information was learned from the MS-
     DOS User's Guide and Reference.
     
     CONFIG.SYS:
     -------------
          DEVICE=C:\DOS\HIMEM.SYS
          DEVICE=C:\DOS\EMM386.EXE NOEMS
          DOS=HIGH,UMB
          STACKS=0,0
     
     AUTOEXEC.BAT:
     ----------------
     Omit.  FS4 will run just fine without any AUTOEXEC.BAT commands, depending
     on your own particular hardware setup.
     
     DISCUSSION:
     -----------
     
       DEVICE=C:\DOS\HIMEM.SYS        Manages use of exTended memory, we'll
                                      need later.
                                      
       DEVICE=C:\DOS\EMM386.EXE NOEMS Does two things, 1) simulates exPanded
                                      memory (which we don't need for FS, hence
                                      the NOEMS parameter), 2) provides access
                                      to the upper memory area on computer that
                                      has 80386 or higher processor.
                                      
       DOS=HIGH,UMB                   Does two things, 1) loads part of MS-DOS
                                      into high memory area (HMA), 2) maintains
                                      a link to upper memory area.
                                      
       STACKS=0,0                     Limit number of interrupt stacks.
     
     I've found that the above CONFIG.SYS, used without any autoexec.bat, will
     yield the maximum amount of conventional memory for Flight Simulator use.
     Here are some optional parameters. Because they're not loaded into
     conventional memory, there is no penalty for using them.  Add these lines
     to your CONFIG.SYS as you desire:
     
       DEVICEHIGH=C:\MOUSE.SYS         Example of loading a mouse driver into
                                        HMA.
       DEVICEHIGH=C:\DOS\SMARTDRV.SYS  Example of loading hard disk cache.
     
     
     CHECKING ON YOUR MEMORY:
     ------------------------
     
     Here is a handy-dandy way to examine your memory usage. Type this from the
     command line prompt:
     
       MEM /C | MORE
     
     This assumes the MORE.COM program is available (usually thru the PATH
     command). You might consider making a short batch file including this line
     for your memory checking needs.

  C.NOT ENOUGH UMB SPACE TO LOAD EVERYTHING?

     If you installed DOS 5.0 using standard default settings, then you are
     probably only getting about half the UMB space that you may be able to
     access.  Most systems do not use the E000-EFFF address areas of Upper
     Memory.  In addition, EMM386.exe defaults to only using a default block
     which does not include this address area.  Hence, try having your
     EMM386.exe driver include this area.  On some systems, UMB space went from
     79K to 143K!  Now that should be plenty to load Mouse, Cache, Network, CD-
     ROM and other drivers you may have...and STILL leave room for more (such as
     the tip described in part E of this section).  To access this area, have
     your EMM386.exe line in your CONFIG.SYS file look like this:
     
     For no expanded memory...
     
       DEVICEHIGH=EMM386.EXE noems i=E000-EFFF
     
     For minimal expanded memory (for using SBTALKER)...
     
       DEVICEHIGH=EMM386.EXE 256 ram FRAME=E000
     
  D.SGA/ASD COMBINATIONS

     With 635,000 bytes free under DOS you can use the following setup:

            ASD: 60,000 bytes static, 30,000 dynamic, 35 dynamic objects
            Soundblaster sampled sounds
            640x480, 640x480 747*, or 800x600* cockpits

     (*no landing gear sound on Soundblaster)

     Note that this does not include SBTALK digitized speech or the NFL or JFL
     utilities, and the landing gear sound is missing on the two enhanced
     cockpits. It is, however, a full ASD configuration that will allow loading
     large scenery files. The 640x480 cockpit works fine - it takes less memory
     so you get all the sounds including landing gear.
     
     If you have 590,000 bytes free under DOS, you can use these features:
     
          ASD: 60,000 bytes static, 30,000 dynamic, 35 dynamic objects
          Soundblaster sampled sounds
          640x480 cockpit
     
     To use the 640x480 747 or 800x600 cockpits, you would have to reduce ASD
     scenery allocations or else give up Soundblaster sound effects.

  E.THE ULTIMATE MEMORY SOURCE

     This is one that not many people would have ever thought of trying, but the
     folks at BAO/Mallard annouced this great trick on CompuServe.
     
     If you have several kb of UMB space left over, you can actually run FS4
     with the LOADHIGH command!  When run this way, FS4 will try to load as much
     of its "stuff" high as possible.  What ever it can load high, will free up
     that much more of conventional memory (which is desperately needed for a
     max'ed out A&SD configuration, plus subLOGIC's NFL, or TekMate products
     like JFL & SEE04).  On some systems tested, free memory went up enough to
     load all these things and not lose a single sound!  Please note that on
     some systems this may not work (or if you do not have enough UMB space
     available - a good 20k or more should work though).
     
     To load FS4 high, start FS4 with the following command:
     
       LOADHIGH FS4
     
  F.INSTALLATION PROGRAM ABORTS

     The install program could not find your FS4.EXE file in the specified
     directory.  Make sure that the source disk is your ORIGINAL SGA disk, and
     that the target drive/directory is your FS drive/directory, *and* that you
     have at least 1MB of free space on your hard disk.

  G.FLIGHT SIMULATOR 4.00 and 4.0A INCOMPATIBILITY

     The first 5000 copies of the SGA package were shipped with an
     incompatibility with Flight Simulator versions 4.00 and 4.0A.  The machine
     may lock up when the Sound Control Panel is selected from the FS Mode Menu.
     
     1.CONTACT MICROSOFT
     
       They will be able to exchange your current Flight Simulator version for
       FS 4,0B.  Read FSFORUM file FS4B.TXT from Library 2, General Aviation
       for instructions.
       
     2.DEBUG FIX
     
       A patch applied will fix the problem.
       
       From the Flight Simulator directory, type:
       
          DEBUG SOUND.DRV
          e cs:11d 74 55
          e cs:2df4 e8 03
          e cs:2df8 70 17
          w
          q
       
     3.CONTACT MALLARD
     
       They have an upgrade of SGA available that corrects this problem.


III.   SOUND RELATED INFORMATION

  A.SOUNDS DROPPING OUT

     A common problem with SGA is disappearing sound effects. FS4 places SGA
     sound effects on a low priority... it will drop sound effects one by one as
     memory gets tight. The first to go is the landing gear sound, then the
     engine.
     
     If you plan on using the 800x600 cockpit as your standard setup for FS4,
     you'll need the most amount of free memory. The 640x480 747 cockpit is a
     close second. You might see sound dropouts or have trouble opening the map
     window with these cockpits until you can free up enough conventional
     memory. Another thing you may notice on the 800x600 cockpit (and maybe also
     on the 747 cockpit) is that opening the map window may cause the engine
     sound to disappear and not come back until you restart FS4.
     
     These problems will most likely go away if you increase DOS memory or
     switch to the 640x480 or standard 640x350 cockpits which take much less
     memory.

  B.SOUND LOSS, FS IN SLOW MOTION

     This is most likely caused by an IRQ conflict in your computer and has been
     a problem only with Soundblaster cards.  Soundblaster usually defaults to
     IRQ7.  Most problems seem to be getting cured by changing the Soundblaster
     IRQ to another number.  It is recommended that you try IRQ2 or IRQ5 first.
     
     A workaround is to use the AdLib mode.
     
     For many people, simply activating the Sound Control Menu and then hitting
     spacebar to go back to flight.  This usually brings the sound back
     instantly.
     
  C.LOW ALTITUDE WARNING HORN

     The low altitude warning horn on the 800x600 display only works
     intermittently.

  D.TIRE CHIRP/SCREECH SOUND

     The sampled tire chirp sound for Soundblaster owners loads from disk the
     first time it's used. This can cause an annoying delay the first time you
     land. As a workaround, Rick Lee suggests saving a startup mode where your
     airplane is a foot off the ground (use the 5,A menu to adjust the
     altitude). When FS4 boots up, your plane will settle to the ground and
     trigger the chirp. From then on, the tire chirp is in memory and you
     shouldn't hear a delay when it sounds on touchdown. The idea was that from
     then on the chirp sound would be in memory and you wouldn't hear a delay
     when it sounded on touchdown. However, it was then noticed that after
     flying long distances the chirp sound was replaced or unloaded from memory
     somewhere along the line.  He then used the SMARTDRV disk cache with DOS5
     to store this sound in memory.  So far, having SMARTDRV loaded into high
     memory has solved this problem with no ill effect.

  E.ENGINE SOUND CUTS IN AND OUT

     The engine sound cutting in and out while in Soundblaster mode is a problem
     caused by an IRQ conflict in your computer.  Try a different IRQ setting by
     following the instructions that come with your Soundblaster card.
     Alternatively, you can run the sound board in AdLib mode and the digital
     board in Soundblaster mode.


IV.    SPEECH RELATED INFORMATION

  A.SBTALKER (for Soundblaster owners)

     The digitized speech feature in SGA uses the SBTALKER program included with
     the Soundblaster card (called by the SBTALK.BAT batch file).  It will
     automatically load most of itself into expanded memory if it finds any on
     your system, leaving a 6K program kernel resident in conventional memory.
     
     To run FS, SBTALKER, ASD, and SGA; it is recommended that you use DOS 5.0
     and have some EXPANDED memory setup.  SBTALKER will load into expanded
     memory, and this should leave enough conventional memory for FS, ASD, and
     SGA.  You may need to tweak the STATIC/DYNAMIC scenery memory allocations
     of ASD to get it to a good tradeoff point.
     
     The SGA manual , incorrectly, recommends that you prevent auto-loading of
     SBTALK into expanded memory by disabling your expanded memory driver, but
     the manual is assuming you don't have ASD installed! Without expanded
     memory, SBTALK hogs 184K in conventional memory. FS4 won't even boot up
     with ASD installed, when SBTALK is using that much memory.
     
     You might be able to load all of SBTALK into high memory, moving that 6K
     kernel out of conventional memory... I tried using QEMM386's Optimize
     program to do that but it failed to load it high.
     
     SBTALK will run fine in expanded memory but you need to follow a few steps
     to avoid problems. If you load SBTALK from inside your Soundblaster sub
     directory, FS4 will lock up solid, either right away or when you first get
     an ATIS or COM message. You need to use the modified BLASTER.DRV driver
     installed into your FS4 sub directory by SGA, not the BLASTER.DRV included
     with the Soundblaster. Easiest way to do this is to copy SBTALK.BAT,
     SBTALKER.EXE, and REMOVE.EXE from your Soundblaster sub directory into your
     FS4 sub directory. Then log onto your FS4 sub directory and type "sbtalk".
     This way it will grab the new driver supplied in the upgrade. After running
     FS4 remember to type "remove" in the FS4 directory to remove the driver.
     
     You'll want to write a batch file like this to run FS4 if you decide to
     keep SBTALK in your configuration... change the path names as necessary for
     your system:
     
       @echo off
       cd\fs4
       call sbtalk
       fs4
       remove
       
     SBTALK digitized speech will pause the simulation while talking (at least
     it does on my machine) and the synthetic "robot" speech is hard to
     understand. Unless this voice synthesizer feature really knocks you out, I
     would recommend not using it at all. The sampled engine and other sounds in
     the SGA package are much better.

  B.CANNOT GET SBTALKER TO WORK

     First check to make sure that the SGA package has been properly installed,
     *and* that the CT-VOICE.DRV and the BLASTER.DRV drivers are the ones that
     come with SGA and *not* the ones packaged with the Soundblaster card.
     
     The SBTALKER program is a TSR (terminate-stay-resident) program that
     requires approximately 200K of memory.  If expanded memory is available,
     SBTALKER will automatically load itself into expanded memory, leaving only
     a 7K shell in conventional memory.  FS, SBTALKER, and the SGA package *can*
     all fit together in the remaining conventional memory.
     
     The stated memory requirements to run all with all the functions of FS,
     ASD, and SGA are a minimum of 590K free conventional memory.  This is a
     minimum, and thus if that is all you have free, you will not be able to
     have large amounts of ASD memory available or SGA memory.  You will have to
     trade off between the two as to which is more important...all sounds and
     little ASD scenery, or some sounds and lots of ASD scenery.  With DOS 5.0
     and other memory utilities, users have been able to get all sounds plus a
     very high memory setting for ASD of 61000-static, 30000-dynamic, and 30
     items.
     
     SBTALKER will perform slower in expanded memory, but this is the only
     practical way to run all of the programs at once.


V.AIRCRAFT RELATED INFORMATION

  A.CONCORDE

     Many FS pilots have become frustrated trying to fly the Concorde.  This is
     primarily due to reports of instability.  There is *not* a problem with
     instability, it is with flying characteristics of the real Concorde.
     
     Supersonic aircraft with the characteristics of the Concorde, are designed
     to go fast *only* when they reach altitudes of 35000 feet AGL and higher.
     This is where the air becomes noticeable thinner and produces less
     drag/resistance.  Standard operating procedures for a Concorde in FS are to
     remain below 450kts while below 35000 feet AGL.  This applies to climbing
     as well as descending.  In other words, be sure to slow back down under 450
     kts before descending below 35000 feet.  If you go faster than 450 kts
     below 35000 feet, you will begin to lose controllability of the aircraft.
     
     Other notes related to the Concorde pertain to its slippery-ness.  It is
     actually hard work to slow the Concorde down.  The aircraft is so slippery
     (aerodynamics) that it produces very little resistance (especially compared
     to a Cessna, 747, etc.).  To slow down, reduce the throttle to idle and
     slowly get into a nose up attitude to bleed off speed (you may need to use
     some spoilers to help out).  It will take some time to slow down from
     Supersonic flight to Subsonic below 450kts.  Be patient.  To be completely
     realistic, do not use flaps, as the real Concorde does not have any.

  B.P-51D MUSTANG

     The most difficult thing about the Mustang is taxing.  This tail dragger
     sits with its nose pointed so high up, that you can not see the
     taxiway/runway.  An easy way to taxi this bird is to get in spot plane mode
     behind the Mustang and taxi it that way.  Once you are moving down the
     runway, and the tail lifts up, you can switch back to cockpit view.   An
     alternate method (and more true to how it is really done) is to look out
     the front 45 degree views and sides and try to taxi parallel to the edges
     of the taxiway.  Still another method would be to use the MAP view.


VI.    VIDEO RELATED INFORMATION

  A.640x400 MODE

     A patch has been written by a user *not* affiliated with FSFORUM or any FS
     related company and thus, the patch is not supported nor endorsed by BAO or
     Mallard Software especially.  It is provided here simply because this text
     file is an attempt to get you what ever information is available related to
     SGA.  You are at your own risk in using the patch.
     
     The following patch will make the SGA 640x400 mode driver display full
     screen, instead of the partial panel with oval instrument dials.  If your
     640x400 screen does not show oval instruments, but rather nice round ones,
     then your version already has this patch done and you should ignore this
     section.
     
     
     From the FS directory, type:
     
          DEBUG VGA_400.gra
          e cs:112 0
          e cs:11d c2 c8
          e cs:1427 10
          w
          q
          
  B.TSENG 4000 GRAPHIC CARDS

     The list of supported video cards and available features on page 11 of the
     SGA manual is self explanatory except for the "Super VGA with Tseng Chip
     Set" category.  In FSFORUM these are usually called Tseng 4000 cards and
     include the Orchid Pro designer II, the Diamond Speedstar, and many new
     inexpensive "no-name" Super VGA cards using the Tseng 4000 VGA chip set. If
     you're looking to upgrade from a standard VGA card to a fast Super VGA
     card, the Diamond Speedstar is a good choice... it's very fast, has good
     Windows drivers, and it's the least expensive of the name brand cards.  Be
     sure to read the ATI section, as there is a new driver soon to be released
     that will show FS in 256 colors!  It must be seen to believed!
     
     A problem has been found with the Tseng 4000 driver that causes the
     instrument panel to change from the Glass Cockpit back to the standard
     640x350 panel when changing aircraft.  After the patch is applied, the
     Glass Cockpit will remain, even when you select different aircraft.
     
     From the FS directory, type:
     
          DEBUG T4_747.gra
          e cs:112 0
          e cs:11d 12
          e cs:11e 89
          w
          q

  C.ATI ULTRA VIDEO DRIVER (BETA)

     The following paragraph relates to the beta ATI Ultra graphics driver (that
     will show FS in 640x480 using 256 colors) that BAO has placed for beta in
     the FSFORUM on CompuServe:
     
          "We have discovered an incompatibility between our ATI graphics
          drivers and SVGA cards utilizing the new ATI 28800-6 (revision 6)
          chip.  If you have this chip on your board, the ATI drivers will flash
          at you because they are not double buffering.  To fix this problem
          type the following line at the DOS prompt:
          
          C> VINSTALL mask ac fe 0
          
          VINSTALL is a utility program supplied with ATI SVGA cards.  It might
          also be named INSTALL or VCONFIG depending on the type of board you
          have. Hope this information helps you ATI owners out there.
          
          Tim Gregson, BAO Ltd."
          
     Review the FSFORUM files ATI_1.ZIP for information on the ATI "Mach-8"
     Graphics Accelerator cards, and the file ATI851.ZIP for a beta version of
     the 256 color driver.  Both files are available in Library 13 - Hardware.
     
  D.VIDEO-7 VRAM II

     A set of patches have been written by a user *not* affiliated with FSFORUM
     or any FS related company and thus, the patches are not supported nor
     endorsed by BAO or Mallard Software especially.  They are provided here
     simply because this text file is an attempt to get you what ever
     information is available related to SGA.  You are at your own risk in using
     patches.
     
     The following patches will make the SGA VIDEO-7 drivers compatible with the
     VIDEO-7 VRAM II video adapter.
     
     
     800x600 Enhanced Instrument Panel
     From the FS directory, type:
     
          DEBUG V7_600.gra
          e cs:11d b6 3b
          e cs:3738 d
          w
          q
     
     640x480 Glass Cockpit Instrument Panel
     From the FS directory, type:
     
          DEBUG V7_747.gra
          e cs:11d ad 7f
          e cs:161d d
          w
          q
     
     640x480 Standard Instrument Panel
     From the FS directory, type:
     
          DEBUG V7_480.gra
          e cs:11d 43 bf
          e cs:1503 d
          w
          q
     

VII.   MISCELLANEOUS PROBLEMS

  A.JOYSTICK INTERFERENCE WITH SOUNDBLASTER (AND PRO)

     When using Soundblaster digital sounds and speech, sound DMA causes timing
     interference problems with FS4's joystick routines.  This causes the screen
     indicators for the yoke to shake a bit.  The problem has little effect on
     flight.  Turning sound on and off causes the controls to move a little too.
     
     This problem is worse on slower computers, and is worse on the prop sound
     than the jet sound due to higher sampling rates.
     
     If you have more than one joystick port in your computer, try switching to
     the port on the Soundblaster card and disabling your other one(s).
     
     There is one work-around.  You can switch to AdLib sound on the Sound menu
     (Soundblaster can run in this mode and produce synthesized sounds).  Speech
     isn't available in this mode.
     
  B.BOBBING

     Some Soundblaster owners have experienced the aircraft "bobbing" mentioned
     in the SGA README file. The cure seems to be to plug the joystick into the
     Soundblaster port rather than use another game card. Others are using
     Soundblasters with the joystick plugged into a multi I/O card joystick port
     with no trouble.  Another way to help cure the problem is to hit the K key
     (from within FS4) to recalibrate the joystick (if you are in flight, be
     sure to run your throttle back up as it will be set to 0 with this
     keypress).

  C.MAP DISPLAY

     The numlock key for toggling the map display on and off does not work (in
     version 1.0) with the 640x480 747 or 800x600 cockpits. Use the 2,8 menu
     choice instead. The 747 cockpit has no separate map window, it uses the MFD
     display in the instrument panel for the map.  Version 1.01 and up have
     corrected this problem.

  D.640x480 INSTRUMENT PANEL

     The instrument panel in the 640x480 cockpit has a "squashed' look... the
     gauges are oval, not round, even when your screen is correctly sized for a
     640x480 display. The proportion was checked by viewing a multi-sided
     building in the ASD editor's overhead view. The building appeared as a
     circle, not an oval.  So apparently the oval gauges are "normal" for this
     display.

  E.OVERLAPPED 3D-WINDOW OR GAUGES

     If you running one of the SGA enhanced graphic drivers and notice that your
     3D window or gauges are overlapped, go to the VIEWS menu and change the
     size or move the windows around until they appear correct.  Then save a
     mode to disk to be able to recall the new window settings.

  F.SCREEN FLASHES

     If the screen flashes when you are using one of the enhanced graphic
     drivers, the video driver you chose may not be supported by your video
     card.  Check the box or the manual to be sure that your video board is one
     that is supported.

  G.SCREEN GOES BLANK

     If the screen goes blank when you are running FS, the video driver you
     chose may not be supported by your video card.  Check the box or the manual
     to be sure that your video board is one that is supported.

  H.SCREEN ROLLS IN 800x600 MODE

     If your picture rolls or cannot otherwise sync in 800x600 mode, your
     monitor may not be able to support 800x600 graphics.  Check the manual that
     came with your monitor to verify whether is supports this video mode or
     not.

  I.FRAME RATE SLOW DOWN WITH 800x600 MODE

     Many people are surprised at the rather severe slowdown in frame-rate when
     using the higher resolution drivers on some video cards.  This is a normal
     occurance and should be expected.  The program can have twice as many
     pixels to push around when using the 800x600 screens so it would be
     expected that the frame rate might be half of what you are accustomed to
     with the 640x350 VGA screen.

  J.LOCKUPS WHEN CHANGING MODES OR USING POSITION SET

     Some people are reporting that the computer locks up tight when selecting a
     new location Mode (.MOD file) or when using Position Set to change
     locations.  This generally only happens when using the SoundBlaster sound,
     so if you experience this problem a workaround is to switch to Adlib sound
     before changing locations and then switch back to SoundBlaster sound.

  K.DMA CAUSED LOCKUPS WITH GEAR ACTIVATION

     There is a known problem caused by DMA channel conflicts in computers with
     multiple DMA based hardware that can lock up the computer when the gear is
     activated for up/down action.  If you were not in the 747 aircraft, then
     there is no fix.  If you were in the 747 aircraft, then try using another
     aircraft, as ASD is the cause of the lockup.
     
  L.CHANGING YOUR DMA TO 0 (ZERO)

     (From messages written by Ed Van Every) To get your SGA to support DMA 0,
     copy the appropriately configured CT-VOICE.DRV form your \SB(PRO)\DRV
     directory over the existing one in your FLTSIM directory (make a backup of
     the driver in FLTSIM first).  (If you have changed your IRQ, DMA and/or I/O
     make sure you "reinstall" your "VOICE DRIVER" using INSTDRV.EXE in your SB(-
     PRO) directory before you copy it over.  It will update the contents of the
     CT-VOICE.DRV with your responses.  You may have to actually run INSTDRV
     while you are in the \SB(PRO)\DRV directory so it can find CT-VOICE.DRV.)

  M.CHANGING YOUR IRQ TO 10 (TEN)

     (From messages written by Ed Van Every) To change your SGA to support IRQ
     10, you will need to have a good sector or hex editor or know how to use
     debug.
     
     The third byte in the SOUND.DEF file is used to identify the IRQ for your
     SB (SBPRO) card.  You can use a hex editor to modify the third byte to set
     it appropriately.  Remember your working in hex so IRQ 10 would be stored
     as a 0A.  Once you make this modification, you will not be able to enter
     the "sound control" menu in flight simulator anymore without crashing your
     system, so make sure everything else is set right (in the "sound control"
     menu) before you make this hack.  If you ever need to revisit the menu,
     just go back to SOUND.DEF and set the third byte to one of the supported
     values (07 for instance).  The next time you start the simulator, you wont
     have any sound, but you will be able to make changes under that menu.  Then
     when you get done with your changes, save the settings, exit FS, and redo
     the IRQ 10 hack.
     

VIII.  FOR FURTHER ASSISTANCE

     For any questions on Flight Simulator, Aircraft and Scenery Designer, SGA,
     FLIGHT PLANNER, or other FS related products; ask in the appropriate
     section of CompuServe FSFORUM and the members there will be glad to help.

     For Mallard Software Tech Support - (214)436-0044
          SGA, FLIGHT PLANNER, and MAC SCENERY UPGRADES.
     
     For Microsoft Inc.   Tech Support - (206)454-2030
          FLIGHT SIMULATOR and A&SD.
     
     For SubLOGIC Inc.    Tech Support - (800)637-4983
          ATP, NFL, and SCENERY DISKS.


IX.    CREDITS

     Original article copyright 1991 Mike Barrs, all rights reserved.
     Changes/Additions copyright 1992 Robert M. MacKay, all rights reserved.
