MAME:Installing - Revision history

Johnnyo: /* Continuous Integration MAME Builds */ an attempt for the better text "flow"

2026-04-23T09:36:46Z

Continuous Integration MAME Builds: an attempt for the better text "flow"

← Older revision		Revision as of 10:36, 23 April 2026
Line 160:		Line 160:
	Continuous Integration (CI) builds are available from both the [https://github.com/mamedev/mame/actions primary MAME repo] and [https://github.com/holub/mame/actions holub's GitHub repo]. Both are considered bleeding-edge, with the primary MAME repo slightly less so. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.		Continuous Integration (CI) builds are available from both the [https://github.com/mamedev/mame/actions primary MAME repo] and [https://github.com/holub/mame/actions holub's GitHub repo]. Both are considered bleeding-edge, with the primary MAME repo slightly less so. MAME CI builds are available for Windows, Linux, and macOS and are updated automatically whenever code is committed by a maintainer or pushed to the primary repo.

	~~To try out a~~ CI ~~build (more precisely~~, ~~the resulting binary executable, which is a produced "artifact" of the build process) , first do a full MAME install from the~~ [https://~~www.mamedev~~.~~org~~/~~release.html latest release~~] ~~if you have not already done so. Then back up your main binary from its installation location - these are called something like <code>mame.exe<~~/~~code> or <code>mame<~~/~~code>~~. ~~You can always restore these if the CI build doesn't work, or if you don't like how it behaves~~.		'''You need to be logged in to github''' to download CI artifacts, so [https://github.com/login sign in] or [https://github.com/signup sign up].

	~~'''You need to be logged in to github''' to download~~ CI ~~artifacts~~, so [https://~~github~~.~~com~~/~~login sign in~~] or ~~[https:/~~/~~github~~.~~com/signup sign~~ up].		To try out a CI build (more precisely, the resulting binary executable, which is a produced "artifact" of the build process) , first do a full MAME install from the [https://www.mamedev.org/release.html latest release] if you have not already done so. Then back up your main binary from its installation location - these are called something like <code>mame.exe</code> or <code>mame</code>. You're backing it up to be able to restore it if the CI build doesn't work, or if you don't like how the CI build behaves.

	Then visit one of the links above and find a workflow run item for your platform. Workflow items are the things in the list. The tags are flagged as <code>CI (Windows)</code>, <code>CI (Linux)</code>, or <code>CI (macOS)</code> in the second row of each workflow item in the list (not the filter in the left hand nav menu). Click on a completed workfow item (only items with green checkmarks will have created downloadable binaries yet), find the Artifacts section at the bottom, then click the Download button. Unzip the downloaded file and find the main binary (with the same name as above). Copy the main binary to the install location, overwriting the original one, and run MAME the same way you were running it before. On Windows and macOS, you need to repeat the security steps above to trust the new MAME executable.		Then visit one of the links above and find a workflow run item for your platform. Workflow items are the things in the list. The tags are flagged as <code>CI (Windows)</code>, <code>CI (Linux)</code>, or <code>CI (macOS)</code> in the second row of each workflow item in the list (not the filter in the left hand nav menu). Click on a completed workfow item (only items with green checkmarks will have created downloadable binaries yet), find the Artifacts section at the bottom (note again: you need to be signed up to see that section and/or download the artifact), then click the Download button. Unzip the downloaded file and find the main binary (with the same name as above). Copy the main binary to the install location, overwriting the original one, and run MAME the same way you were running it before. On Windows and macOS, you need to repeat the security steps above to trust the new MAME executable.

	= More MAME related links =		= More MAME related links =

Ped7g: fix urls to specnext.cpp

2026-04-22T22:12:51Z

fix urls to specnext.cpp

← Older revision		Revision as of 23:12, 22 April 2026
Line 19:		Line 19:
	Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].		Alternatively, for the MAME platform as a whole, you can also check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].

	Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/] [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/specnext.cpp specnext.cpp]		Git of official MAME: [https://github.com/mamedev/mame/ https://github.com/mamedev/mame/] [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp]

	Git of holub's fork: [https://github.com/holub/mame https://github.com/holub/mame] [https://github.com/holub/mame/blob/master/src/mame/sinclair/specnext.cpp specnext.cpp] (may contain extra fixes and features before they are merged to official repository)		Git of holub's fork: [https://github.com/holub/mame https://github.com/holub/mame] [https://github.com/holub/mame/blob/master/src/mame/sinclair/next/specnext.cpp specnext.cpp] (may contain extra fixes and features before they are merged to official repository)

	=== 2. Get TBBLUE (the Next 'boot ROM') ===		=== 2. Get TBBLUE (the Next 'boot ROM') ===

Luzie at 17:49, 24 January 2026

2026-01-24T17:49:25Z

← Older revision		Revision as of 18:49, 24 January 2026
Line 174:		Line 174:
	For '''Linux''' users there are more tips (how to compile MAME from source, how to configure it to not use CWD as starting path for resource directories, how to mount or create image file) at [[Development_Tools:Linux_setup]] page.		For '''Linux''' users there are more tips (how to compile MAME from source, how to configure it to not use CWD as starting path for resource directories, how to mount or create image file) at [[Development_Tools:Linux_setup]] page.

	~~MAME Stable Controller IDs~~ [https://docs.mamedev.org/advanced/devicemap.html MAMEDEV.ORG MAME Stable Controller IDs].		[https://docs.mamedev.org/advanced/devicemap.html MAMEDEV.ORG MAME Stable Controller IDs].
	By default, MAME does not assign stable numbers to input devices. For instance, a game pad controller may be assigned to “Joy 1” initially, but after restarting, the same game pad may be reassigned to “Joy 3”.		By default, MAME does not assign stable numbers to input devices. For instance, a game pad controller may be assigned to “Joy 1” initially, but after restarting, the same game pad may be reassigned to “Joy 3”.
	Here a some hints how to fixate MAME´s Joystick-Detection to specific Controllers~~: Youtube "MAME - Mapping your controllers for stable IDs"~~: [https://www.youtube.com/watch?v=YmjfwLuZ_X0 Youtube]		Here a some hints how to fixate MAME´s Joystick-Detection to specific Controllers: [https://www.youtube.com/watch?v=YmjfwLuZ_X0 Youtube - Mapping your controllers for stable IDs]
	and [https://forums.launchbox-app.com/topic/89296-stable-controller-ids-for-mame/ Stable Controller IDs for MAME]		and: [https://forums.launchbox-app.com/topic/89296-stable-controller-ids-for-mame/ Stable Controller IDs for MAME]

Luzie: Addded Internet-Links for Infos on "Stable Controller IDs for MAME"

2026-01-24T17:39:43Z

Addded Internet-Links for Infos on "Stable Controller IDs for MAME"

← Older revision		Revision as of 18:39, 24 January 2026
Line 173:		Line 173:

	For '''Linux''' users there are more tips (how to compile MAME from source, how to configure it to not use CWD as starting path for resource directories, how to mount or create image file) at [[Development_Tools:Linux_setup]] page.		For '''Linux''' users there are more tips (how to compile MAME from source, how to configure it to not use CWD as starting path for resource directories, how to mount or create image file) at [[Development_Tools:Linux_setup]] page.

			MAME Stable Controller IDs [https://docs.mamedev.org/advanced/devicemap.html MAMEDEV.ORG MAME Stable Controller IDs].
			By default, MAME does not assign stable numbers to input devices. For instance, a game pad controller may be assigned to “Joy 1” initially, but after restarting, the same game pad may be reassigned to “Joy 3”.
			Here a some hints how to fixate MAME´s Joystick-Detection to specific Controllers: Youtube "MAME - Mapping your controllers for stable IDs": [https://www.youtube.com/watch?v=YmjfwLuZ_X0 Youtube]
			and [https://forums.launchbox-app.com/topic/89296-stable-controller-ids-for-mame/ Stable Controller IDs for MAME]

Johnnyo: /* 3. Get the NextZXOS Image */ rearranging words

2026-01-24T13:26:56Z

3. Get the NextZXOS Image: rearranging words

← Older revision		Revision as of 14:26, 24 January 2026
Line 29:		Line 29:

	=== 3. Get the NextZXOS Image ===		=== 3. Get the NextZXOS Image ===
	Get an SD card image file of [https://www.specnext.com/latestdistro/ NextZXOS]. Note that '''~~currently~~ some ~~published~~ disk images on the official SpecNext.com site do not work with some emulators''' (the <code>latestdistro</code> link points to the official location where the latest distribution can be found), but '''all images from <code>https://zxnext.uk/hosted/</code> work with both MAME and CSpect''', like [https://zxnext.uk/hosted/index_files/hdfimages/cspect-next-2gb.zip this SD card image in the zip archive]. Extract the image <code>cspect-next-2gb.img</code> from the archive to use it, then point MAME to this SD card image with the <code>-hard1</code> option (or select that file from the menu inside MAME).		Get an SD card image file of [https://www.specnext.com/latestdistro/ NextZXOS]. Note that '''some disk images published on the official SpecNext.com site do not work with some emulators currently''' (the <code>latestdistro</code> link points to the official location where the latest distribution can be found), but '''all images from <code>https://zxnext.uk/hosted/</code> work with both MAME and CSpect''', like [https://zxnext.uk/hosted/index_files/hdfimages/cspect-next-2gb.zip this SD card image in the zip archive]. Extract the image <code>cspect-next-2gb.img</code> from the archive to use it, then point MAME to this SD card image with the <code>-hard1</code> option (or select that file from the menu inside MAME).

	= Usage =		= Usage =

Johnnyo: /* Creating and manipulating NextZXOS SD card image */ refer to zxnext.uk/hosted here too

2026-01-23T18:16:54Z

Creating and manipulating NextZXOS SD card image: refer to zxnext.uk/hosted here too

← Older revision		Revision as of 19:16, 23 January 2026
Line 125:		Line 125:
	= Creating and manipulating NextZXOS SD card image =		= Creating and manipulating NextZXOS SD card image =

	Most users wanting to emulate the Next using MAME will be fine using a pre-built SD card image downloaded from the ~~specnext~~ website. The following guide is provided for anyone wanting to create a NextZXOS SD card image from scratch.		Most users wanting to emulate the Next using MAME will be fine using a pre-built SD card image downloaded from the site hosting best pre-made images (currently, [https://zxnext.uk/hosted zxnext.uk/hosted] ) website. The following guide is provided for anyone wanting to create a NextZXOS SD card image from scratch.

	Download the [https://www.specnext.com/latestdistro/ latest NextZXOS distribution zip file] (named something like sn-complete-WX.YZ.zip) and extract it into a new, empty directory.		Download the [https://www.specnext.com/latestdistro/ latest NextZXOS distribution zip file] (named something like sn-complete-WX.YZ.zip) and extract it into a new, empty directory.

Johnnyo: /* 3. Get the NextZXOS Image */ emphasis to what works

2026-01-23T18:12:02Z

3. Get the NextZXOS Image: emphasis to what works

← Older revision		Revision as of 19:12, 23 January 2026
Line 29:		Line 29:

	=== 3. Get the NextZXOS Image ===		=== 3. Get the NextZXOS Image ===
	Get an SD card image file of [https://www.specnext.com/latestdistro/ NextZXOS]. Note that currently some published disk images on the official SpecNext.com site (the <code>latestdistro</code> link points to the official location where the latest distribution can be found) ~~do not work with some emulators~~, but all images from <code>https://zxnext.uk/hosted/</code> work with both MAME and CSpect, like [https://zxnext.uk/hosted/index_files/hdfimages/cspect-next-2gb.zip this SD card image in the zip archive]. Extract the image <code>cspect-next-2gb.img</code> from the archive to use it, then point MAME to this SD card image with the <code>-hard1</code> option (or select that file from the menu inside MAME).		Get an SD card image file of [https://www.specnext.com/latestdistro/ NextZXOS]. Note that '''currently some published disk images on the official SpecNext.com site do not work with some emulators''' (the <code>latestdistro</code> link points to the official location where the latest distribution can be found), but '''all images from <code>https://zxnext.uk/hosted/</code> work with both MAME and CSpect''', like [https://zxnext.uk/hosted/index_files/hdfimages/cspect-next-2gb.zip this SD card image in the zip archive]. Extract the image <code>cspect-next-2gb.img</code> from the archive to use it, then point MAME to this SD card image with the <code>-hard1</code> option (or select that file from the menu inside MAME).

	= Usage =		= Usage =

Ped7g: Moving Linux related mounting details to dev tools page, making this article simpler and less technical (especially for Win/Mac users)

2026-01-21T16:55:33Z

Moving Linux related mounting details to dev tools page, making this article simpler and less technical (especially for Win/Mac users)

@@ Line 123: / Line 123: @@
 * Return to the previous menu twice, then choose Save Settings
-= Creating a NextZXOS SD card image =
+= Creating and manipulating NextZXOS SD card image =
 Most users wanting to emulate the Next using MAME will be fine using a pre-built SD card image downloaded from the specnext website. The following guide is provided for anyone wanting to create a NextZXOS SD card image from scratch.
@@ Line 131: / Line 131: @@
 == Creating and populating a SD card image using hdfmonkey jjjs build ==
-The [[https://www.specnext.com/forum/viewtopic.php?t=2604 | <code>hdfmonkey "jjjs build"</code>]] is a variant of hdfmonkey tool which includes some unique features and its main archive (at the previously given link) also contains pre-built binaries for Windows x64, MacOS x64, MacOS Apple Silicon and Linux x64. (Alternatively, the process to build a local Linux version of the executable is described [[Development_Tools:Linux_setup#Building_the_executable_binary_2 | here]] )
+The [https://www.specnext.com/forum/viewtopic.php?t=2604 hdfmonkey "jjjs build"] is a variant of hdfmonkey tool which includes some unique features and its main archive (at the previously given link) also contains pre-built binaries for Windows x64, MacOS x64, MacOS Apple Silicon and Linux x64. (Alternatively, the process to build a local Linux version of the executable is described [[Development_Tools:Linux_setup#hdfmonkey_tool | here]] )
 If you extracted sn-complete-WX.YZ.zip into a subdirectory named <code>snWXYZ</code>, and you want to create a 1GB image called <code>NextZXOS.img</code> and you have a jjjs build" of hdfmonkey, then it's enough to do:
@@ Line 149: / Line 149: @@
 The most convenient tool to copy of all the content from the image to a folder outside of the image is 7-zip. On Windows, just use the 7-zip GUI. On MacOS and Linux, see: [[Development_Tools:Linux_setup#Extracting_all_files_from_the_sd-card_image]].
 =MAME Plugins and Scripts=
@@ Line 215: / Line 166: @@
 Then visit one of the links above and find a workflow run item for your platform. Workflow items are the things in the list. The tags are flagged as <code>CI (Windows)</code>, <code>CI (Linux)</code>, or <code>CI (macOS)</code> in the second row of each workflow item in the list (not the filter in the left hand nav menu). Click on a completed workfow item (only items with green checkmarks will have created downloadable binaries yet), find the Artifacts section at the bottom, then click the Download button. Unzip the downloaded file and find the main binary (with the same name as above). Copy the main binary to the install location, overwriting the original one, and run MAME the same way you were running it before. On Windows and macOS, you need to repeat the security steps above to trust the new MAME executable.
-= More MAME links =
+= More MAME related links =
 MAME [https://docs.mamedev.org/ documentation].
 Report any issues with MAME on the [https://mametesters.org/ bugtracker].

Ped7g: change url anchor to follow edits

2025-12-22T20:09:04Z

change url anchor to follow edits

← Older revision		Revision as of 21:09, 22 December 2025
Line 148:		Line 148:
	The fastest way to transfer a file or a directory (including its content, recursively) into an image is by using a single <code>put</code> (or <code>putdir</code>, if it's to transfer the directory file content to an existing directory) command of hdfmonkey.		The fastest way to transfer a file or a directory (including its content, recursively) into an image is by using a single <code>put</code> (or <code>putdir</code>, if it's to transfer the directory file content to an existing directory) command of hdfmonkey.

	The most convenient tool to copy of all the content from the image to a folder outside of the image is 7-zip. On Windows, just use the 7-zip GUI. On MacOS and Linux, see: [[Development_Tools:Linux_setup#~~Extracting_all_files_from_the_SD_image~~]].		The most convenient tool to copy of all the content from the image to a folder outside of the image is 7-zip. On Windows, just use the 7-zip GUI. On MacOS and Linux, see: [[Development_Tools:Linux_setup#Extracting_all_files_from_the_sd-card_image]].

	== Creating and populating a SD card image using Linux ==		== Creating and populating a SD card image using Linux ==

Ped7g: Adding url to MAME docs with default keys

2025-12-22T01:50:11Z

Adding url to MAME docs with default keys

← Older revision		Revision as of 02:50, 22 December 2025
Line 111:		Line 111:
	* F11 - DivMMC NMI		* F11 - DivMMC NMI
	* F12 - Multiface NMI		* F12 - Multiface NMI

			Check [https://docs.mamedev.org/usingmame/defaultkeys.html default keys documentation] for more.

	= Changing the UI toggle key =		= Changing the UI toggle key =