Posted-By: auto-faq 188.8.131.52
See reader questions & answers on this topic! - Help others by sharing your knowledge
------------------------------------------------------------ OS2.GAMES Sep 20, 1995 Version 2.1i ------------------------------------------------------------ ADMINISTRIVIA: This version of the list covers OS/2 version 2.1, 2.11, and Warp. The HTML version is finally complete! Check it out at http://eyelab.msu.edu/os2games This list is really starting to get large, so if anyone has any suggestions for ways to format it so it's easier to find stuff, let me know. For those of you that want to join the mailing list to receive updates of this file, please read the Where to Get Updates section. I now have a computer again at home, so I can actualyl test things again. The HTML version will now include a What's New and Changed Section, to help you find the most recent updates. My appologies for the fact that I don't always manage to reply to updates that are mailed to me. I really do appreciate you folx mailing them to me, and I'll try to at least reply to them, but I don't always do so if I'm falling behind. (I've currently got about 300 unread email messages from various things (not all due to this list, but some are), so you can imagine what it's like for me to try catching up to things. ------------------------------------------------------------ INTRODUCTION: This file brings together in one place the information that you need to be able to optimize the performance of your DOS based games. Unfortunately, much of the information still is incomplete, so your help would be greatly appreciated. If you happen to know how to get a game working that isn't listed, or how to get one working that's listed as not working, or even if you know that a specific game doesn't work under OS/2, please mail me (firstname.lastname@example.org) so I can include the information. If you are having problems getting a game to work, please feel free to contact me (email@example.com) and I'll do my best to help you out. Thanks to IBM I now have a copy of Warp. I'll be making changes based on the differences between settings available under 2.1 and Warp over the next week or so. --------------------------------- FUTURE PLANS FOR THE LIST: A .INF version will probably only be made available if I find a tool to automate most of the translation from HTML to INF. Anyone have any ideas? --------------------------------- REPORTING CHANGES: I'd really appreciate it if you would mail me any changes or additions to this list. Some of the things that would be appreciated when you do this are: -Your system setup (things like sound card, IRQ's). This will help me coordinate what works with what. -Please mail this information to firstname.lastname@example.org The recommended way to send me your settings is to go into the settings menu and using the button to save the settings to a file, then drop that file into a mail message to me. Otherwise, just let me know what you changed to get it to work. For a base reference, my home system is (was :P): 486dx2 66 w/16MB Ram Adaptec 1520 SCSI controller OS/2 Warp on a FAT partition on a Seagate SCSI drive Cardex ET4000W32 w/2MB Ram (VLB card) Gravis Ultrasound Max, although most of my experiance with games under OS/2 are from: SB Pro (IRQ 5, IO 220, DMA 1) Mitsumi Double Speed CDROM --------------------------------- WHERE TO GET UPDATES: You can obtain the list from any of several ftp sites. It is typically stored on ftp-os2.nmsu.edu in the /os2/32bit/info directory. This version is games21i.zip. You can also get it off my distribution site for it, which is eyelab.msu.edu in /os2. You can peruse the HTML version by pointing your web browser to http://eyelab.msu.edu/people/gary/os2games/ Many thanks to the Michigan State University Psycholinguistics and Visual Cognition Laboratory for letting me use their server to host this list. I've also started a mailing list that I will send out updated versions of the list on as they become available. This mailing list won't echo things that people send to it, it is only for the purpose of distributing new versions of the list (so traffic will be light on it). You can subscribe by sending email to: email@example.com no subject "subscribe os2games" (without the quotes!) in the body I haven't set it up yet to send the current version on demand yet, but I'm planning on doing this. You can also join this list if you have a forms capable Web browser. Check out http://eyelab.msu.edu/os2games/subscribe.html for this process. ------------------------------- GENERAL TIPS (READ THIS FIRST!): Read the README file in your OS/2 root directory. Also, check the manual for OS/2. Both of these provide information for running some DOS and Windows apps under OS/2. Read the comp.sys.ibm.pc.games FAQ. This is very important since it will tell you about possible problems when running the game even under plain DOS. If you can't find a copy of the FAQ in comp.sys.ibm.pc.games.announce, email Jurgen Appelo, the keeper of the FAQ, but I don't have his email address currently. Also, look to see if a game-specific FAQ is available. Several games have these (Wolf3d, Civ, DOOM). If you have trouble installing the game under OS/2 and you are trying to install the game on a FAT drive, boot up plain DOS (via dual boot or the Boot Manager) and install it there. Sometimes a game (or other app) won't install for some reason under OS/2, but once installed they'll work fine under OS/2. If you experiance strange anomalies or incompatibilities of any kind (especially with older games), try booting a real copy of DOS from a floppy inside a VDM running under OS/2 and run the game in that DOS session. (See VMDISK in the Command Reference online docs for details.) Some games that require keydisks will only work this way. The following are the recommended base settings for running games under OS/2. If you have a game not listed in here, try these out and work from there to try to get it running. Dos Fullscreen: Check this option; Very few DOS games perform well in a window. DOS_BACKGROUND_EXECUTION: OFF (so it won't take CPU time when you switch away from it, and so you don't die while it's running in the background) DOS_HIGH: ON (more memory for those games that need it) DOS_RMSIZE: 640 DPMI_MEMORY_LIMIT: 0 (most DOS games don't use DPMI memory) or DPMI_MEMORY_LIMIT: 16 (more and more recent game use an extender which uses DPMI) EMS_MEMORY_LIMIT: 1024 (most games that use more than 640k use EMS memory. If you're playing an earlier game, you might not need this. Note also, many games may require more than this. Check the box that it came in) HW_ROM_TO_RAM: ON (copies ROM BIOS to RAM--several people have said that this improves performance on their machines) HW_TIMER: ON (very important, especially for games using soundcards) IDLE_SECONDS: 10 IDLE_SENSITIVITY: 100 (very important) INT_DURING_IO: ON KBD_ALTHOME_BYPASS: ON (although keep it off if you want to flip to windowed, such as to check walkthroughs, etc) SESSION_PRIORITY: 32 (This setting is only available under Warp. Note that by raising the priority to 32 will have serious impact on anything running in the background.) VIDEO_FASTPASTE: ON (some people say this helps) VIDEO_RETRACE_EMULATION: OFF (leaving this on can cause some games to run far too fast, and other to run too slow) VIDEO_ROM_EMULATION: OFF XMS_MEMORY_LIMIT: 64 (needed for DOS=HIGH. If the game supports XMS memory, naturally you should raise this) For best performance close ALL windows and apps, especially other DOS apps, before you run the game. Leaving other apps open steals CPU time from the game, thus slowing it down. (Although it IS possible to do high speed downloads while playing games, I don't recommend it) Sometimes you just have to fiddle with the settings until it works well for you, which is why this list is put together. ------------------------------------------- SOUND CARDS: Sound cards are probably one of the leading causes of games not working under OS/2. The following are a couple of suggestions to help, but it's unfortunately all to common for them to be the culprit. Soundblaster cards: Somebody at Creative Labs decided that IRQ 7 should be the default. If your computer has an LPT1: (it probably does), you need to change the IRQ. I recommend IRQ 5, although it may not be free depending on your configuration. Make sure you have the BLASTER environment variable set, otherwise sounds might be cut off funny. (I think more recently Creative Labs realized that IRQ 7 was a bad choice and switched the default to 5). Roland LAPC-1: the default IRQ2 and 330 base address work fine. IRQ 2 is automatically mapped to IRQ9 on 386 and 486 computers. Pro Audio Spectrun-16: Make sure your IRQ's are set to something that is not used. Avoid 7,3,4 (I don't know what these cards can be set to). IRQ 5,2, and 10 tend to be free. You can load the PAS16's mvsound.sys by opening the DOS settings box, and adding a line to the DOS_DEVICE bos, such as: c:\proaudio\mvsound.sys d:3 q:2 The path and the optional parameters will vary of course. Gravis Ultrasound: The utilities that Gravis provides like SBOS and MEGAEM won't run under OS/2. DO NOT even make an attempt to. Recently I've seen some reports that Gravis might rewrite them to allow them to work properly. Also, don't use the Gravis Alpha drivers if you want dos access under OS/2. There are also some shareware drivers available that give you some of the functionality of the Gravis tools under Dos sessions, but you have to have an external midi synthesizer. (I couldn't even get just the digitized sound in OS/2 stuff to work without trapping consistantly with the Manley Drivers). -------------------------------------------- JOYSTICKS: If you are running under Warp and are having problems with your joystick acting funny while playing games, you might want to try downloading and installing their Joystick driver. I'll list the site for it when I find it (couldn't get through to hobbes this evening). -------------------------------------------- DOS EXTENDERS: Apparently there is sometimes a problem trying to run a game that uses a dos extender from an icon on the desktop. DOS4GW (A very popular extender being used these days) is one of those that often causes trouble. Basically this is caused by the program having an odd fileheader that causes it not to be recognized properly. There are a couple of methods that you can use to get around this problem. If the program is one of the many using DOS4GW, in the settings notebook you can set the program to DOS4GW.EXE and the parameters to the name of the executable for the program. Otherwise, you can set the program to be * (similar to the command line shell windows) and the parameter to be: /C d:\path\game.exe. Make sure you also set the working dir to the proper path also. --------------------------------------------- WinG BASED GAMES: Many reports have indicated that WinG will work under OS/2, although your mileage may vary. If you have the option, boot Dos up and install WinG under a real Windows session. It supposedly can be installed under full-screen Win-Os/2 sessions if you don't have that option. If you are having problems, it might be one of several things: -WinG doesn't like your video driver. There's no real solution to this one, unless there happens to be a new version of your driver available that it works with. -Try running it in a full-screen Win-OS/2 mode. Your odds are better there. --------------------------------------------- SPECIFIC GAMES: Start with the base settings that were listed above, making sure to set EMS, XMS, and/or DPMI memory to what is specified for the game you are running. The idea here is to list as many of the games people are running as possible. If you are running a game, or having problems with one, PLEASE mail me so it can be added to the list (firstname.lastname@example.org). A seperate section at the end of the list has been added to detail CD-ROM games seperately. If the game you are looking for is a CD-ROM game, you might want to try looking there first. Please note: If a game is listed as 'runs fine,' then it was tested by either the original maintainer of the list or by me (I do my best to specify which this is). 'Reported to run fine' means that people on the net have said that it runs. Most of the checking here was probably done under os/2 2.x. I believe almost all games that worked under it also work under Warp. I will try to note games where the only information I have applies to Warp. ACES OF THE DEEP: -Apparently won't install under Warp. The user didn't report if it would run under OS/2 if installed under Dos. Sierra was less than helpfull to the user when told he was using OS/2. ACES OF THE PACIFIC: -Several people have reported this game to run fine. -Also note, there is a patch you may need which increases the screen update speed, so if the update speed is slow on your system you might want to try to find it. ACES OVER EUROPE: -The following modification to the default games settings have been recommended: DPMI_MEMORY_LIMIT: DISABLED -Other than this change, the game is supposedly pretty easy to get running, but will not run if set to enabled, and hangs when set to auto. ADVENTURES OF WILLY BEAMISH: -Reported to run fine. AIR WARRIOR: -Make sure you allocate enough DPMI memory (try at least 6, more if it still gives a memory error). -If running from an object, use DOS4GW.EXE as the program and the name of the program as the parameter (I don't know what it is). ALADDIN: -A user reported having problems with the sound (it would periodically give something that sounded like a shotgun). I've also heard rumours that a lot of the Disney stuff has enough trouble running under Dos, let alone os/2. ALONE IN THE DARK: -Reported to run fine. Make sure you set DOS_UMB and HW_NOSOUND to off and HW_TIMER to on for the best sound production. ALPHABET BLOCKS: -Reported to run fine. APBA BASEBALL FOR WINDOWS: -Reported to run fine in a full screen Win-OS/2 session ONLY. -It will NOT work in a seamless windows session. ARCHON ULTRA: -I was unable to get this to run, but didn't spend much time on it. Anyone else try it? A-10 TANK KILLER: -Reported to run fine. ATLANTIS: -Reported to run fine. A-TRAIN: -Another user said that he used the Migrate Applications utility and was able to get music, sound, color all working fairly well. -Reported to run with color if you add in the device section of the dos settings box: c:\os2\mdos\ega.sys (Warp might do this automatically now) BARDS TALE: -Reported to run fine. BATTLE CHESS: -Reported to run fine. BENEATH A STEEL SKY: -Reported to work for a while, but crashes when moving from place to place. -One person suggested disabling the scrolling between scenes might help. BETRAYAL AT KRONDOR: -Reported to lock up 10 minutes into the game. -Using the settings in the migration database with Warp it should work, although the sound card might cause lock-up problems (which might be where the note about that comes from). It should run with PC Speaker or no sound with no trouble. BIOFORGE: -Reported to generate a page fault (doesn't run). BIO-MENACE (Apogee): -Reported to run fine in a real DOS VDM. -Start this game with the /LATCHPEL command line switch to reduce jerky graphics. -The following changes to the default settings for a DOS VDM were supplied by a user: a. Turn DOS_BACKGROUND_EXECUTION Off. b. Turn DOS_HIGH On. (This may or may not already be set - double check.) c. Select DOS_STARTUP_DRIVE, and enter C:\VMB\DOS.IMG in the "Value" field. d. Turn DOS_UMB Off. e. Set DPMI_DOS_API to DISABLED. f. Set DPMI_MEMORY_LIMIT to Zero (0). g. Set DPMI_NETWORK_BUFF_SIZE to One (1). h. Set EMS_FRAME_LOCATION to NONE. i. Set EMS_HIGH_OS_MAP_REGION to Zero (0). j. Set EMS_MEMORY_LIMIT to Zero (0). k. Turn HW_ROM_TO_RAM Off. l. Turn HW_TIMER On. m. Set IDLE_SECONDS to 60. n. Set IDLE_SENSITIVITY to 100. o. Turn INT_DURING_IO Off. p. Turn KBD_BUFFER_EXTEND Off. q. Turn VIDEO_ONDEMAND_MEMORY Off. r. Turn VIDEO_RETRACE_EMULATION Off. s. Turn VIDEO_ROM_EMULATION Off. t. Turn VIDEO_SWITCH_NOTIFICATION Off. u. Turn VIDEO_8514_XGA_IOTRAP Off. u. Set XMS_MEMORY_LIMIT to 2048. BLAKE STONE: -Reported to work fine using the /noxms switch. BREACH 2: -One person has reported that he couldn't get the mouse to work, so he had to use the keyboard instead. CASTLE WOLFENSTEIN 3D: -This game can be real picky. Do not switch away from a session running this game, because it won't restore the screen right. -If you have a SoundBlaster and your sounds are getting cut off, check to make sure you are defining the BLASTER environment variable properly. -I was able to get the registered version to run fine, but the shareware one occaisionally would pause when I picked something up or got hit. -If you can't get the game to start up due to a conflict with LPT2, try starting the game with the /noss (undocumented parameter). (From Shawn Green, email@example.com) CHESSMASTER 3000: -Reported to work fine. CHESSMASTER 4000: -Reported to work fine. CHUCK YEAGER'S AIR COMBAT: -One user made the suggestion that when you are using the PC speaker for sound to start the game and allow it to go through the intro. Then do a test flight and hit a ^S to kill the sound. This stops the sound for future sessions. If you want digitized speech thereafter, you can turn it on during flights, but make sure you turn it off before finishing a mission. CIVILIZATION: -Get the most recent version of the game. I believe this is now version 5. -Always use fullscreen mode. (Tend to get divide by 0 errors if you try running it in a window) -Some people have had problems with running it in Adlib/Soundblaster where the game runs slow. A possible solution is to start the game in PC SPEAKER mode, quit, and run it again during the same DOS session with the Adlib/SoundBlaster Support enabled. This might fix that problem. (Note: I never had this problem with my SoundBlaster Pro) -A possible solution to the divide by 0 errors is to turn COM_HOLD to ON. I don't know that this works. Run it in fullscreen mode, that works, and windowed the game runs far too slow. -One suggestion for running under Warp: before starting the game turn on HW_TIMER. When it gets to the point it's creating the world, turn it off. CIVILIZATION FOR WINDOWS: -Runs fine in either full-screen or seamless mode. I recommend not running this version since it is very slow (nothing to do with OS/2 though). COLONIZATION: -Reported to run fine, although sound effects don't work unless you turn the music off. COLONIZATION FOR WINDOWS: -Reported to work, although it was flakey getting it to start working because of WinG problems. COMMANCHE: MAXIMUM OVERKILL: -This game tries to go into a protected mode, and I believe they use the VCPI standard for that. As a result, it WILL NOT run. -There have been rumors that if the makers hear enough interest they will come out with a patch that will fix this (or a replacement executable, something along those lines). COMMANDER BLOOD: -Reported to run fine. COMMANDER KEEN 3: -Reported to run fine. COMMANDER KEEN 4: -Reported to run fine, but you can't switch away from the session or the screen will get messed up. CONQUERED KINGDOMS: -One person said they couldn't get it to run because the mouse pointer gets lost. Anyone get this one to work? CONQUESTS OF THE LONGBOW: -Reported to run better with VIDEO_RETRACE_EMULATION set to ON. CURSE OF THE AZURE BONDS: -Runs fine. (original maintainer) DAGGER OF AMON RA: -Reported to run better with VIDEO_RETRACE_EMULATION set to on. DARKLANDS: -Runs fine. If the into runs jerky, you can try turning your VIDEO_RETRACE_EMULATION to ON (normally it should be set OFF for this game, so make sure once you've seen the intro you quit and change this setting back) Note: I thought the intro was slow whatever I did. I've never seen the game under DOS, so I don't know how it is normally. -Make sure you get the most recent version, which at this time is Version 7. I had problems running earlier versions. DARKSEED: -The copy protection wants to do something 'illegal' to the a: drive, and OS/2 catches it and stops it. -A couple of possible solutions: -There are a couple of cracks for this game, you could try one of these to see if it removes this check. -A user said he managed to get it to run by booting a real version of DOS under OS/2, but that the digitized sounds need to be switched off. DARK SUN: -Starting it from an object on the desktop appears to give an "unable to open window" error. This error reportedly goes away if you open the full screen dos session and start the program normally. DARKSUN II: -Reported to work completely except for the music. (Sound effects worked). Use the normal Games settings. DAY OF THE TENTACLE: -Reported to run fine. DESCENT: -Works great, including sound. Will also run in a window (although it is definitely slower there). If you switch from window to full-screen, the screen doesn't come up right, but hitting tap to bring up the map will fix it. -This game runs better for me under OS/2 than it does under Dos. I've got a system that's at the lower end of the playability realm for Descent. -I've got settings for this one that can be loaded into an OS/2 session if you're running warp. Check out eyelab.msu.edu /os2/games/descent.txt DINOSAUR ADVENTURE: -Reported to run fine. DINOSAUR DISCOVERY KIT: -Reported to run fine. DISCWORLD: -Will not run. DOOM: -Id includes a list of recommended settings for Doom under OS/2, so I'd recommend looking into using those. Some people have reported that Doom ran better with the default games settings. -Version 1.2 of Doom will not work with sound enabled. Do not try this because it could cause your system to lock up. A patch is supposedly in the works to fix this problem. -The most recent version I've tried is 1.1, which ran fine for me. Doom can be a very picky game, and you may have problems trying to get it to run even under Dos. DRACULA UNLEASHED: -Uses a proprietary memory manager. In other words, it doesn't work. DRAGON LORE: -A user reported that the game complained that a memory manager was needed to run the game. This might be caused by not having the memory settings for a dos box incorrect. -Someone else reported that fiddling with the memory settings got it to work. -I have seen one report that it will hang a few scenes before the end. DRAGON'S LAIR: -Has some problems with the sound and video getting out of sync. The following was recommended to try to reduce this: Create a Dos Session with memory allocated so that it's somewhat less than you have physically in the system. Run something that's memory intensive to make sure the swap file has been allocated for the memory. Then run the fine-tuning mechanism that comes with the game. Then run the game. You might be able to run the game in future sessions without going through all this hastle. DRAGON WARS: -Runs fine (original maintainer). DRAKKEN: -One user reports that this game runs, but it crashes often with a contact your IBM rep message. Note, this was probably under the BETA of OS/2 2.1, so it MAY be fixed. (Anyone know?) DUKE NUKEM II: -Reported to run fine. DUNE II: -Reported to run fine. -One user did have a problem where it would eventually hang after first losing the Soundblaster sound, and another user also said he couldn't get the digitized sounds working correctly either. EARTHSIEGE: -Works with digitized sound, but supposedly doesn't like to play music without giving errors. One suggestion was that if you don't have generic MIDI support, configure it to use general MIDI for the music. (Apparently you HAVE to have music setup in order to have sounds). 1830: -Reported to work fine. -Allocate MORE than 4096 KB of RAM as EMs (the user set it at 4700). -Make sure SET BLASTER is defined if using SB card. ELDER SCROLLS: ARENA: -It'll supposedly work. At least, as well as it ever worked under Dos, which isn't exactly saying much. I always had problems when I cast a spell - it would crash at that point. -make sure you are running the most recent version of the program, hopefully it'll reduce the crashes. -People have reported problems getting the music to work. To be honest, I don't remember if it worked when I tried it. ELF: -According to one user, there are problems with this game. -Wasn't that specific? Anyone know more? EL-FISH: -Works with a few quirks. Will not render (animate) fish in the background. Causes a DOS session crash after exiting (But you were closing the session anyways, so isn't too serious). ELFLAND (ver 1.1): -Reported to run fine, except you can't switch away from the game (traditional screen messed up problem). EMPIRE DELUXE FOR WINDOWS: -Reported to run fine. EPIC PINBALL: -I haven't gotten this to work acceptably for me, although several people apparently have. Here's the settings one of them sent me: AUDIO_ADAPTER_SHARING: REQUIRED DOS_FILES: 40 DOS_UMB: OFF DPMI: AUTO, set at 4MB EMS: AUTO frame, set at 4MB HW_ROM_TO_RAM: ON IDLE_SENSITIVITY: 100 INT_DURING_IO: ON XGA_IOTRAP: OFF VIDEO_FAST_PASTE: OFF VIDEO_RETRACE_EMULATION: OFF VIDEO_ROM_EMULATION: OFF VIDEO_SWITCH_NOTIFICATION: OFF XMS: 4MB, 32 handles -I've tried the above, and the sound still didn't work, and it was still too slow and too jerky to play. I do know that many people are getting it to run though. -I got an opportunity to try running it over break under dos and had the same problems with sound, so it appears the sound problem might not be OS/2 related. The slow moving board does appear to be related to OS/2. ERIC THE UNREADY: -The original maintainer of the list has this to say: This game crashed about a dozen times during play. OS/2 reported several reasons for the crash, including trying to access a nonexistant FPU and trying to issue a command that's not supported by the 386 instruction set. I didn't try runnning it under a real copy of DOS booted in a VDM. I got the settings to a point where the last half of the game wend without a single crash; These settings were: COM_HOLD: ON DOS_HIGH: OFF DOS_UMB: OFF DPMI_MEMORY_LIMIT: 0 EMS_MEMORY_LIMIT: 0 HW_ROM_TO_RAM: ON HW_TIMER: ON IDLE_SECONDS: 30 IDLE_SENSITIVITY: 100 VIDEO_FASTPASTE: ON VIDEO_ONDEMAND_MEMORY: ON VIDEO_RETRACE_EMULATION: OFF VIDEO_SWITCH_NOTIFICATION: ON XMS_MEMORY_LIMIT: 0 I ran the game in regular VGA mode. Crashing seemed to happen while music was changing themes. INT_DURING_IO seemed to have no effect. The music and digitized sounds & voices worked superbly under OS/2 (except for the crashing). ETERNAM: -Reported to run fine. EYE OF THE BEHOLDER I: -Runs fine (original maintainer). EYE OF THE BEHOLDER II: -Reported to run fine. EYE OF THE BEHOLDER III: -Moving the IRQ on a SB card from 5/7 to 10 supposedly fixes a sound problem, although many games do not work with the IRQ set to 10. -I've been informed that the PAS cannot be set to IRQ 10, so this won't help those of you that have that card. -I've been told that the sound card problem is similar to what was occuring in the original release of doom, which was being cut off after a couple of minutes. This is a bug (feature?) of OS/2, which doesn't like the DMA being on for more than 2 minutes. F15: -One user said that the key disk protection caused OS/2 to generate an illegal instruction. Booting real DOS in a VDM didn't help. F15 STRIKE EAGLE 3: -Reported to run fine by several people (DOS_UMB to OFF, and give the game at least 64k XMS and several MB EMS). F17: -Reported to run fine. FALCON 3.0: -First step is to make sure you have the latest revision level. I believe this is level 'D'. -There have been several reports of a sound error when it tries to read sound.bnk (I had this error). The solution is supposedly to delete sound.bnk, then go into the CONFIG screen and reenable the sound. This will produce sound, but the voice you hear will be messed up. One person believes this to be an HPFS problem, as when he installed on a FAT partition the problem wasn't there, but when he moved it to an HPFS partition the problem occurred. -I never managed to get the game to work (I gave up). I had the sound.bnk problem, but the above solution did not work for me. FIFA INTERNATIONAL SOCCER: -Reported not to run at all. EA was not helpfull at all to try to get it to work, but said that they were testing their software under Windows 95 :P. FLIGHT SIMULATOR 5.0: -A user has reported that this program has been giving him all sorts or problems with his file system (HPFS). It's been corrupting the the desktop and OS2.INI files. The migration app apparently recognizes this program, so presumably it SHOULD work. FORGOTTEN REALMS UNLIMITED ADVENTURES (SSI): -If running with a SB type card, it runs for a while and then locks up. Turning off sound is supposed to fix this. FORMULA 1 GP: -Works, but if you add the ftp'able upgrade to add head-to-head modem support you can't do head-to-head. It supposedly won't access the modem under OS/2. FPS FOOTBALL: -Reported to run, but was a little jerky. This might be fixable by fiddling with the settings. FPS FOOTBALL PRO: -Hangs or bizzarre crashes when using the Soundblaster. Select Adlib sound by using the -A option to get by this. FPS FOOTBALL '95: -The mouse was reported to be jerkey, although another user suggested making sure HW_TIMER was on. -And another user reported the exact same problems under Dos. FRONTIER: ELITE II: -Reported to run fine. FULL THROTTLE: -Give it at least 8 megs or so of DPMI memory. -Also read the section on Dos Extenders (DOS4GW game). FUN SCHOOL TEDDY: -Reported to get randomly occuring horizontal bars. GABRIEL KNIGHT: (SIERRA) -Reported not to run at all. GALACTIX: -Reported to run fine, though the person said his joystick (a Gravis Gamepad hooked to a Soundblaster Pro port) tended to lose sync and would drift. GLOBAL DILEMMA: -One user reported the following: "Well, here's one for the 'better DOS than DOS department: I just noticed that 'Global Dilemma', which ran just fine on my Compaq 386, won't run on my new 486; the AMI Bios doesn't seem to like the way the game addresses the keyboard. That's under real DOS-5. In a DOS task under OS/2 it runs just fine." GOBLINS 2: -Whenever the game tries to play digitized sounds the system crawls and the sound gets distorted. GUNSHIP 2000: -Reported to run fine, although one use said that it would not install onto an HPFS drive. The solution is to install onto a FAT drive and copy the files to the HPFS drive. HARDBALL 4: -Reported to run fine except for sound, which may be screwed up (some people can get it to work, some can't, no idea why). HARPOON GOLD: -Reported to run fine. HARPOON II: -The installation program supposedly warns about installing under OS/2, but the game appears to run under OS/2 (Warp at least), but ONLY if it is run on a FAT file system. HERETIC: -Everything except the sound works (the usual ID software problem). HONG KONG MAHJONG: -One person said it hangs at the opponent selection screen, but he found away around the hang, but didn't report how. -You can set either XMS or EMS to 0 to prevent the game from running in SVGA mode (you'll have to check to see which it requires to do this), which gets around that hang. The game might still hang intermittantly if you play it for a while though. There's also supposedly a commandline parameter you can use to specify non SVGA mode. -Some people have reported that they can get it to work fine on some systems, but didn't have luck on others. The culprit quite possibly is the video cards. HOYLE'S BOOK OF GAMES VOL 3: -Reported to run better with VIDEO_RETRACE_EMULATION set to ON. HUMANS: -Runs fine. THE INCREDIBLE MACHINE (SIERRA): -Reported to run fine by a couple of different people. INDIANA JONES (FATE OF ATLANTIS): -Reported to run fine by several people. INDYCAR RACING: -Use DPMI memory -Problems with digitized sounds have been reported from some users. INDY 500: -Reported to run fine. IRON HELIX: -Supposedly will give a GPF when you scan for DNA. This problem might not be related to OS/2, so you can give the program a shot. JACK NICKLAUS SIGNATURE GOLF: -One user reported it runs until his sinks the ball on the first hole, at which point the entire machine freezes. -Another user responded that the game works fine for him with the sounds turned off. JET FIGHTER II: -This game is extremely ill-behaved. Apparently there are a couple of versions of this, one of which can run under memory managers. You'd need this one to have any chance. Here's the suggestions one user made: 1) JF2 uses all the video memory (A000-B7FF). Exclude all of it. 2) Disable video retrace and video emulation in DOS settings notebook. 3) Disable DPMI, XMS, EMS memory allocation. This will speed things up. 4) If you have a DX2-66, you must start the game in non-turbo mode to load. JILL OF THE JUNGLE: -Runs fine (original maintainer). -There have also been reports of the game running at much slower than normal speeds, with no success at getting it to run properly. JOURNEYMAN PROJECT: -Reported to run fine in a Win-OS/2 session. -The user who reported this said that he had to hack the installation program because it kept crashing. KING'S QUEST IV: -Reported to run fine. KING'S QUEST V: -Runs fine (original maintainer). KNIGHTS OF LEGEND: -Runs fine (original maintainer). LANDS OF LORE: -Moving the IRQ setting from 5/7 to 10 supposedly fixes a sound problem. The problem here is that many games don't work properly with an IRQ of 10. -I've been told by another user that he was able to get the sound to run fine even on normal IRQ's, but that you have to adjust the sound levels to max volume with one of the mixer tools for MMPM to be able to hear it (apparently plays very quietly). LEGENDS OF VALOUR: -Reported to run fine, although text scrolling is a little fast. -I've run this fine. LEISURE SUIT LARRY 3: -Reported to run fine. LEMMINGS (also see Lemmings 2): -It is important to have this game configured with HW_TIMER=ON, VIDEO_RETRACE_EMULATION=OFF, and to have it configured to run in a full screen session. You may have to install the game under plain DOS if you get a protection violation under OS/2 during installation. -One user reported that Lemmings wouldn't run except in a "Specific DOS" session, so give that a try if you have problems. Also, if performance suffers, or if you have flickering problems, try NOT running the game in "High Performance PC" mode. LEMMINGS 2: -This game uses a copy protection that does something that OS/2 prevents. A possibility around this is to find a crack that removes the check (although I couldn't even get it to install). -One person said that they had geoworks installed in a DOS box with the patches from ftp-os2. He then installed Lemmings 2 from the geoworks session and it worked. -Yet another person installed an ran Lemmings 2 by creating a VM boot image out of the install disk. You still have to leave the diskette in the machine, but only until the program starts up. Supposedly also works in a window this way.