To: F-15-III Owners From: MicroProse Date: January 2, 1993 Updated: March 10, 1993 Subject: F15 III Problems * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * In response to some of the early problem reports, I have compiled a list of some suggestions. 1) There is a known problem with using the coolie hat to switch views with an early Thrustmaster joystick that is plugged into a Sound Blaster sound card's joystick port. This is specifically mentioned in the Technical Supplement. It is a hardware problem with the joystick and not a problem with our software, it is Thrustmaster's problem. 2) The joystick is auto-calibrated in F15 III. However, the calibration routine cannot effectively determine the entire dynamic range of each individual's joystick, so it uses a conservative estimate. To properly get the entire range, the user must "stir" the stick to all four corners when the home screen first comes up. This must also be done each time "Alt-J" is used, either in the wrapper screens or in the game. Likewise for picking the "Recalibrate" option from the menu bar in the game. 3) When users encounter mouse drift, they are usually seeing the results of the mouse pointer being pushed around by a drifting joystick. Have the user "stir" the stick to get the entire dynamic range established. If that doesn't fix it, have them type "Alt-J" to re-center the stick and then stir it. 4) For in-game lockups, check the setup using the DOS "mem" command. Minimum memory limits are described in the tech supp and are also check by the install program and the F15 program itself. We think that players may be attempting to run the game with not enough conventional memory or EMS. 5) Anytime someone gets speech during the opening but not the game, it means there was insufficient memory to load the speech driver or the speech data. This should have been flagged when the user ran the Install program. The driver is loaded into conventional memory and the data is loaded into EMS. Try to run the DOS command "mem" and check the free EMS and conventional memory. This process and the program memory requirements are described in the Technical Supplement. 6) If the game locks up when the user first gets to the home screen and tries to move the cursor with the mouse or joystick, try the following: When the opening animation is running, continually push the mouse or joystick so as to move the cursor to the top of the screen. Basically you want the cursor to be at the top of the screen when the home screen fnially comes up. This has worked for some customers. Obviously it is not the final solution, but it does let the users play the game. 7) If the game locks up in the Install process where it asks about Modem configuration, a fix has been established. The Install program was assuming that an EMS manager was present (EMM386) and crashed if there was not one active. There is a new version of the Install program available that handles this condition. A simple work-around is for the user to set his Config.sys up to include the EMS manager before running the old Install program. The new Install is available as Filename "F15INS.ZIP". 8) There is a known problem with AHEAD Video Cards and DrDos. We are looking into patches for those problems at this time. 9) Here is a example of the startup files which are created by the BOOTDISK program which comes with F-15 III. AUTOEXEC.BAT: @ECHO OFF PROMPT $P$G PATH= LOADHIGH MOUSE.COM C: CD \MPS\F15 F15 CONFIG.SYS: DOS = HIGH,UMB DEVICE=HIMEM.SYS DEVICE=EMM386.EXE ram x=B000-C400 frame=e000 5136 FILES=20 BUFFERS=20 REM * Next line is for a ProAudio Spectrum Card * devicehigh=C:\PROAUDIO\MVSOUND.SYS D:3 Q:5 J:0 SHELL=C:\DOS\COMMAND.COM C:\DOS\ /P 10) GATEWAY Computer users receiving the "Write Error" messages should according to GATEWAY, "disable the HD1 Block Mode on the system's Phoenix Bios setup screen". * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * NEW as of March 10, 1993 * DRDOS There now is a patch for DRDOS Users available on their BBS. At this time I do not have the file name or BBS number but hope to have it soon. * MODEMS The following are posts from the MicroProse BBS for those having modem problems with US Robotics and Zoom modems: From : CRAIG NELSON Subject : USR Modem Strings Conf : 000 - Main MPS Con The Modem String/Configuration For the 16.8k USRobotics Dual: Dip Switches UP: 1,2,4,6,7 & 10 Dip Switches DOWN: 3,5,8,9 Wide Switch : UP String : AT&F [Hit Return] ATE1Q0M1X7V1S7=60 [Hit Return] AT&A3&K3&B1&C1&D2&H1&M4&N0&R2&W [Hit Return] [This string is supposed to work with all the newer USRobotics] [Dual Standard Modems with the retangular LEDs. ] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From : HAROLD KISTNER Subject : F15 III & USR Modems Conf : 000 - Main MPS Con I have been running F15 with A USR DS14.4 modem at 9600 baud. I have connected with a friend and have played several games with very little problems. He is using a Supra high speed modem. We tried to run 14.4 but could not hookup. I was not able to get the USR to dial out through the modem screen. Hope the design team will jump right on the problem and get it corrected soon. In the mean time I am using a make shift method of dialing out by editing the modem.int file by placing the number I want to dial right after the first ATD line and then goto the game, setup options (if going to be the caller) then goto the modem screen, setup as caller and no voice. Place cursor on # and press enter. This has worked everytime so far. Below is my MODEM.INT file I am using for my USR DS 14.4 modem. Hope this helps +++ ATE0V0X0M1&M0&N0&K0 ATA ATA ATDT999-9999 ATD ATH - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - From : JASON REGNER Subject : F-15 III ZOOM MODEM I have finally gotten a working MODEM.INI for my Zoom 14.4k: +++ ATE0V0X0&Q0 ATA ATA AT&Q6S37=9DT AT&Q6S37=9DT ATH This works just fine for connecting to another V.32 modem. I imagine it would not work for 2400 baud users since it forces a 9600 connect. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * OS/2 Information From : LEE JOHNSON Subject : F15 III OS/2 I got SE3 to run under OS/2 2.0 by doing the following: Tear off a program object from the template. In the 'Path and file name field, enter the path to the F15.COM file; e.g. C:\MPS\SE3\F15.COM, or whatever you installed it as. Use the following DOS settings: DOS_BACKGROUND_EXECUTION On DOS_HIGH On DOS_UMB Off DPMI_MEMORY_LIMIT 0 EMS_MEMORY_LIMIT 1024 HW_ROM_TO_RAM On HW_TIMER On IDLE_SECONDS 0 IDLE_SENSITIVITY 100 VIDEO_RETRACE_EMULATION Off VIDEO_ROM_EMULATION On XMS_MEMORY_LIMIT 256 The DOS_UMB setting is very important. If you turn it ON, you'll get the "Out of memory error, 3" which other people have seen. It must be turned OFF. The XMS setting can be set to 0 if you don't need it. I only use it bec I use 4DOS, which I have configured to use XMS for swapping. SE3 seems to work fairly decently under OS/2, at least for me. -- Lee - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks to the above MPS*BBS Members for their Help! Quentin/MicroProse