Mundo do CD-ROM 2

home *** CD-ROM | disk | FTP | other *** search

/ Mundo do CD-ROM 2 / CDROM02.iso / jogosdos / duel / readme.txt < prev next >

Wrap

Text File | 1995-10-24 | 19.1 KB | 493 lines

Fighter Duel Demo Oct 23, 1995 (c)1995, Philips Media Games, Inc. Written by Jaeger Software, Inc. in association with Philips Media, Inc. Portions (c) 1993-1995 SciTech Software Portions (c) 1995 Miles Design This demo is copyrighted, but freely distributable as long as all files in this archive are included and kept unaltered. Please distribute it to as many bulletin boards and information services as you can. The Fighter Duel demo is limited in these areas: You may fly one aircraft, the Spitfire MK1 and against only Spitfire MK1s. The situation is limited to only the "Flying Circus". You may fly for only 3 minutes at a time. Fuel load is locked to a quantity that will last 3 minutes. The ability to print out the flight log is disabled. Two player modes are disabled. The contents are: 1. System Requirements 2. Installation 3. Keyboard Commands 4. Memory 5. Windows 95 6. Video 7. Sound 8. Screengrabs 9. Digital Simultaneous Voice & Data modems 10. Notebook Gameport 11. Troubleshooting ---------------------------------------------------------------------------- 1. SYSTEM REQUIREMENTS: ---------------------------------------------------------------------------- Minimum Requirements: 486 DX 33mhz 8 megs of ram. 500k Conv 7mb XMS/EMS 1 meg VL or PCI local bus SVGA card , Vesa 1.2 or Univbe compliant. Sound Blaster compatible sound card for sound. Support for Ensonique, Media Vision, Microsoft Sound System, Gravis Ultra Sound PC speaker not supported. Mouse (100% Microsoft compatible) Recommended for full appreciation: Pentium system with >=256 cache 16 megs of ram. Fast dos video card such as Diamond, ATI, Tseng brand VL or PCI SVGA card. Sound Blaster 16 class sound card with Amplified speakers with sub woofer. Joystick with "Top Hat" and throttle Rudder pedals with Toe brakes. 9600 Baud or greater modem The retail Fighter Duel also requires a CD-ROM drive. ------------------------------------------------------------------------------ 2. INSTALLATION: ------------------------------------------------------------------------------ To install and run the Fighter Duel demo: The Fighter Duel demo archive either comes as 1 file named FDDEMO.ZIP or as two files named FDDEM1.ZIP and FDDEM2.ZIP that will fit on a 1.44MB floppy. Make a directory on your harddisk such as FD. Copy the FDDEMO file(s) to your harddisk and place them into your FD directory. Unzip the FDDEMO files using Pkunzip. Example: Pkunzip.exe FDEMO.ZIP Type FDDEMO and hit return to run the demo. The FDDEMO will lead you through some configuration screens and then run. After the Fighter Duel demo is successfully installed, you may delete the Zip files on your harddisk. ---------------------------------------------------------------------------- 3. KEYBOARD COMMANDS: ---------------------------------------------------------------------------- ESC = Quit back to Pre-flight interface Q = Quite sound. A = Turn off and on gunsight, you can still fire, but the gunsight is invisible and the hit counter is not shown. S = Adjust range of optical gunsight. Shift S to restore to full back. I = Instrument panel on. O = Toggle to last pan/exterior view Return = Instruments off and return from exterior view to straight ahead Enter T = Turbo around (move at 16 times your velocity) Shift T is slower turbo. (Turbo is disabled in Two player modes) Z,X = Throttle (shifted Z and X goes to full on and full off throttle) W,E = Flaps, up and down G = Gear control. H = Hook (gear must be down first and plane so equipped) ~ = Save screen as PCX file V,B = Rudder left and right. (shifted V and B goes to full left and right) DEL = Left wheel brake PgDn = Right wheel brake End = Brake release L = Launch from catapult P = Pause, hit it again to advance 1 frame, hit any other key to unpause , = Lock to Low graphic detail . = Lock to High graphic detail / = Auto graphic detail based on GUI set framerate Cursor keys, fine analog trim control. View keys: With all view keys, you must hit enter or return to return to straight ahead. 1 = Over the left shoulder 2 = Back and up 3 = Over the right shoulder 4 = Left 5 = Up 6 = Right 7 = Up and left 8 = Up and forward 9 = Up and right Exterior aircraft views: With all view keys, you must hit enter or return to return to straight ahead. All views are looking at your aircraft from... F1 = Chase F2 = North F3 = East F4 = South F5 = West F6 = Looking Up from 40 ft. F7 = Looking Down from 40ft. F8 = Looking Down from 500ft. F9 = Looking Down from 1000ft. F10 = Looking Down from 2000ft. Views supported on the CH FlightStick Pro: Forward = Forward and up Left = Left over the shoulder view Right = Right over the shoulder view Back = Back and up Views supported on the Thrustmaster FCS: Forward = Forward and up Left and back = Left over the shoulder view Right and back = Right over the shoulder view Back = Back and up View Aircraft keys: Esc = Quit the viewer Cursor keys. Up and Down moves the aircraft further and closer to you. ~ = Save screen as PCX file ---------------------------------------------------------------------------- 4. MEMORY: ---------------------------------------------------------------------------- Fighter Duel demo Memory Requirements: 500k of conventional ram, 7 megs of XMS or EMS. To see the free memory, type Mem and hit return on Dos 6.X or higher machines. The output should look something like this. This system is pretty well optimized. Memory Type Total Used Free ---------------- -------- -------- -------- Conventional 636K 34K 602K Upper 107K 107K 0K Reserved 0K 0K 0K Extended (XMS) 23,445K 181K 23,264K <----Should be 7,000 or larger ---------------- -------- -------- -------- Total memory 24,188K 322K 23,866K Total under 1 MB 743K 141K 602K Total Expanded (EMS) 23M (24,543,232 bytes) Free Expanded (EMS) 16M (16,777,216 bytes) Largest executable program size 602K (616,224 bytes) <-----500k or larger Largest free upper memory block 0K (0 bytes) MS-DOS is resident in the high memory area. To get more conventional memory please see your Dos manual for usage of the Memmaker program. Seven megabytes of XMS/EMS ram is the minimum that the Fighter Duel demo needs to safely run. You will only have approximately two enemy to fly against. The Fighter Duel demo will dynamically adjust the number of enemy upward as more XMS/EMS is available. You should have all eight enemy at once available with about 7.3Mb of XMS available. Do NOT edit or delete the CONFIG.SYS or AUTOEXEC.BAT on your hard disk with out making a backup copy first. It is safest to copy them to a floppy for backup. The largest memory consumer on modern Dos machines is the SmartDrive harddisk caching program used in Dos and Windows 3.1. On an 8 meg machine unless set otherwise, it will use 2 megs of ram for its cache. The line in the autoexec.bat line that launches usually is something like "C:\Windows\Smartdrv" Either comment the line in the autoexec.bat file with a leading ; or reduce Smartdrive''s cache size. The number at the end of the Smartdrive line sets the cache size in bytes. Try 256 or 512. Disabling Smartdrive entirely will usually significantly slow down Windows 3.X performance. Especially loading and exiting of Windows 3.1. If you still cannot get enough free memory to run the Fighter Duel demo, it will be necessary to make a boot disk. To make a Fighter Duel demo boot floppy: Format a floppy with the option to make it bootable. Example: FORMAT A: /S Copy your CONFIG.SYS and AUTOEXEC.BAT from your hard drive to the floppy. Change to the floppy. Edit the CONFIG.SYS and AUTOEXEC.BAT files on the floppy. See your DOS manual for details on how to work with CONFIG.SYS and AUTOEXEC.BAT. The only item the Fighter Duel demo requires is a mouse driver. Here is an example of a minimum startup for the Fighter Duel demo: [CONFIG.SYS] DEVICE=C:\DOS\HIMEM.SYS DOS=HIGH FILES=50 BUFFERS=30 << ANY SOUND RELATED COMMANDS >> [AUTOEXEC.BAT] PROMPT P$G$ PATH C:\DOS << ANY SOUND RELATED COMMANDS >> << MOUSE DRIVER >> << VESA DRIVER IF NEEDED >> CD C:\ << CD to the logical drive to which you installed the demo >> CD FDDEMO << CD to the directory in which the Fighter Duel demo is installed >> FDDEMO Include only the items listed above. Delete or add the word "REM" to the start of any line that is not mentioned above. Restart your computer with your new boot disk in drive A: The machine should boot, not show any error messages and directly run the Fighter Duel demo. ---------------------------------------------------------------------------- 5. WINDOWS 95 ---------------------------------------------------------------------------- The Fighter Duel demo will generally perform better when not run from a Windows 95 MS-DOS prompt. When the Fighter Duel demo is run from a Windows 95 Ms-DOS prompt, it will attempt to determine if you in fact have enough actual free memory available. Depending on programs run in the Windows startup and or other Windows features such as networking, you may not have enough actual free memory to run the Fighter Duel demo. Windows does have a memory virtualizing system that usually can give the Fighter Duel demo the memory it needs by shifting other programs in memory temporarily to the harddisk. We found the delays and and or large pauses during flight unacceptable. We recommend that you either shutdown Windows 95 and restart the computer in MS-DOS mode or create a shortcut to put your computer into MS-DOS mode while running the Fighter Duel demo. ---------------------------------------------------------------------------- 6. VIDEO: ---------------------------------------------------------------------------- The Fighter Duel demo requires VESA compatibility for video access. VESA stands for the Video Electronics Standard Association. VESA video progamming standards allow programmers a common way to access video cards. Modern video cards usually offer VESA software compatibility via either a built-in chip called a bios chip or a small TSR program run from the autoexec.bat file. The Fighter Duel demo utilizes some standard high performance VESA commands that are not properly implemented on some video card VESA bios. For compatibility and speed, we provide VESA compatibility through the Scitech Univbe Ultra VESA graphic library. It provides fast 32 bit protected mode VESA 2.0 graphic compatibilty on over 160 video chipsets. Most video cards do not come with the newer VESA 2.0 standard which Univbe provides. The Fighter Duel demo has been designed to automatically detect and use Vesa 2.0. For best performance, use the Univbe driver with the Fighter Duel demo. The Fighter Duel demo will configure and use Univbe by default. Univbe is compatible with the following chipsets: . Acer Labs ALi CAT-32/64 . Ark Logic ARK1000VL, ARK1000PV . Avance Logic AL2101/2201/2228/2301/2302/2364 SuperVGA . Ahead V5000A, V5000B . ATI Technologies 18800, 28800, Mach32, Mach64 . Chips & Technologies 82c45x, 655xx, 643x0 WinGine . Cirrus Logic CL-GD62xx, 5402, 5422/4/6/8/9, 5430/4 . Cirrus Logic LCD CL-GD64xx . Compaq IVGS/AVGA, QVision QV1024/1280 . Diamond Viper P9000+W5186/OAK87 VLB and PCI . Everex Viewpoint, Viewpoint/NI, Viewpoint/TC . Genoa Systems GVGA . Hualon HMC86304/14 . IIT AGX-010/11/14/15/16/17 . Matrox MGA Atlas . MXIC 86000/86010 SuperVGA . NCR 77C20/21/22E/32BLT . OAK Technologies OTI-037C/057/067/077/087 . Paradise/Western Digital PVGA1A, WD90C1x/2x/3x . Primus 2000 SuperVGA . RealTek RTG3103/3105/3106 SuperVGA . S3 86c911/924/801/805/928/864/964/866/868/968/Trio32/Trio64 . Sierra Semiconductor Falcon/64 . Trident 88/8900/9x00/8900CL/8900D/9200CXr/9400CXi/9420DGi/9440AGi . Tseng Labs ET3000, ET4000, ET4000/W32/W32i/W32p . UMC 85c408/18 . Video7 VEGA, HT208/209/216 . Weitek 5086/5186/5286, P9100 If after installation, no error messages about VESA compatibilty are reported on the command line, but the opening title pictures do not display properly or the screen does not display properly during flight, your video board may not be compatible with Univbe. The first thing to try is to use your video card's built-in VESA bios. Please note that some built-in VESA bios on some cards are not compatible with the Fighter Duel demo. To disable UNIVBE: Type NOUVESA from the FDDEMO directory. This will delete the Univbe driver file and the Fighter Duel demo will then use your video card's built-in VESA. Please note that some video cards require that you run a small VESA compatibility program for VESA compatibility. To reenable UNIVBE, Type UVESA from the FDDEMO directory. This will generate a Univbe driver and the Fighter Duel demo will use it the next time it is run. ---------------------------------------------------------------------------- 7. SOUND: ---------------------------------------------------------------------------- The Miles Design AIL sound system is used for universal sound support. On installation, the AIL Setsound.exe program is run. Follow its instructions to configure for your sound board. You may reconfigure or check your configuration later by typing Setsound.exe while in the FDDEMO directory. Please note that the master volume level for your sound card is a combination of its volume knob (if equipped) and sound levels set via program command parameter set in either your autoexec.bat file or by Windows. If the sound seems too low, check the master volume levels in the autoexec.bat file and or Windows sound control first. Windows 95 will set the volume on Reveal Se400- Rev3 and Aztech Gold Washington Sound Galaxy 16 sound cards to zero when restarting into MS-Dos mode. The Volset.exe program will need to be run and the volume set back up before running the Fighter Duel demo. Please refer to your sound card manual for details on the possible autoexec.bat program command parameters. ---------------------------------------------------------------------------- 8. SCREENGRABS: ----------------------------------------------------------------------------- The Fighter Duel demo has the built-in ability to screen grab what you are seeing while either viewing the aircraft or flying. Hit the ~ key to save a 256 color 640x480 PCX format file. The Fighter Duel demo saves the file as a sequence beginning with FDuel0001.pcx. ---------------------------------------------------------------------------- 9. DIGITAL SIMULTANEOUS VOICE & DATA MODEMS: ----------------------------------------------------------------------------- Please note that two player mode is not included in this demo of Fighter Duel. Fighter Duel supports the new Digital Simultaneous Voice and Data Modems (DSVD) created by a joint a venture of Intel, U.S. Robotics, Rockwell, Creative Labs, and Hayes. These new line of V.34 28.8 modems allow you to have two computers transfer data at up to 14.4bps while you are simultaneously talking on the same phone line. When the voice line is not used, they function as standard V.34 28.8 modems. You may call your Fighter Duel opponent and then have Fighter Duel start with only a quick interruption of your call as the modems negotiate the connection. Most modem playable software requires you to set your modem to turn off error correction, data compression, etc. Fighter Duel is designed to work well with your modem set with error correction and data compression on which not only improves connection reliability, but is a requirement for DSVD modems. ----------------------------------------------------------------------------- 10. NOTEBOOK GAMEPORT: ----------------------------------------------------------------------------- In addition to supporting standard PC gameports, the Fighter Duel demo supports the Colorado Spectrum Notebook Gameport (NG). The NG allows you to connect your joystick, yoke, and/or rudder pedals to your notebook or desktop PC via a standard serial port. To use the NG with the Fighter Duel demo, install the hardware as outlined in the NG manual, install the NG software driver, and check its operation with the NG diagnostic program, NGDIAG.EXE. Whenever the NG is attached and the software driver, NG.EXE is run, the Fighter Duel demo will automatically use it for all joystick, yoke, and/or rudder pedal functions. Set the Flight, Throttle, and Rudder controls in the the Fighter Duel demo pre-flight interface as you would normally. Please note that toe brakes are not supported through the NG. ----------------------------------------------------------------------------- 11. TROUBLE SHOOTING: ------------------------------------------------------------------------------ "The Fighter Duel demo REPORTS THAT I DON'T HAVE ENOUGH VIDEO MEMORY" FDDEMO requires 1 meg of video ram. If in fact you do have 1 or more megs of video ram, you may have to manually configure the Univbe video driver. To do this, enter the FDDEMO directory, type "uvconfig" and hit enter. A screen will display that shows your detected video chipset and a guess at the video memory. If the memory figure shows 256 or 512, use your mouse pointer to click the down arrow to the far right of the video memory number. Change it to match the amount of ram on your video card. Do not adjust it for more memory than your card has. Do not select or change the options labeled "Ignore old VBE BIOS", "Disable VBE 2.0 extensions", or "Disable Linear Frame Buffer". Click "OK". Uvconfig may ask to do some quick tests on your video board. Allow it to do so. When it exits, try the Fighter Duel demo again. "I ONLY GET A FEW ENEMY" In low memory situations, the Fighter Duel demo will reduce the number of foes. See the section above regarding memory. "The Fighter Duel demo REPORTS I DON'T HAVE ENOUGH CONVENTIONAL OR XMS MEMORY" See the section above regarding memory. "WHILE FLYING THE GUNSIGHT AND OR THE OVER THE SHOULDER VIEW FLICKERS" The Fighter Duel demo is very optimized to go as fast as it can at all times. On very fast systems with very fast video cards flicker may occur. The "Decrease Framerate to Reduce Flicker" option in the graphics control window should stop the flicker. Unless you experience flickering, do not use this option as it will needlessly reduce your framerate. "THE OPENING PICTURES OR THE VIEW WHILE FLYING ARE NOT DISPLAYING PROPERLY" See the section on video above. "I GET NO SOUND" The sound volume on your sound card may be too low. See the section above on sound.