Xmame xmamerc



Keywords: xmame xmamerc
Description: Xmame runs on both little endian and big endian CPU's, using aligned integer access if needed and is compatible with 64 bit CPU's. The current list of supported CPU's in the makefile is: i386

Xmame runs on both little endian and big endian CPU's, using aligned integer access if needed and is compatible with 64 bit CPU's. The current list of supported CPU's in the makefile is:

  • i386 + gnu-asm
  • i386 no asm
  • alpha
  • ia64 (merced)
  • m68k
  • generic risc (powerpc, sparc, hppa, ibm)
  • generic risc, lsb-first (RISC (ultrix machines))
  • mips (generic risc + SGI compiler bug workarounds)
  • Linux
  • FreeBSD
  • NetBSD
  • Solaris (SunOS)
  • OpenStep (noasm only on i386)
  • IRIX with sound using the dmedia package or the new al package (sound currently broken)
  • AIX (sound currently broken)
  • generic unix, no sound

The generic unix entry should work for any reasonable standard Unix variant, but lacks sound since there is no single Unix sound standard.

On all platforms zlib is now needed since the core uses it, if you don't have zlib use the included one by uncommenting the appropriate line in Makefile.

The following display methods are supported, X11 is the only one which works on all platforms, except for OpenStep which only work with Openstep bitmaps:

  • X11 (X-windows)
  • svgalib
  • GGI (Generic Graphics Interface)
  • OpenGL using X11 for input
  • glide using X11 for input (3DFX)
  • glide using svgalib for input (3DFX)
  • OpenStep bitmaps
  • SDL (Simple Direct Medialayer)

The following is a list of arch/os/display combinations, with maintainers, for arch/os/display combinations which are activly supported. Please mail the maintainer of the arch/os/display combination for compilation and other arch/os/display specific problems. Mail Hans hans@highrise.nl for generic (e.g. x11) problems.

We are always looking for people willing to test and answer questions about xmame on a new arch/os/display. This takes very little work and could help other people tremendously. If you're interested mail Hans hans@highrise.nl.

Xmame/xmess should run on 8bpp Pseudo Color displays and on 16, 24 and 32bpp True Color displays. If your X-Server does not support any of these display types, xmame/xmess will not run.

You can verify your X-Server support by starting your X-Server and running the xdpyinfo program. See the xdpyinfo manual page for more information.

Most of the time, you will want to use the same configuration for each game. Xmame/xmess will read this file for default values for the parameters that you can set. This way the only parameters you need to express on the command line are the ones you want to override.

Another reason for xmamerc/xmessrc is keyboard remapping. Some Unix keyboards are very different than their PC counterparts. To compensate for the changes, xmame/xmess allows you to remap keys that are not available on Unix keyboards to keys that are available.

See xmamerc.dist for most keywords. Allmost all commandline options can be used as keywords (without the -), use value 0 or 1 for commandline options which have a negating (-no[option]) counterpart. As usual lines begining with "#" are comments.

Xmame/xmess uses a ":" seperated rompath to find out which dirs to search for roms/samples.

This is overwritten by any rompath in xmamerc/xmessrc. Which can be overwritten again with the -rompath commandline option.

So lets say that we are searching for rom0001.1 which is part of pacman then xmame/xmess would search every dir in your rompath for:

Note: If your neogeo games can't find neogeo.rom put it in a dir called neogeo somewhere in your rompath, or put it in neogeo.zip somewhere in your rompath.

This section only applies to xmess emulations which support read/write diskette images and thus try to open the image read/write.

Where path is the path specified with the image on the commandline, this way absoulte and relative filenames can be used directly on the commandline for an image which is not in the rompath.

Where path is the path specified with the image on the commandline, this way absoulte and relative filenames can be used directly on the commandline for an image which is not in the rompath.

So letts say we want to play mario.nes on the nes emulation of xmess. We would then type: "xmess nes mario.nes". Xmess then begins by searching the current dir for:

Since xmess first searches for cartridges/disks from the current dir you can also specify cartridges/disks not in your rompath for example:

And will also search the rompath as described above with. /mario.nes as image name but this is not that usefull.

So lets say we want to play foo which uses bar.png. Xmame/xmess then begins searching each dir in your rompath for:

Xmame looks for the following configuration files and parses each one found, later parsed files can overwrite options in previously parsed files:

DISPLAY_METHOD is the DISPLAY_METHOD for which xmame was compiled, this can be one of: x11, svgalib, ggi, xgl, xfx, svgafx, openstep, SDL.




Photogallery Xmame xmamerc:


anti-particle.com: wah!cade quick start guide


repositories | ? Walking in Light with Christ - Faith, Computing ...


repositories | ? Walking in Light with Christ - Faith, Computing ...


MAME @ 4.1 [Forums - AmigaOS4] - The Amigans website


Retrogames ] - Your ONE STOP emulation site!


Retrogames ] - Your ONE STOP emulation site!


hip0's stuff (Security Audit Tools, Exploits, System ...


Historien om hvordan jeg laget min egen arcademaskin - Generell ...


Historien om hvordan jeg laget min egen arcademaskin - Generell ...


hip0's stuff (Security Audit Tools, Exploits, System ...


XMAME?????ARM9?!-usa9002-ChinaUnix??


Transformer un Pegasos en Media Center


Transformer un Pegasos en Media Center


Transformer un Pegasos en Media Center


????( ??? )


yang's note: 08/01/2006 - 09/01/2006


Jeux Linux