              M.A.M.E.  -  Multiple Arcade Machine Emulator
         Copyright (C) 1997  by Nicola Salmoria and the MAME team

      MAME32 Copyright (C) 1997 by Nicola Salmoria and the MAME team.

MAME32 was created by Christopher Kirmse (ckirmse@ricochet.net).  Please
do NOT send me email without first reading this entire file and
http://www.geocities.com/TimesSquare/Lair/8706/mame32.html
the home page of MAME32.

MAME32 is simple to use--put ROM files in the subdirectories specified 
in README.TXT, and run MAME32.  MAME32 requires DirectX 2.0 or higher
to be installed on your system.  If you get the error 'error loading
ddraw.dll' when you start MAME32, go to http://www.microsoft.com/directx
and download the latest DirectX runtime (version 5).

Known problems with MAME32: 

MAME32 can perform poorly under Windows NT. DirectX under NT can be very 
slow, especially sound and joysticks. You may get better performance by 
disabling sound, joysticks, or by changing video modes. Sorry, I love NT,
but its support of DirectX isn't very fast right now. 

Gorf doesn't work correctly in MAME32, but does in MAME. 

Each time you play a game, MAME32 wastes some memory. If you play dozens of 
different games without quitting and restarting MAME32, this could slow down 
your computer. If this happens, just quit MAME32 and run it again. 

Known issues in MAME32 (the facts of life): 

MAME32 runs slow in a window if your desktop is at 16 bit or 24 bit or 
32 bit color depth.  This isn't a problem, it's just a fact--moving around 
that much more video memory takes a long time.  I optimized the 16 bit color
depth version a bit, so it's about as fast as it can get. 

MAME32 runs slow in a window at 8 bit color depth if the game changes the 
palette (some of the Williams games such as Joust and Robotron, some of 
the MCR games such as Tapper, and others).  Changing the palette is slow, 
unless you play full screen. 

