HELP FILE FOR VIPER SOFTWARE SIMULATIONS V1.45 and ON Index A: SYSTEM REQUIREMENTS 1: KNOWN PROBLEMS 2: Do's and Don'ts 3: Help with flying SYSTEM REQUIREMENTS: (SVGA MODE 640*480 256 Colour VESA) Minimum System 486DX66 with 4Mb of RAM Local or PCI video BUS with VESA SVGA CARD or Vesa driver loaded capable of 640*480 256 colours 1Mb of video memory required. ***IMPORTANT NOTES ON VIDEO CARD TYPE AND SUPPLIED BATCH FILES*** Each mission is started with a batch file. Two batch files are supplied per mission for different video modes. Batch files with the words 'VESA' in them, support VESA 1.2 compliant video cards. Batch files with the words 'S3' in them, are for S3 based video cards e.g. Diamond Stealth. If your video card uses the S3 chipset be sure to use the correct batch files. The frame rate will be 20% faster. Other video cards should use the VESA batch files. If you try an S3 based mode with a non S3 card you will get the message 'video bios not responding' and your system will hang. NB: YOU CANNOT RUN THE SIMULATION FROM THE EXECUTABLE FILES. YOU MUST USE THE SUPPLIED BATCH FILES. KNOWN PROBLEMS 1: Soundblaster 16 Multi media sound card Engine sound sometimes stops after other sound effects, e.g. guns fired. We suspect a bug in the SB hardware when running 32 bit VCPI software. Simply click button 2 on your joystick (Weapons toggle) or hit key F if using the keyboard (Drops a flare) When the new FX stops the engine sound comes back. Message: Previously installed software is neither DPMI or VCPI compatible. And game will not load. Cause: EMM386 loaded with NOEMS or NOVCPI switch. If you must use EMM386 use EMM386 RAM instead. This will still provide access to UMB's and extended memory. Backup your AUTOEXEC.BAT AND CONFIG.SYS Files BEFORE you start modifying them. See your DOS manual for further details about modifying these files, and EMM386 switches. Some video cards will lock the system if running in SVGA mode. This is caused by EMM386 using the mono UMB area of the video ROM for extra memory. Either run the simulation from a boot disk, or edit EMM386 command line to remove the conflict. DO'S AND DON'TS 2: Do run the game from DOS only DON'T try to run it from a shell such as PCTOOLS or Windows. Win95 users should run the simulation from either safe DOS mode or from a DOS bootable floppy disk. Do use a Joystick rather than the keyboard or mouse. Trying to fly an aircraft with such realistic handling qualities as this with the keyboard means one of two things. Either you don't take flight sims seriously, or you are playing it in the office where a joystick would look a bit odd! Either a: stick to space invaders or b: get on with the spreadsheet you are supposed to be working on. HELP WITH FLYING 3: Rule one, use a good quality joystick (Gravis, thrustmaster etc.) Remember to use the elevator trim control + - on NUM PAD so that the aircraft will fly straight and level at the given throttle setting. Use the waypoints (/) forward slash key to find your way about the flying area. Learn what the various cockpit instruments are, and how to use them. Most of the vital information is contained on the heads up display (HUD). Another vital instrument is the ADF (Auto direction finder.) To see this working, press the / key before takeoff and watch the ADF needle move around as you toggle through the waypoints. The needle is pointing to target areas. After take off, turn into the needle until it is pointing straight up. This means you will be flying towards the target. Note that waypoint 100 is always your home base.