Arawak OS/2 Shareware/PAKLED.ISO/docs/games20a.txt

Text File | 1993-10-29 | 33.3 KB | 1,066 lines

------------------------------------------------------------
OS2.GAMES       May 19, 1993   Version 2.0a
------------------------------------------------------------

This file provides guidelines for running various games under OS/2.
The info here has been gathered from postings to the net and from my
own experiences.  Much of the information here is incomplete, so if
anyone spots an error, or if anyone has a solution for a particular
problem, please email me and I will update this file.

---------------------------------------

GENERAL TIPS (READ THIS FIRST!):

Read the README file in your OS/2 root directory.  It has tips for
running specific 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,
email Chris Warren, the keeper of the FAQ, at [e-mail] for a
copy.

If you have trouble installing the game under OS/2 and you are trying
to install the game on an FAT drive, boot up plain DOS (via dual boot
or the Boot Manager) and install it there.  Sometimes a game (or other
apps) won't install for some reason under OS/2, but once installed
they'll work fine under OS/2.

If you experience 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.

In order to achieve maximum performance and speed, especially for graphics
intensive games such as flight simulators, try the following settings:

DOS Fullscreen:  check this option; best performance can always be
    achieved by running the game in a full screen DOS session.
DOS_BACKGROUND_EXECUTION:  OFF
    (so it won't take CPU time when you switch away from it)
DOS_HIGH: ON (more memory for those that need it)
DOS_RMSIZE: 640
DPMI_MEMORY_LIMIT: 0  (most DOS games don't use DPMI memory)
EMS_MEMORY_LIMIT: 1024  (this is EXPANDED memory.  If a game
    uses more than 1024k, use a higher number; if the game uses no
    EMS, such as Ultimas 4-5 and most of the earlier EGA games
    [SSI games, Tunnels and Trolls, Might and Magic II, Dragon
    Wars, Magic Candle I, Knights of Legend, etc.] set EMS to 0)
HW_ROM_TO_RAM: ON  (copies ROM BIOS to RAM--several people
    have said this boosts performance on their machines)
HW_TIMER: ON  (this is important, especially for those games that
    use soundboards.  However, one user noted that when this setting
    is set to ON it causes many games that send sound directly to the
    SB to crash the entire system.  I have not experienced this myself.)
IDLE_SECONDS: 10
IDLE_SENSITIVITY: 100  (this is important)
KBD_ALTHOME_BYPASS: ON  (this prevents the DOS session from
    being shrunk to a window via ALT-HOME; keep it on OFF if you
    want to run your game in a window)
VIDEO_FASTPASTE:  ON  (reported by some to boost performance)
VIDEO_RETRACE_EMULATION:  OFF  (important for fast graphics,
    though you may have to experiment with this one)
VIDEO_ROM_EMULATION: OFF
XMS_MEMORY_LIMIT:  64  (this is EXTENDED memory; when you have
    DOS_HIGH=ON, DOS can use this 64k which will help give you more
    base memory)

For best performance close ALL windows and apps (especially DOS apps) before
you run the game so that the game can get as much of the CPU as
possible.

Trying to find the right combination of DOS parameters for finicky
games is sometimes a matter of experimentation.

-----------------------------------------

SOUND CARDS:

Soundblaster: make sure that you don't have your Soundblaster set for IRQ7.
    OS/2 uses IRQ7 (which is LPT1) to print, even though DOS doesn't, so
    under OS/2 you need to change the default IRQ for your SB from 7 to
    5 (or to some other available IRQ).

Roland LAPC-1: the default IRQ2 and 330 address work fine.  IRQ2 is
    automatically mapped to IRQ9 on 386 and 486 boards.

PRO AUDIO SPECTRUM-16: be sure to set the IRQ's to something other
        than 7.  See the note under Soundblaster above.  You can load
        the PAS16's mvsound.sys by opening the DOS games program
        object icon, going into its DOS settings, and entering a line
        similar to the following in the DOS_DEVICE box:

              c:\proaudio\mvsound.sys d:3 q:2

        The path and the optional parameters will vary of course.

------------------------------------------

SPECIFIC GAMES:

Use the settings detailed above for the following games, varying EMS
as needed.  Exceptions to the above settings are noted where applicable.
I have decided to include all the games that were mentioned on the net
by OS/2 users--even if there were no problems reported--to allow those
who are thinking about buying a game to know how it runs.  A complete
list will also let people post or email additional hints when they see
their game listed.

[NOTE: "runs fine" means I've tested the game myself.  "Reported to
    run fine" means that the game was mentioned on the net as being
    compatible with OS/2.]


ACES OF THE PACIFIC:

--reported to run fine by a couple different people.
--one person made the following note:
     There's a patch out which increases screen update considerably.
     Without the patch, AotP is slightly slow on a 386/40, with the patch
     it is OK.


ALONE IN THE DARK:

--reported to run fine.  Be sure to set DOS_UMB and HW_NOSOUND to off
   and HW_TIMER to on for best sound production.


ATLANTIS:

--reported to run fine.


A-TRAIN:

--two people reported having to run the game in monochrome mode because
   if you try to run it in color it displays in a horrible monochrome
   mode anyway; and although the game was playable there was no sound.

Anybody got it to run in color?


BATTLE CHESS:

--reported to run fine.


BREACH 2:

--one user reported that he couldn't get the mouse to work, so
    he had to use the keyboard instead under OS/2.


CASTLE WOLFENSTEIN [WOLF3D]:

--this is one of the most finnicky games, and may require some
    experimentation to make it run well.  According to net reports,
    this game uses a special split-screen mode of the video card,
    and thus its behavior tends to rely on a person's hardware
    peculiarities more than OS/2 itself.  I find that I can run this
    game fine, but if I switch away from the game and then switch back
    to it the bottom portion of the screen will no longer display
    the statistics for my character.
--sometimes the special effects sounds for this game (shots, doors
    opening, people talking, etc.) will get lost after a brief
    period of time.  If this happens, create a batch file (wolf3d.bat)
    and have your program object point to the batch file.  In the
    batch file put the following two lines:
        SET BLASTER=A220 I5 D1
        WOLF3D.EXE
    The first line tells the wolf3d.exe program which address you
    are using, which IRQ you are using (in this case it's IRQ5),
    and which DMA you are using (in this case DMA1).  That should
    solve the loss of special effects sounds.  SB-Pro owners should
    add T2 or T3 to the end of the first line (check your docs for
    details).
--if you have further problems, set XMS memory to 64k.


CHUCK YEAGER'S AIR COMBAT:

--one user made the following suggestion when using the PC speaker
    for sound: Start up the game and allow it to go through the
    intro (even though the sound will just crackle).  Then after
    the intro, do a test flight and do a ^S to kill the sound.
    This will kill the sound for future sessions.  If you want
    digitized speech thereafter you can turn it on during flights
    BUT be sure to turn off the sound before you finish a mission.


CIVILIZATION (Microprose):

--Make sure you have the updated version.  It will have the "rename" button
    on the city screen.  This version performs much better under OS/2.
    If you don't have this version, you can download an update from the
    Microprose forum on CompuServe.
--Always use fullscreen mode, and when the program starts up, use vga
    resolution and ibm sound.  (ega or no sound slows it down.) If you
    want to turn off sound, do it from the options menu.
--one person reported that he could not start a new game in vga since
    he got a divide by zero error in the dos box.  But it was
    possible to load a saved game into vga mode.  Another person
    reported that he cured this divide by zero error when he set
    COM_HOLD to ON.
--another user made the following observation:

   I had been having speed problems running the game in adlib/soundblaster
   mode (and believe it or not I never tried anything else). However:
   When I ran Civilization in PC SPEAKER mode, then quit, and ran it
   again in soundblaster/adlib mode (in the same DOS session), it ran
   at the correct speed!  Since doing this on a regular basis would be
   a pain in the ass, I wanted to find another way to 'prep' the system
   for Civilization: and I found it. I ran SBFMDRV.COM (comes with the
   soundblaster) before running civilization. This way I can run Civ
   from a batch file called by a WPS icon.


COMMANCHE: MAXIMUM OVERKILL:

--this game will not run under OS/2 because it attempts to put the
   CPU into protected mode.


COMMANDER KEEN 3:

--reported to run fine.


COMMANDER KEEN 4:

--reported to run fine, with the exception that if you switch away
   from the game to the WPS and then back again the screen will get
   messed up.


CONQUERED KINGDOMS:

--one person said they could not get this game to run because the
   mouse pointer would get lost when using the game under OS/2.


CURSE OF THE AZURE BONDS:

--runs fine.


DARKLANDS:

--runs fine.  If you find the intro animation jerky, try turning your
   VIDEO_RETRACE_EMULATION to ON (normally you should set it to OFF
   for best performance).


DARKSEED:

--one person said:
   the intro will start and run OK under OS2, but then as part of the
   copy protect mechanism, the game wants to do something'illegal' on the
   A-disk'. OS2 catches the illegal instruction, and the game won't
   proceed beyond the demo.
--another person said he could get this game to run by booting real DOS
   from a boot image, but the digitized sounds needed to be turned off
   because it exhibited the same problems that Wizardry has (see
   "WIZARDRY 7").


DRAGON WARS:

--runs fine.


DRAKKHEN:

--one user reported that this game runs under OS/2, but it often
    crashes giving the "Contact your IBM rep" message.  Any
    suggestions?


DUNE II:

--reported to run fine.  One user, however, said that when he ran it
   the game would eventually hang after first losing the Soundblaster
   sound, and another user said he could not get the digitized sounds
   to work correctly either.


ELF:

--according to one user there are problems with this game.


ELFLAND (ver. 1.1):

--reported to run fine, with the exception that if you switch away
   from the game and then back to it the screen will get messed up.
   Also, according to the person who made the report on this game,
   it tends to lock up occasionally under OS/2, but that occurred
   under plain DOS as well.


ERIC THE UNREADY:

--this game crashed about a dozen times during play.  OS/2 reported
   several reasons for the crash, including trying to access
   a nonexistent fpu and trying to issue a command that's not
   supported by the 386 instruction set.  I didn't try running it
   under a real copy of DOS booted in a vdm because I wanted to
   continue to tinker with the DOS settings.  I got the settings
   to a point where the last half of the game went without a single
   crash; here were my final settings for the game:

   COM_HOLD: on (don't know if this matters or not)
   DOS_HIGH: off
   DOS_UMB: off
   DPMI_MEMORY_LIMIT: 0
   EMS_MEMORY_LIMIT: 0 (this game doesn't use any)
   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.  It has svga (VESA) capability,
   but that just makes the pictures smaller, so I didn't use it.  As
   far as the crashing goes, it seemed to do it when the music changed
   themes or when the music started a song over again.  I tried turning
   INT_DURING_IO to ON but it made no difference.  I have an LAPC-1
   on IRQ2 and a Soundblaster at IRQ5.  BTW, this game has the BEST
   music I've ever heard--tons of different songs... some of them
   written for just one scene in the game!  And the Soundblaster
   digitized voices and digitized sounds worked superbly under OS/2.


ETERNAM:

--reported to run fine.


EYE OF THE BEHOLDER I:

--runs fine.


EYE OF THE BEHOLDER II:

--reported to run fine.


F15:

--one person said that he could not get this game to run at all.  It
  either gave him an illegal instruction @$c, or failed to run when
  trying to read the keydisk.  He even tried loading DOS 5.0 and
  DR DOS 6.0 in a vdm, but it still did not work.


F15 STRIKE EAGLE 3:

--reported to run fine by several people (make sure that DOS_UMB is
   set to off, and try giving the game at least 64k XMS and several
   MB EMS).


F17:

--reported to run fine.


FALCON 3.0:

--several patches have been put out for this game.  I believe that there
    have been four, with patch 'd' being the latest and the one which
    lets the soundblaster work the best.  Check comp.sys.ibm.pc.games
    for details.  One person said that the mission disk (Operation
        Flying Tiger) also has a patch available that fixes minor problems.
--one user reported that he needed to have the HW_TIMER set to OFF or
    the game hung.  But when he set it to OFF the screen updates were
    excruciatingly slow.

--there have been several reports of an error when the program tries
  to read the file sound.bnk.  The solution seems to be to delete (or
  rename) sound.bnk, then go into the CONFIG screen and reenable the
  sound.  This will produce sound, but the voice you hear over the
  radio will not work correctly.  One person emailed me about this
  problem to say that he thinks it is HPFS related; when he installed
  the game on an FAT partition the problem wasn't there, but when he
  moved the game to an HFPS partition the problem came back.  He said
  he was unable to get the voices to work.



FPS FOOTBALL:

--reported to run fine, though a bit jerky [user said he needed to
   fine tune the settings though].


GALACTIX:

--reported to run fine, though the person said his joystick (a Gravis
   Gamepad hooked to Soundblaster Pro port) tended to lose sync and
   would drift.


GLOBAL DILEMMA:

--one user made the following observation:

   Well, here's one for the "better DOS than DOS" department: I just
   noticed that "Global Dilemma" (or Guns & Butter), 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.


GUNSHIP 2000:

--reported to run fine.
--one user reported that the game would not install onto an HPFS
    drive.  He was able to install it onto a FAT drive, though.
    He could run the game on an HPFS drive if he copied the
    installed files from his FAT drive to his HPFS drive.


HARPOON GOLD:

--reported to run fine.


HONG KONG MAHJONG:

--one person said it hangs at the opponent selection screen, but he
   found a way to get around this (but he didn't mention how).


HUMANS:

--reported to run fine (be sure to set IDLE_SENSITIVITY to 100).


THE INCREDIBLE MACHINE (SIERRA):

--reported to run fine by a couple different people.


INDIANA JONES (FATE OF ATLANTIS):

--reported to run fine by several people.


INDY 500:

--reported to run fine.


JACK NICKLAUS SIGNATURE GOLF:

--one user reported that he could only run this game to the point that
    he sunk the ball in the first hole, at which point the entire
    machine (not just the game) would freeze forcing a reset (cold
    boot).
--another user responded that the game works fine for him with the
    sounds turned off.


JET FIGHTER II:

--this game is extremely ill-behaved.  According to numerous reports it
   will not run under OS/2, but there is a later version that allows
   itself to be run under memory managers (such as QEMM).  I have
   had a number of people email me telling me they couldn't get it
   to run, but one person said the following in response to a
   statement that the game would not run under OS/2:

     Yes, it runs--for me a least. JFII is the absolutly most finicky
     game I've run across.
   1) JFII uses all the video memory (A000-B7FF). Exclude this if necessary.
   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 game in non-turbo mode to load.


JILL OF THE JUNGLE:

--runs fine.


KING'S QUEST IV:

--reported to run fine.  One person said that for him the keyboard
   buffer would eventually fill up and he couldn't clear it while
   running this game, but I never experience that.


KING'S QUEST V:

--runs fine.


KNIGHTS OF LEGEND:

--runs fine.


LEISURE SUIT LARRY 5:

--one person asked the net how to get this game to run under OS/2;
   no one answered him.  Any more info?


LEMMINGS (see next entry for 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 also have to install the game under plain DOS if you get a protection
violation under OS/2 during installation (even though it will run under OS/2
after installation).

One user reported that Lemmings wouldn't run except in a "Specific DOS"
session, so if you have troubles try that.  Also, if performance suffers,
or if you have flickering problems, try NOT running the game in "High
Performance PC" mode.


LEMMINGS 2:

--There have been a number of reports that say this game uses some
   type of copy protection that looks either at the boot sector of
   the hard drive, or looks at the bios, and OS/2 kills its attempt
   to do this.
--One person responded to the paragraph above and said:
     I have a friend who installed it and is running it under OS/2.
     Kind of.  He installed geoworks in a DOS box and the patches
     from hobbes.  He then installed Lemmings from the geoworks
     session(stilling running OS/2) and it worked!  I know he was
     not dual booted because I hit alt-esc and it popped me out to
     the desktop.
--Another poster said:
     I installed and run Lemmings 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.  I can even run it in a window.



LINKS:

--one user posted this helpful notice:

   I have adjusted my Links settings and think that I have the best
   solution for running LINKS under OS/2 2.0.  First, Migrate it to
   the DOS File.  Next, instead of executing the file LINKS.BAT, use
   the SETTINGS to have it run GOLF.EXE with NO optional parameters
   (the /t in LINKS.BAT appears to be for the title screen).  As soon
   as the program starts, select SYSTEM and turn off ALL sounds.  This
   last step will alleviate the slow down immediately after the swing
   as Links tries to create the sound even if HW_SOUND is turned off.
   I also have HW_NO_SOUND set to ON and MOUSE_EXCLUSIVE_ACCESS turned ON.
   This seems to have the game working quite well for me in full screen
   mode.  I hope that it helps others.

--another user said that the game works fine for him in a full screen
    DOS session with full sounds without having to do any of the
    above.


LINKS 386 PRO:

--according to several users there are problems running this game
    under OS/2.  One user called Access Software (1-800-793-8324)
    and was told that a fix would be put out if there was enough
    interest.
--one user said he could play the game by booting DOS in a vdm, but
    the game soon gave an insufficient swap space message and
    eventually dumped him back to the DOS prompt.  Apparently the
    game uses its own swap file that doesn't run correctly under
    OS/2.
--another user said it runs for him under OS/2 ok, but with the
        following problems: it plays too fast (timing is important,
        so it's harder to play under OS/2), there are occasional
        lockups, and Soundblaster digitized sound will only play
        the first one or two seconds of a given sound.
--one person emailed me and said that the game uses DPMI memory,
        and that was the cause of insufficient memory that people
        were experiencing.  He said to set DPMI_MEMORY_LIMIT to
        16 MB and you should have no problems.


LOST ADMIRAL:

--one person noted that this game (and other QQP games) will lose the
   mouse pointer under OS/2.


MAGIC CANDLE I:

--runs fine.


MAGIC CANDLE II:

--runs fine in full screen, but you cannot switch away from the session
        and then back to it without getting screen distortion.  Be sure
        you have the updated version that has the mouse driver in it
        for best performance (a sound blaster/Roland board combination
        will not work otherwise).


MARTIAN DREAMS:

--reported to run fine.


MIGHT AND MAGIC II:

--runs fine.  If you have trouble with the keydisk being recognized,
    boot up real DOS in a vdm (see VMDISK in the Command Reference
    for directions on how to do this).


MIGHT AND MAGIC III:

--runs fine with the exception that the digitized intro speech by
    Sheltem at the beginning of the game and another speech toward
        the end of the game will not work with a Soundblaster under
        OS/2.
--this game runs faster under OS/2 than under plain DOS due to OS/2's
    super-FAT and HPFS.


MIGHT AND MAGIC IV:

--runs fine in a full screen vdm.


MONKEY ISLAND II:

--one user posted the following observation:

   After intensive study and exhaustive analysis ( :) ) I have
   finally determined a solution to the problem I've been having.
   The problem was that The Secret of Monkey Island 2 would not play
   music correctly on the sound blaster under OS/2.  I asked several
   people for help in reconfiguring my Sound Blaster, and I thank
   you all for your help, but that wasn't the problem.  The new wave
   of LucasFilm games has implemented a new music system they call
   iMUSE.  It turned out in my case that the iMUSE driver I had for
   the sound blaster was out of date or something, I'm not sure.  But
   I copied the SOUNBLAS.IMS file from my copy of Indy 4 into my
   Monkey Island 2 directory.  Now, no problems.  It may be a hack
   solution, but it works now, and I'm waiting for LucasFilm to call
   me back.

    This person then followed up:

   I got a call back from LucasFilm Games about my Monkey Island II
   question about sound, and they'll be sending me a disk with new
   *.IMS files.  I'm going to ask permission to post them onto the
   net somewhere, but these should solve all sound problems with the
   game.


NOVA 9:

--reported to run fine.


OUT OF THIS WORLD:

--one user reported the following:

   Out of this World will run under OS/2 if HW_TIMER is set OFF,
   not ON as many other games have required.  Also, it requests
   that you do not use an expanded memory manager, so setting
   EMS_MEM_LIMIT 0.  I have found that this combination is extremely
   slow with any sound support, and so I have been playing it without
   sound.


PACIFIC WAR:

--reported to run fine.


PATRIOT:

--reported to run fine.


PERFECT GENERAL:

--one user reported that this game (and other QQP games) will lose
   its mouse pointer when run under OS/2.  Another user emailed me
   to say that he never had this problem when he played Perfect
   General under OS/2.


POOL OF RADIANCE:

--runs fine.


PRINCE OF PERSIA:

--reported to run fine.


QIX:

--one user posted a note saying that he had problems running this
    game under OS/2.  He gave no specifics.


RED BARON (Dynamix):

--this game runs fine, but two users observed that although RB's music
    played OK for them, the sound effects (such as guns and engine
    noise) were silent.  The cure for this is simply to run Red
    Baron's install program (with RB already installed) and choose
    the appropriate options again to make them take effect.
--Although I have had no problems running RB with my Soundblaster and
    with my Roland LAPC-1, another user noted the following:

   At least on my machine (486, 8 Megs and Soundblaster Pro) this program
   locks up if you set the sound option to Sound Blaster; however if
   you set the option to Adlib, you still get digitized sound and the
   program runs fine.
--this game will NOT run in a window.  You should run it in full screen
    mode only.


RINGWORLD:

--reported to run fine.


SCORCHED EARTH (ver. 1.1 and 1.2):

--reported to run fine, with the exception that the screen will get
   messed up if you switch away from the game and then back to it.
   The game has a screen redraw option that fixes it each time though.


SECRET OF THE SILVER BLADES:

--runs fine.


SECRET WEAPONS OF THE LUFTWAFFE:

--reported to run fine.


SHANGHAI II: DRAGON'S EYE:

--reported to run fine in a full-screen session.


SHERLOCK HOLMES (CD GAMES):

--one user said that this game (games?) could not be played under OS/2.


SIEGE:

--reported to run fine: be sure to set the HW_TIMER to ON.


SIMCITY:

--reported to run fine; if you want to run it in a window, be sure
    to turn MOUSE_EXCLUSIVE_ACCESS to ON.


SIMEARTH:

--reported to run fine by several users.


SOLITAIRE'S JOURNEY:

--one user reported that he had trouble getting the mouse cursor to
    work correctly under OS/2.  It would leave black blocks on the
    screen or extra mouse cursor images.


SPACE QUEST IV:

--runs fine, with the exception that some of the digitized sounds
    on the soundblaster may be cut short.  For example, I noticed
    that the lightning sounded fine when I was far away from it,
    but when I drew near the sound of the thunder would be cut
    short (this is on a 386/33 with Roland music and SB speech).
--one person emailed me and said that OS/2 comes with a fix for this
        game, called SQ4FIX.COM, but he didn't know what it did.
        [I haven't tried it myself yet.]


SPEAR OF DESTINY:

--one user emailed me to say that this game would just start and
   then hang the DOS box.


SPECTRE:

--reported to run fine.


SPELLCASTING 101 and 201:

--reported to run fine.


STAR CONTROL 2:

--one person said that this game causes intermittent crashes, and
   one crash even trashed his save file causing him to start over
   again.
--another person emailed me in response to what the person above said,
   and he said that he played and completed the game without any
   crashes or glitches; he said he had no sound board and set the
   battle to "Cyborg".


STAR TREK: 25th ANNIVERSARY:

--reported to run fine.


STELLAR 7:

--reported to run fine.  One user however could not get the game to
    run using his Soundblaster, and he was informed that Stellar 7
    is hard coded to use IRQ7 (which conflicts with OS/2's use of
    LPT1 at that IRQ).


STUNT ISLAND:

--three users reported problems trying to get this game to run under
   OS/2.  One of them said it hung on him during the intro; another
   said it would eventually crash while playing the game.  But another
   user responded with "I've played Stunt Island ALOT without it ever
   crashing."


STUNTS [Broderbund]:

--reported to run fine both full screen and windowed.


SUPER JEOPARDY:

--one person posted a message saying he had trouble with the timer in
   the game.  He set the clock for 20 minute rounds but they only
   lasted about 5 minutes.  [any other experiences?]


SVGA AIR WARRIOR:

--one user reported that this game will not run under OS/2 because
   it attempts to put the cpu in protected mode.


TASK FORCE 1942:

--reported to run fine.


TERMINATOR 2029:

--one user reported problems trying to get this game to run under OS/2.
   Another user was more explicit: it gave him an illegal instruction
   message when he tried to run it, and when he called Bethesda Soft-
   works the rep there said it would not run under OS/2.


TEST DRIVE 3:

--reported to run fine.


TRISTAN PINBALL:

--one person said that when he tries to run this game it randomly
   crashes, sometimes to the point of rebooting.


TUNNELS AND TROLLS:

--runs fine.


ULTIMAS 4 and 5:

--if you have trouble with the keydisks for these games being recognized,
    boot a real copy of DOS in a vdm (see VMDISK in the Command
    Reference for details).


ULTIMA 6:

--runs fine.


ULTIMA 7:

--this game will NOT run under OS/2 since it uses its own memory manager.
    No amount of tweaking will make it run, so don't waste your time.
    Instead, spend the time to write Origin and tell them to patch it!


ULTIMA UNDERWORLD:

--there is a patch that fixes many inventory bugs in this game.  Check
    comp.sys.ibm.pc.games for more details.
--this game will not run in a window since it will be distorted.
--the digitized intro speeches for this game will not work reliably
    under OS/2 with a Soundblaster; this is the only time in the
    game where there is digitized speech though.  To READ the
    intro speeches, configure the game for no sound (or PC speaker)
    and then run the intro.
--some people report no problems with this game, other people can't get
    it to run under OS/2 at all.  Most people are able to run the game
    if they start the game in one of the following two ways:

   1)  Set the game to start minimized with background execution OFF.
    Start the game and WAIT until all disk activity stops (about 10-15
    seconds on my 386/33).  Then switch to the game.  This works best
    for me, and allows me to switch back and forth from the game safely.
    I've never had the game crash on me doing it this way, and I've
    switched back and forth from my word processor hundreds and
    hundreds of times.
   2)  Set the game to start in a windowed DOS session.  The game will look
    garbled, but wait until you see the blue title screen come up.  Then
    switch the game to full screen mode with ALT-HOME.  If the keyboard
    doesn't respond after doing this, tap the ALT key to unstick it.


ULTIMA UNDERWORLD II:

--see "ULTIMA UNDERWORLD" above if you have problems starting/running
   this game.
--the new digitized sounds in this game will not work reliably under
   OS/2.  You will hear the sounds for 5-30 seconds or so, and
   then they'll stop.  Going into the sound option in the game
   and turning the sound off and on will make them come back on
   again, but they won't stay on.  All the sound files are simple
   .voc files located in the \uw2\sound directory and may be
   heard with any .voc player.  Those with Roland cards will
   be able to hear the nondigitized versions of the sounds under
   OS/2 without problems.


V FOR VICTORY ("UTAH BEACH"):

--reported to run fine.


VELIKIYE LUKI:

--reported to run fine by two different people, one of whom said
   it ran fine on his 486 with Soundblaster Pro, while the other
   said it ran very fast even on his 386
--one user posted a message saying that he couldn't get it to run
   under OS/2 because it would generate an illegal instruction.


WAYNE GRETZKY HOCKEY 3:

--two people posted messages to say they could not get the game to
   run under OS/2.  [any other experiences?]


WELLTRIS:

--reported to run fine in a full screen session.


WHEEL OF FORTUNE:

--reported to run fine.


WHERE IN THE WORLD IS CARMEN SAN DIEGO:

--reported to run fine.


WING COMMADER I-II (and SM1-2, SO1):

--these run fine, even with the speech pack.
--I have found that in WCII my soundblaster's digitized voices in
    battle often hang causing me to have to hit ESC to "unstick"
    them.  This happens only when there are lots of enemy ships
    in the area.  I have a 386/33; testing it on a 486/33 didn't
    exhibit this problem.


WINTREK (for Windows):

--one user reported that this game doesn't work under Win-OS2 because
    it requires Win 3.1.


WIZARDRY 7:

--reported to run fine, with the exception that the digitized sounds
   will give problems and cause the game to slow down to a crawl at
   points (several people have made this observation).  The only
   solution seems to be to disable the sound.  One person observed
   that you don't need the sound to enjoy the game; another person
   said he decided to just play it under plain DOS because he felt
   the digitized sounds added a lot.
--Sir-Tech and IBM have been talking over the problem with the
   Soundblaster sound in the latest Wizardry game (Dark Savant).
   We called Sir-Tech's support line and were told that Sir-Tech
   is working on the problem and will send out information (possibly
   a patch?!) to people who call and request that their names be put
   on the mailing list...  So call Sir-Tech's tech support line at
   315-393-6644 (9-5 PM EST) and tell them you're running the game
   under OS/2 and you want it fixed!


WOLF3D:

[listed under "Castle Wolfenstein"]


WONDERLAND:

--runs fine.


WORLD WRESTLING FEDERATION:

--according to one user there were problems with this game.


X-WING

--reported to run fine by several people.


------------------------------------------------

Note: I may not be reachable after May 20, 1993, since I am losing
this account.  If you email me and it bounces, please post your questions
or revisions in comp.sys.ibm.pc.games or comp.os.os2.misc.  I will
probably see the post and add your comments to the file, or if someone
else is updating this file they will probably see your post.

   Steve Smith       | __|__ |    " #*&<-[89s]*(k#$@-_=//a2$]'+=.(2_&*%>,,@
<[e-mail]. |   |   |      {7%*@,..":27g)-=,#*:.#,/6&1*.4-,l@#9:-) "
  ohio-state.edu>    |   |   |
  BTW, WYSInaWYG     |   |   |                           --witty.saying.ARC