[MacPorts] howto/Mame modified

[MacPorts Wiki]

Page "howto/Mame" was changed by mascguy
Diff URL: <https://trac.macports.org/wiki/howto/Mame?action=diff&version=9>
Revision 9
Comment: Updated per latest port: mame is now invoked via 'mame', rather than 'mame64'
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: howto/Mame
=========================================================================
--- howto/Mame (version: 8)
+++ howto/Mame (version: 9)
@@ -10,7 +10,7 @@
 }}}
 
 == Configuring MAME
-Once the port successfully installed, what you're going to have is an executable called `mame64`. Now, to be able to run the ROMs, we need to build the right filesystem tree in a directory. What I generally do is to create a directory in the root of my home, called, very originally, `mame`.
+Once the port successfully installed, what you're going to have is an executable called `mame`. Now, to be able to run the ROMs, we need to build the right filesystem tree in a directory. What I generally do is to create a directory in the root of my home, called, very originally, `mame`.
 
 {{{ 
 mkdir ~/mame
@@ -22,7 +22,7 @@
 cd ~/mame
 }}}
 
-and you run the `mame64` executable inside of it. MAME will run full screen and it will create a folder inside of `~/mame`  called `cfg`. That is the folder where MAME stores the configuration files. In the MAME initial dashboard you won't see much for the moment...
+and you run the `mame` executable inside of it. MAME will run full screen and it will create a folder inside of `~/mame`  called `cfg`. That is the folder where MAME stores the configuration files. In the MAME initial dashboard you won't see much for the moment...
 
 [[Image(mame-dash.png)]]
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/howto/Mame>
MacPorts <https://www.macports.org/>
Ports system for macOS

This is an automated message. Someone added your email address to be
notified of changes on 'howto/Mame' page.
If it was not you, please report to admin at macports.org.