SpecNext Wiki - User contributions [en-gb]

MAME:Installing

2026-05-12T16:24:05Z

Orcmeal: Added info about required SDL3 library when installing on macOS.

[https://www.mamedev.org/ MAME] (formerly an acronym of Multiple Arcade Machine Emulator) is a free and open-source emulator designed to emulate the hardware of arcade games, later expanded to include video game consoles, old computers and other systems in software on modern personal computers and other platforms.

MAME has supported the ZX Spectrum Next since version 0.267. The existing implementation is based on the v3.02.01 core and implements most of the features.

= Installation =

You will need to install MAME, provide it with the Next firmware ('ROM'), and get the NextZXOS image:

=== 1. Get MAME ===
Start with these official MAME releases. If you encounter crashes or other bugs, try replacing the MAME executable with holub's latest Continuous Integration (CI) builds as described at the end of this article.

MAME for macOS now requires the SDL3 library.

* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].
* '''macOS:''' Download the [https://github.com/libsdl-org/SDL/releases/latest SDL3 library], and copy its '''SDL3.xcframework''' and '''share''' folders to ~/Library/Frameworks, as instructed in the included INSTALL.md file. Then download [https://sdlmame.lngn.net/ MAME for macOS].
* '''Linux:''' Install MAME from the flatpak repositories by running:
<pre>sudo flatpak install org.mamedev.MAME</pre>

Note that Windows and macOS will likely prevent you from launching MAME (and the SDL3 framework) directly for security reasons. See below on how to solve this.

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/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/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') ===
Put the file [https://github.com/Threetwosevensixseven/NexCreator/raw/master/bootroms/tbblue.zip tbblue.zip] into MAME's <code>roms</code> folder. Don't extract it; MAME will look for the zip file when the "tbblue" machine is selected.

Note: The ROMs in this zip are what is embedded inside the FPGA core on real Next hardware. They're different from any ZX Spectrum machine ROMs you may be used to using, that are on the distro, SD card or SD image file.

=== 3. Get the NextZXOS Image ===
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 =
MAME looks for its configuration and helper files in specific (configurable) folders. By default, these are relative to the current working directory (cwd), i.e., from where you launched the executable. The <code>mame.ini</code> file and folders like <code>roms, bgfx, plugins, language, ...</code> are expected there, unless the <code>mame.ini</code> file specifies other paths. When launching through a desktop icon or menu, depending on the OS, the working directory is often defined by the properties of that launch shortcut. When launching MAME from the command line, the current directory is "cwd" (doh). On Linux, MAME will look for <code>mame.ini</code> first in the <code>~/.mame</code> folder. You can use the option <code>-inipath</code> to point MAME to a different path for the <code>mame.ini</code> file.

However, the fastest way to run a machine with a desired configuration is from the command prompt, without requiring a <code>mame.ini</code> file. Most of the features are also available through MAME's UI, although that takes more time to configure.

As an example, this invocation enables the UI, uses "crisp pixels", starts in a window, doesn't display the starting gameinfo window (it can still be displayed interactively from the UI), disables the mouse, confirms before exiting MAME, and specifies the disk image (remember to adjust the path to it):

<pre>mame -ui_active -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered -window -skip_gameinfo -mouse_device none -confirm_quit tbblue -hard1 /path/to/cspect-next-2gb.img</pre>

Let's cover some useful options:

<ol start="1">

<li>
Run inside a window and with no mouse support, until you get familiar with the UI keys:
<pre>> mame tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
To launch the Linux flatpak version using the same options:
<pre>> flatpak run org.mamedev.MAME tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
</li>

<li>
Activate UI keys on startup:
<pre>> ... -ui_active</pre>
</li>

<li>
Don't show the info popup on startup:
<pre>> ... -skip_gameinfo</pre>
</li>

<li>Run with debugger. If you don't request this on startup, you won't have access to it:
<pre>> ... -debug</pre>
</li>

<li>Use "crisp" pixels:
<pre>> ... -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered</pre>
</li>

<li>No joystick connected to PC (having this may slightly speed up MAME's startup, but ''remember to remove this part from the command line and the corresponding setting in the ini file if you do want to use a joystick''):
<pre>> ... -joystickprovider none</pre>
</li>

<li>Ask for confirmation when exiting MAME (otherwise it's easy to exit MAME accidentally by hitting ESC, especially when playing games or navigating menus):
<pre>> ... -confirm_quit</pre>
</ol>

Check the [https://docs.mamedev.org/commandline/commandline-all.html#mame-commandline-universal official MAME documentation] for more advanced usage.

= Security: Allowing MAME to Run on Windows and macOS =

'''On Windows,''' you will need to confirm that you want to launch MAME by clicking "Run Anyway" on first launch. ''(More details needed here.)''

'''On macOS,''' MAME will not open at first. Instead, a dialog will appear saying:

''“mame” Not Opened. Apple could not verify “mame” is free of malware that may harm your Mac or compromise your privacy.''

Click “Done”. Then open '''System Settings -> Privacy & Security''', and scroll down to the message ''mame was blocked to protect your Mac.'' Click “Allow Anyway”.

Now launch MAME again. A dialog will ask once more if you want to open “mame”. Click “Open Anyway”, and enter your password or use Touch ID when prompted by macOS.

You will then need to '''repeat this process for the SDL3 framework.'''

From now on, you can launch this version of MAME without warnings. However, you '''will''' need to repeat this each time you update MAME or the SDL3 framework.

= Keys =

Keys are emulated in two modes: either to control the MAME emulator or completely dedicated to the emulated system (the Next). You can toggle between these two keyboard modes with ScrLk (on Win and Linux) or fn+delete (on Mac).

Some UI keys:
* F3 - soft reset
* Shift+F3 - hard reset
* F4 - sprites/tiles/font viewer (Enter, ], [)
* F5 - pause emulation
* F6 - save state
* F7 - load state
* Tab - emulator settings
* ~ - menu
* ` (backtick) - debugger (when enabled by starting MAME with <code>-debug</code> or <code>-d</code> on the command line)
* PgDwn (Linux/Mac), fn-Downarrow (MacBooks) or Insert (Win) - hold down to fast-forward emulation at maximum speed, e.g., to speed up booting the Next
* Esc - exit (exits menus but also the entire emulator - see <code>-confirm_quit</code> option above)
* F11 - DivMMC NMI
* F12 - Multiface NMI

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

= Changing the UI toggle key =

Some laptops don't have a Scroll Lock key, so you may not be able to exit MAME if you run it in full-screen mode. In these cases, you can change the UI toggle key as follows:

* Run MAME without any command line arguments (except maybe -window) to open its GUI.
* Push TAB and enter the General Settings menu.
* Go to Input Assignments -> User Interface -> Toggle UI controls and select a new key. I use Right Alt / Alt GR.
* Return to the previous menu twice, then choose Save Settings

= 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 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.

== Creating and populating a SD card image using hdfmonkey jjjs build ==

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:

<pre>
hdfmonkey create NextZXOS.img 1G
hdfmonkey putdir NextZXOS.img snWXYZ /
</pre>

The first line creates an empty 1GB image and formats it with the best FAT parameters suited to the size of the image.

The second line recursively copies all the content of the directory <code>snWXYZ</code> to the image, preserving the directory structure inside, starting from the <code>/</code> in the image.

One of the advantages of this method is that even if the image has a capacity of 1GB, it will use much less space on your hard drive until you fill up the image. On Linux or MacOS, a command <code>du -h NextZXOS.img</code> shows the actual amount of disk space used by the image. On Windows the same information can be seen in the File Properties dialog.

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-card_image]].

=MAME Plugins and Scripts=

Some MAME plugins and scripts that may be useful for Next developers and end users are listed [[MAME:Plugins_and_Scripts|here]]. They let you speed up the Next boot time, profile your NextBASIC or assembler code, and more.

=Continuous Integration MAME Builds=

MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].

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.

'''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 (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 =

MAME [https://docs.mamedev.org/ documentation].

Report any issues with MAME on the [https://mametesters.org/ bugtracker].

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.

[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: [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]

MAME:Installing

2026-05-12T16:17:19Z

Orcmeal:

[https://www.mamedev.org/ MAME] (formerly an acronym of Multiple Arcade Machine Emulator) is a free and open-source emulator designed to emulate the hardware of arcade games, later expanded to include video game consoles, old computers and other systems in software on modern personal computers and other platforms.

MAME has supported the ZX Spectrum Next since version 0.267. The existing implementation is based on the v3.02.01 core and implements most of the features.

= Installation =

You will need to install MAME, provide it with the Next firmware ('ROM'), and get the NextZXOS image:

=== 1. Get MAME ===
Start with these official MAME releases. If you encounter crashes or other bugs, try replacing the MAME executable with holub's latest Continuous Integration (CI) builds as described at the end of this article.

MAME for macOS now requires the SDL3 library.

* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].
* '''macOS:''' Download [https://sdlmame.lngn.net/ MAME for macOS].
* '''Linux:''' Install MAME from the flatpak repositories by running:
<pre>sudo flatpak install org.mamedev.MAME</pre>

Note that Windows and macOS will likely prevent you from launching MAME directly for security reasons. See below on how to solve this.

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/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/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') ===
Put the file [https://github.com/Threetwosevensixseven/NexCreator/raw/master/bootroms/tbblue.zip tbblue.zip] into MAME's <code>roms</code> folder. Don't extract it; MAME will look for the zip file when the "tbblue" machine is selected.

Note: The ROMs in this zip are what is embedded inside the FPGA core on real Next hardware. They're different from any ZX Spectrum machine ROMs you may be used to using, that are on the distro, SD card or SD image file.

=== 3. Get the NextZXOS Image ===
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 =
MAME looks for its configuration and helper files in specific (configurable) folders. By default, these are relative to the current working directory (cwd), i.e., from where you launched the executable. The <code>mame.ini</code> file and folders like <code>roms, bgfx, plugins, language, ...</code> are expected there, unless the <code>mame.ini</code> file specifies other paths. When launching through a desktop icon or menu, depending on the OS, the working directory is often defined by the properties of that launch shortcut. When launching MAME from the command line, the current directory is "cwd" (doh). On Linux, MAME will look for <code>mame.ini</code> first in the <code>~/.mame</code> folder. You can use the option <code>-inipath</code> to point MAME to a different path for the <code>mame.ini</code> file.

However, the fastest way to run a machine with a desired configuration is from the command prompt, without requiring a <code>mame.ini</code> file. Most of the features are also available through MAME's UI, although that takes more time to configure.

As an example, this invocation enables the UI, uses "crisp pixels", starts in a window, doesn't display the starting gameinfo window (it can still be displayed interactively from the UI), disables the mouse, confirms before exiting MAME, and specifies the disk image (remember to adjust the path to it):

<pre>mame -ui_active -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered -window -skip_gameinfo -mouse_device none -confirm_quit tbblue -hard1 /path/to/cspect-next-2gb.img</pre>

Let's cover some useful options:

<ol start="1">

<li>
Run inside a window and with no mouse support, until you get familiar with the UI keys:
<pre>> mame tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
To launch the Linux flatpak version using the same options:
<pre>> flatpak run org.mamedev.MAME tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
</li>

<li>
Activate UI keys on startup:
<pre>> ... -ui_active</pre>
</li>

<li>
Don't show the info popup on startup:
<pre>> ... -skip_gameinfo</pre>
</li>

<li>Run with debugger. If you don't request this on startup, you won't have access to it:
<pre>> ... -debug</pre>
</li>

<li>Use "crisp" pixels:
<pre>> ... -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered</pre>
</li>

<li>No joystick connected to PC (having this may slightly speed up MAME's startup, but ''remember to remove this part from the command line and the corresponding setting in the ini file if you do want to use a joystick''):
<pre>> ... -joystickprovider none</pre>
</li>

<li>Ask for confirmation when exiting MAME (otherwise it's easy to exit MAME accidentally by hitting ESC, especially when playing games or navigating menus):
<pre>> ... -confirm_quit</pre>
</ol>

Check the [https://docs.mamedev.org/commandline/commandline-all.html#mame-commandline-universal official MAME documentation] for more advanced usage.

= Security: Allowing MAME to Run on Windows and macOS =

'''On Windows,''' you will need to confirm that you want to launch MAME by clicking "Run Anyway" on first launch. ''(More details needed here.)''

'''On macOS,''' MAME will not open at first. Instead, a dialog will appear saying:

''“mame” Not Opened. Apple could not verify “mame” is free of malware that may harm your Mac or compromise your privacy.''

Click “Done”. Then open '''System Settings -> Privacy & Security''', and scroll down to the message ''mame was blocked to protect your Mac.'' Click “Allow Anyway”.

Now launch MAME again. A dialog will ask once more if you want to open “mame”. Click “Open Anyway”, and enter your password or use Touch ID when prompted by macOS.

From now on, you can launch this version of MAME without warnings. However, you '''will''' need to repeat this each time you update MAME.

= Keys =

Keys are emulated in two modes: either to control the MAME emulator or completely dedicated to the emulated system (the Next). You can toggle between these two keyboard modes with ScrLk (on Win and Linux) or fn+delete (on Mac).

Some UI keys:
* F3 - soft reset
* Shift+F3 - hard reset
* F4 - sprites/tiles/font viewer (Enter, ], [)
* F5 - pause emulation
* F6 - save state
* F7 - load state
* Tab - emulator settings
* ~ - menu
* ` (backtick) - debugger (when enabled by starting MAME with <code>-debug</code> or <code>-d</code> on the command line)
* PgDwn (Linux/Mac), fn-Downarrow (MacBooks) or Insert (Win) - hold down to fast-forward emulation at maximum speed, e.g., to speed up booting the Next
* Esc - exit (exits menus but also the entire emulator - see <code>-confirm_quit</code> option above)
* F11 - DivMMC NMI
* F12 - Multiface NMI

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

= Changing the UI toggle key =

Some laptops don't have a Scroll Lock key, so you may not be able to exit MAME if you run it in full-screen mode. In these cases, you can change the UI toggle key as follows:

* Run MAME without any command line arguments (except maybe -window) to open its GUI.
* Push TAB and enter the General Settings menu.
* Go to Input Assignments -> User Interface -> Toggle UI controls and select a new key. I use Right Alt / Alt GR.
* Return to the previous menu twice, then choose Save Settings

= 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 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.

== Creating and populating a SD card image using hdfmonkey jjjs build ==

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:

<pre>
hdfmonkey create NextZXOS.img 1G
hdfmonkey putdir NextZXOS.img snWXYZ /
</pre>

The first line creates an empty 1GB image and formats it with the best FAT parameters suited to the size of the image.

The second line recursively copies all the content of the directory <code>snWXYZ</code> to the image, preserving the directory structure inside, starting from the <code>/</code> in the image.

One of the advantages of this method is that even if the image has a capacity of 1GB, it will use much less space on your hard drive until you fill up the image. On Linux or MacOS, a command <code>du -h NextZXOS.img</code> shows the actual amount of disk space used by the image. On Windows the same information can be seen in the File Properties dialog.

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-card_image]].

=MAME Plugins and Scripts=

Some MAME plugins and scripts that may be useful for Next developers and end users are listed [[MAME:Plugins_and_Scripts|here]]. They let you speed up the Next boot time, profile your NextBASIC or assembler code, and more.

=Continuous Integration MAME Builds=

MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].

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.

'''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 (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 =

MAME [https://docs.mamedev.org/ documentation].

Report any issues with MAME on the [https://mametesters.org/ bugtracker].

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.

[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: [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]

MAME:Installing

2025-12-06T13:03:13Z

Orcmeal: Added suggestion in the beginnign to start with official MAME, and try the CI builds if problems occur.

[https://www.mamedev.org/ MAME] (formerly an acronym of Multiple Arcade Machine Emulator) is a free and open-source emulator designed to emulate the hardware of arcade games, later expanded to include video game consoles, old computers and other systems in software on modern personal computers and other platforms.

MAME has supported the ZX Spectrum Next since version 0.267. The existing implementation is based on the v3.02.01 core and implements most of the features.

= Installation =

You will need to install MAME, provide it with the Next firmware ('ROM'), and get the NextZXOS image:

=== 1. Get MAME ===
Start with these official MAME releases. If you encounter crashes or other bugs, try replacing the MAME executable with holub's latest Continuous Integration (CI) builds as described at the end of this article.

* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].
* '''macOS:''' Download [https://sdlmame.lngn.net/ MAME for macOS].
* '''Linux:''' Install MAME from the flatpak repositories by running:
<pre>sudo flatpak install org.mamedev.MAME</pre>

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].

Note that Windows and macOS will likely prevent you from launching MAME directly for security reasons. See below on how to solve this.

=== 2. Get TBBLUE (the Next 'ROM') ===
Put the file [https://github.com/Threetwosevensixseven/NexCreator/raw/master/bootroms/tbblue.zip tbblue.zip] into MAME's <code>roms</code> folder. Don't extract it; MAME will look for the zip file when the "tbblue" machine is selected.

=== 3. Get the NextZXOS Image ===
Get an SD card image file of [https://www.specnext.com/system-next22-10/ NextZXOS]. Some published images do not work with some emulators, but all images from https://zxnext.uk/hosted/#sd are now confirmed to work with both MAME and CSpect, like [https://zxnext.uk/hosted/index_files/hdfimages/cspect-next-2gb.zip this one] (the SD card image is the <code>cspect-next-2gb.img</code> file inside the zip archive). You will point MAME to this SD card image with the <code>-hard1</code> or <code>-hard2</code> options (or select the files from the menu inside MAME).

= Usage =
MAME looks for its configuration and helper files in specific (configurable) folders. By default, these are relative to the current working directory (cwd), i.e., from where you launched the executable. The <code>mame.ini</code> file and folders like <code>roms, bgfx, plugins, language, ...</code> are expected there, unless the <code>mame.ini</code> file specifies other paths. When launching through a desktop icon or menu, depending on the OS, the working directory is often defined by the properties of that launch shortcut. When launching MAME from the command line, the current directory is "cwd" (doh). On Linux, MAME will look for <code>mame.ini</code> first in the <code>~/.mame</code> folder. You can use the option <code>-inipath</code> to point MAME to a different path for the <code>mame.ini</code> file.

However, the fastest way to run a machine with a desired configuration is from the command prompt, without requiring a <code>mame.ini</code> file. Most of the features are also available through MAME's UI, although that takes more time to configure.

Let's cover some useful options:

<ol start="1">

<li>
Run inside a window and with no mouse support, until you get familiar with the UI keys:
<pre>> mame tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
To launch the Linux flatpak version using the same options:
<pre>> flatpak run org.mamedev.MAME tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
</li>

<li>
Activate UI keys on startup:
<pre>> ... -ui_active</pre>
</li>

<li>
Don't show the info popup on startup:
<pre>> ... -skip_gameinfo</pre>
</li>

<li>Run with debugger. If you don't request this on startup, you won't have access to it:
<pre>> ... -debug</pre>
</li>

<li>Use "crisp" pixels:
<pre>> ... -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered</pre>
</li>

<li>No joystick connected to PC (may slightly speed up MAME's startup):
<pre>> ... -joystickprovider none</pre>
</li>

<li>Ask for confirmation when exiting MAME (otherwise it's easy to exit MAME accidentally by hitting ESC, especially when playing games or navigating menus):
<pre>> ... -confirm_quit</pre>
</ol>

Check the [https://docs.mamedev.org/commandline/commandline-all.html#mame-commandline-universal official MAME documentation] for more advanced usage.

As an example, this invocation enables the UI, uses "crisp pixels", starts in a window, doesn't display the starting gameinfo window (it can still be displayed interactively from the UI), disables the mouse, confirms before exiting MAME, and specifies the disk image (remember to adjust the path to it):

<pre>mame -ui_active -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered -window -skip_gameinfo -mouse_device none -confirm_quit tbblue -hard1 /path/to/cspect-next-2gb.img</pre>

= Security: Allowing MAME to Run on Windows and macOS =

'''On Windows,''' you will need to confirm that you want to launch MAME by clicking "Run Anyway" on first launch. ''(More details needed here.)''

'''On macOS,''' MAME will not open at first. Instead, a dialog will appear saying:

''“mame” Not Opened. Apple could not verify “mame” is free of malware that may harm your Mac or compromise your privacy.''

Click “Done”. Then open '''System Settings -> Privacy & Security''', and scroll down to the message ''mame was blocked to protect your Mac.'' Click “Allow Anyway”.

Now launch MAME again. A dialog will ask once more if you want to open “mame”. Click “Open Anyway”, and enter your password or use Touch ID when prompted by macOS.

From now on, you can launch this version of MAME without warnings. However, you '''will''' need to repeat this each time you update MAME.

= Keys =

Keys are emulated in two modes: either to control the MAME emulator or completely dedicated to the emulated system (the Next). You can toggle between these two keyboard modes with ScrLk (on Win and Linux) or fn+delete (on Mac).

Some UI keys:
* F3 - soft reset
* Shift+F3 - hard reset
* F4 - sprites/tiles/font viewer (Enter, ], [)
* F5 - pause emulation
* F6 - save state
* F7 - load state
* Tab - emulator settings
* ~ - menu
* ` (backtick) - debugger (when enabled by starting MAME with <code>-debug</code> or <code>-d</code> on the command line)
* PgDwn (Linux/Mac), fn-Downarrow (MacBooks) or Insert (Win) - hold down to fast-forward emulation at maximum speed, e.g., to speed up booting the Next
* Esc - exit (exits menus but also the entire emulator - see <code>-confirm_quit</code> option above)
* F11 - DivMMC NMI
* F12 - Multiface NMI

= Changing the UI toggle key =

Some laptops don't have a Scroll Lock key, so you may not be able to exit MAME if you run it in full-screen mode. In these cases, you can change the UI toggle key as follows:

* Run MAME without any command line arguments (except maybe -window) to open its GUI.
* Push TAB and enter the General Settings menu.
* Go to Input Assignments -> User Interface -> Toggle UI controls and select a new key. I use Right Alt / Alt GR.
* Return to the previous menu twice, then choose Save Settings

= Creating a NextZXOS SD card image under Linux =

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.

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.

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

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 [[Development_Tools:Linux_setup#hdfmonkey_tool | "jjjs build" of hdfmonkey]], then it's enough to do:

<pre>
hdfmonkey create NextZXOS.img 1G
hdfmonkey putdir NextZXOS.img snWXYZ /
</pre>

The first line creates an empty 1GB image and formats it with the best FAT parameters suited to the size of the image.

The second line recursively copies all the content of the directory <code>snWXYZ</code> to the image, preserving the directory structure inside, starting from the <code>/</code> in the image.

One of the advantages of this method is that even if the image has a capacity of 1GB, it will use much less space on your hard drive until you fill up the image. A command <code>du -h NextZXOS.img</code> shows the actual amount of disk space used by the image.

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 [[Development_Tools:Linux_setup#Extracting_all_files_from_the_SD_image | copy of all the content from the image to a folder outside of the image]] is 7-zip.

== Creating and populating a SD card image using other tools ==

Create a disk image of at least 256 MB. The current complete NextZXOS distro requires at least 130 MB of disk space. This command will create a 256 MB SD card image; change the <code>count</code> value to make the image file as big as you want in megabytes:

<pre>dd if=/dev/zero of=NextZXOS.img bs=1M count=256</pre>

The rest of the commands in this guide must be run as the root user or using sudo.

You will need to install the dosfstools and parted packages if they are not already installed. Debian and Ubuntu Linux users can install these using this apt command:

<pre>apt install dosfstools parted</pre>

Mount the SD card image loopback device:

<pre>losetup --partscan --show --find NextZXOS.img</pre>

Create a FAT32 partition:

<pre>parted /dev/loop0 mklabel msdos
parted /dev/loop0 mkpart primary fat32 1MB 100%</pre>

Format and mount the partition under /mnt:

<pre>mkfs.vfat -F 32 /dev/loop0p1
mount /dev/loop0p1 /mnt</pre>

You can now copy all of the files you extracted from sn-complete-WX.YZ.zip into /mnt.

After copying the files, unmount and detach the loopback device (the SD card image):

<pre>umount /mnt/
losetup -D</pre>

Warning: the resulting image of this method, if the parameters of different steps aren't carefully chosen and matched, could be out of the official FAT specifications and/or the expectations of some of the existing programs or systems.

= Mounting SD card images under Linux =

Under Linux, you can use <code>losetup</code> to mount SD card images as loop devices. This lets you copy files to and from the image and perform other file management tasks as you would using any other filesystem.

Run the following commands as the root user to mount an image called sn-emulator-22.10a.img under the /mnt directory:

<pre>losetup --partscan --show --find cspect-next-2gb.img
mount /dev/loop0p1 /mnt/</pre>

After you are finished modifying the SD card image, cd out of /mnt, then unmount and detach the loopback device:

<pre>umount /mnt/
losetup -D</pre>

=MAME Plugins and Scripts=

Some MAME plugins and scripts that may be useful for Next developers and end users are listed [[MAME:Plugins_and_Scripts|here]]. They let you speed up the Next boot time, profile your NextBASIC or assembler code, and more.

=Continuous Integration MAME Builds=

MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].

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].

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 =

The official MAME source code repository is available [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/specnext.cpp here].

holub, the author of the Next emulation, maintains a fork [https://github.com/holub/mame here] that may contain new fixes and features before they are merged into the official repository.

MAME [https://docs.mamedev.org/ documentation].

Report any issues with MAME on the [https://mametesters.org/ bugtracker].

MAME:Installing

2025-12-05T22:46:59Z

Orcmeal: Added security instructions for macOS. Reformatted instructions for clarity.

[https://www.mamedev.org/ MAME] (formerly an acronym of Multiple Arcade Machine Emulator) is a free and open-source emulator designed to emulate the hardware of arcade games, later expanded to include video game consoles, old computers and other systems in software on modern personal computers and other platforms.

MAME has supported the ZX Spectrum Next since version 0.267. The existing implementation is based on the v3.02.01 core and implements most of the features.

= Installation =

You will need to install MAME, provide it with the Next firmware ('ROM'), and get the NextZXOS image:

=== 1. Get MAME ===
* '''Windows:''' Download [https://www.mamedev.org/release.html MAME for Windows].
* '''macOS:''' Download [https://sdlmame.lngn.net/ MAME for macOS].
* '''Linux:''' Install MAME from the flatpak repositories by running:
<pre>sudo flatpak install org.mamedev.MAME</pre>

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].

Note that Windows and macOS will likely prevent you from launching MAME directly for security reasons. See below on how to solve this.

=== 2. Get TBBLUE (the Next 'ROM') ===
Put the file [https://github.com/Threetwosevensixseven/NexCreator/raw/master/bootroms/tbblue.zip tbblue.zip] into MAME's <code>roms</code> folder. Don't extract it; MAME will look for the zip file when the "tbblue" machine is selected.

=== 3. Get the NextZXOS Image ===
Get an SD card image file of [https://www.specnext.com/system-next22-10/ NextZXOS]. Some published images do not work with some emulators, but all images from https://zxnext.uk/hosted/#sd are now confirmed to work with both MAME and CSpect, like [https://zxnext.uk/hosted/index_files/hdfimages/cspect-next-2gb.zip this one] (the SD card image is the <code>cspect-next-2gb.img</code> file inside the zip archive). You will point MAME to this SD card image with the <code>-hard1</code> or <code>-hard2</code> options (or select the files from the menu inside MAME).

= Usage =
MAME looks for its configuration and helper files in specific (configurable) folders. By default, these are relative to the current working directory (cwd), i.e., from where you launched the executable. The <code>mame.ini</code> file and folders like <code>roms, bgfx, plugins, language, ...</code> are expected there, unless the <code>mame.ini</code> file specifies other paths. When launching through a desktop icon or menu, depending on the OS, the working directory is often defined by the properties of that launch shortcut. When launching MAME from the command line, the current directory is "cwd" (doh). On Linux, MAME will look for <code>mame.ini</code> first in the <code>~/.mame</code> folder. You can use the option <code>-inipath</code> to point MAME to a different path for the <code>mame.ini</code> file.

However, the fastest way to run a machine with a desired configuration is from the command prompt, without requiring a <code>mame.ini</code> file. Most of the features are also available through MAME's UI, although that takes more time to configure.

Let's cover some useful options:

<ol start="1">

<li>
Run inside a window and with no mouse support, until you get familiar with the UI keys:
<pre>> mame tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
To launch the Linux flatpak version using the same options:
<pre>> flatpak run org.mamedev.MAME tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
</li>

<li>
Activate UI keys on startup:
<pre>> ... -ui_active</pre>
</li>

<li>
Don't show the info popup on startup:
<pre>> ... -skip_gameinfo</pre>
</li>

<li>Run with debugger. If you don't request this on startup, you won't have access to it:
<pre>> ... -debug</pre>
</li>

<li>Use "crisp" pixels:
<pre>> ... -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered</pre>
</li>

<li>No joystick connected to PC (may slightly speed up MAME's startup):
<pre>> ... -joystickprovider none</pre>
</li>

<li>Ask for confirmation when exiting MAME (otherwise it's easy to exit MAME accidentally by hitting ESC, especially when playing games or navigating menus):
<pre>> ... -confirm_quit</pre>
</ol>

Check the [https://docs.mamedev.org/commandline/commandline-all.html#mame-commandline-universal official MAME documentation] for more advanced usage.

As an example, this invocation enables the UI, uses "crisp pixels", starts in a window, doesn't display the starting gameinfo window (it can still be displayed interactively from the UI), disables the mouse, confirms before exiting MAME, and specifies the disk image (remember to adjust the path to it):

<pre>mame -ui_active -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered -window -skip_gameinfo -mouse_device none -confirm_quit tbblue -hard1 /path/to/cspect-next-2gb.img</pre>

= Security: Allowing MAME to Run on Windows and macOS =

'''On Windows,''' you will need to confirm that you want to launch MAME by clicking "Run Anyway" on first launch. ''(More details needed here.)''

'''On macOS,''' MAME will not open at first. Instead, a dialog will appear saying:

''“mame” Not Opened. Apple could not verify “mame” is free of malware that may harm your Mac or compromise your privacy.''

Click “Done”. Then open '''System Settings -> Privacy & Security''', and scroll down to the message ''mame was blocked to protect your Mac.'' Click “Allow Anyway”.

Now launch MAME again. A dialog will ask once more if you want to open “mame”. Click “Open Anyway”, and enter your password or use Touch ID when prompted by macOS.

From now on, you can launch this version of MAME without warnings. However, you '''will''' need to repeat this each time you update MAME.

= Keys =

Keys are emulated in two modes: either to control the MAME emulator or completely dedicated to the emulated system (the Next). You can toggle between these two keyboard modes with ScrLk (on Win and Linux) or fn+delete (on Mac).

Some UI keys:
* F3 - soft reset
* Shift+F3 - hard reset
* F4 - sprites/tiles/font viewer (Enter, ], [)
* F5 - pause emulation
* F6 - save state
* F7 - load state
* Tab - emulator settings
* ~ - menu
* ` (backtick) - debugger (when enabled by starting MAME with <code>-debug</code> or <code>-d</code> on the command line)
* PgDwn (Linux/Mac), fn-Downarrow (MacBooks) or Insert (Win) - hold down to fast-forward emulation at maximum speed, e.g., to speed up booting the Next
* Esc - exit (exits menus but also the entire emulator - see <code>-confirm_quit</code> option above)
* F11 - DivMMC NMI
* F12 - Multiface NMI

= Changing the UI toggle key =

Some laptops don't have a Scroll Lock key, so you may not be able to exit MAME if you run it in full-screen mode. In these cases, you can change the UI toggle key as follows:

* Run MAME without any command line arguments (except maybe -window) to open its GUI.
* Push TAB and enter the General Settings menu.
* Go to Input Assignments -> User Interface -> Toggle UI controls and select a new key. I use Right Alt / Alt GR.
* Return to the previous menu twice, then choose Save Settings

= Creating a NextZXOS SD card image under Linux =

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.

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.

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

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 [[Development_Tools:Linux_setup#hdfmonkey_tool | "jjjs build" of hdfmonkey]], then it's enough to do:

<pre>
hdfmonkey create NextZXOS.img 1G
hdfmonkey putdir NextZXOS.img snWXYZ /
</pre>

The first line creates an empty 1GB image and formats it with the best FAT parameters suited to the size of the image.

The second line recursively copies all the content of the directory <code>snWXYZ</code> to the image, preserving the directory structure inside, starting from the <code>/</code> in the image.

One of the advantages of this method is that even if the image has a capacity of 1GB, it will use much less space on your hard drive until you fill up the image. A command <code>du -h NextZXOS.img</code> shows the actual amount of disk space used by the image.

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 [[Development_Tools:Linux_setup#Extracting_all_files_from_the_SD_image | copy of all the content from the image to a folder outside of the image]] is 7-zip.

== Creating and populating a SD card image using other tools ==

Create a disk image of at least 256 MB. The current complete NextZXOS distro requires at least 130 MB of disk space. This command will create a 256 MB SD card image; change the <code>count</code> value to make the image file as big as you want in megabytes:

<pre>dd if=/dev/zero of=NextZXOS.img bs=1M count=256</pre>

The rest of the commands in this guide must be run as the root user or using sudo.

You will need to install the dosfstools and parted packages if they are not already installed. Debian and Ubuntu Linux users can install these using this apt command:

<pre>apt install dosfstools parted</pre>

Mount the SD card image loopback device:

<pre>losetup --partscan --show --find NextZXOS.img</pre>

Create a FAT32 partition:

<pre>parted /dev/loop0 mklabel msdos
parted /dev/loop0 mkpart primary fat32 1MB 100%</pre>

Format and mount the partition under /mnt:

<pre>mkfs.vfat -F 32 /dev/loop0p1
mount /dev/loop0p1 /mnt</pre>

You can now copy all of the files you extracted from sn-complete-WX.YZ.zip into /mnt.

After copying the files, unmount and detach the loopback device (the SD card image):

<pre>umount /mnt/
losetup -D</pre>

Warning: the resulting image of this method, if the parameters of different steps aren't carefully chosen and matched, could be out of the official FAT specifications and/or the expectations of some of the existing programs or systems.

= Mounting SD card images under Linux =

Under Linux, you can use <code>losetup</code> to mount SD card images as loop devices. This lets you copy files to and from the image and perform other file management tasks as you would using any other filesystem.

Run the following commands as the root user to mount an image called sn-emulator-22.10a.img under the /mnt directory:

<pre>losetup --partscan --show --find cspect-next-2gb.img
mount /dev/loop0p1 /mnt/</pre>

After you are finished modifying the SD card image, cd out of /mnt, then unmount and detach the loopback device:

<pre>umount /mnt/
losetup -D</pre>

=MAME Plugins and Scripts=

Some MAME plugins and scripts that may be useful for Next developers and end users are listed [[MAME:Plugins_and_Scripts|here]]. They let you speed up the Next boot time, profile your NextBASIC or assembler code, and more.

=Continuous Integration MAME Builds=

MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].

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].

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 =

The official MAME source code repository is available [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/specnext.cpp here].

holub, the author of the Next emulation, maintains a fork [https://github.com/holub/mame here] that may contain new fixes and features before they are merged into the official repository.

MAME [https://docs.mamedev.org/ documentation].

Report any issues with MAME on the [https://mametesters.org/ bugtracker].

MAME:Installing

2025-12-02T19:01:08Z

Orcmeal: Added -confirm_quit startup option. Corrected minor typos throughout.

[https://www.mamedev.org/ MAME] (formerly an acronym of Multiple Arcade Machine Emulator) is a free and open-source emulator designed to emulate the hardware of arcade games, later expanded to include video game consoles, old computers and other systems in software on modern personal computers and other platforms.

MAME supports the ZX Spectrum Next since version 0.267. The existing implementation is based on the v3.02.01 core and implements most of the features.

= Get =
The latest MAME version for Windows is available [https://www.mamedev.org/release.html here], and macOS builds can be downloaded from [https://sdlmame.lngn.net/ here.] For the MAME platform as a whole, check your package manager, or [https://docs.mamedev.org/initialsetup/compilingmame.html build from sources].

Linux users can also install the latest stable version of MAME from the flatpak repositories by running:
<pre>sudo flatpak install org.mamedev.MAME</pre>

Put the ROM dump zip of the ZX Next [https://github.com/Threetwosevensixseven/NexCreator/raw/master/bootroms/tbblue.zip tbblue.zip] into MAME's <code>roms</code> folder (don't extract it; MAME will look for the zip file when the "tbblue" machine is selected).

Prepare an SD card image file of [https://www.specnext.com/system-next22-10/ NextZXOS]. Some published images do not work with some emulators, but all images from https://zxnext.uk/hosted/#sd are now confirmed to work with both MAME and CSpect, including the official ones like [https://zxnext.uk/hosted/index_files/hdfimages/cspect-next-2gb.zip this one] (the SD card image is the <code>cspect-next-2gb.img</code> file inside the zip archive). You will point MAME to the desired SD card image with the <code>-hard1</code> or <code>-hard2</code> options (or select the files from the menu inside the emulator).

= Use =
MAME looks for its configuration and helper files in specific (configurable) folders. By default, these are relative to the current working directory (cwd), ie., from where you launched the executable. The <code>mame.ini</code> file and folders like <code>roms, bgfx, plugins, language, ...</code> are expected there, unless the <code>mame.ini</code> file specifies other paths. When launching through a desktop icon or menu, depending on the OS, the working directory is often defined by the properties of that launch shortcut. When launching MAME from the command line, the current directory is "cwd" (doh). On Linux, MAME will look for <code>mame.ini</code> first in the <code>~/.mame</code> folder. You can use the option <code>-inipath</code> to point MAME to a different path for the <code>mame.ini</code> file.

The fastest way to run a machine with a desired configuration is from the command prompt. Most of the features are also available through MAME's UI, but that takes more time to configure.

Let's cover some useful options:

<ol start="1">

<li>
Run inside a window and with no mouse support, until you get familiar with the UI keys:
<pre>> mame tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
To launch the Linux flatpak version using the same options:
<pre>> flatpak run org.mamedev.MAME tbblue -window -mouse_device none -hard1 /path/to/next-distribution.img</pre>
</li>

<li>
Activate UI keys on startup:
<pre>> ... -ui_active</pre>
</li>

<li>
Don't show the info popup on startup:
<pre>> ... -skip_gameinfo</pre>
</li>

<li>Run with debugger. If you don't request this on startup, you won't have access to it:
<pre>> ... -debug</pre>
</li>

<li>Use "crisp" pixels:
<pre>> ... -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered</pre>
</li>

<li>No joystick connected to PC (may slightly speed up MAME's startup):
<pre>> ... -joystickprovider none</pre>
</li>

<li>Ask for confirmation when exiting MAME (otherwise it's easy to exit MAME accidentally by hitting ESC, especially when playing games or navigating menus):
<pre>> ... -confirm_quit</pre>
</ol>

Check the [https://docs.mamedev.org/commandline/commandline-all.html#mame-commandline-universal official MAME documentation] for more advanced usage.

As an example, this invocation enables the UI, uses "crisp pixels", starts in a window, doesn't display the starting gameinfo window (it can still be displayed interactively from the UI), disables the mouse, confirms before exiting MAME, and specifies the disk image:

<pre>mame -ui_active -nounevenstretch -aspect 2:1 -video bgfx -bgfx_screen_chains unfiltered -window -skip_gameinfo -mouse_device none -confirm_quit tbblue -hard1 /path/to/next-distribution.img</pre>

= Keys =

Keys are emulated in two modes: either to control the MAME emulator or completely dedicated to the emulated system (the Next). You can toggle between these two keyboard modes with ScrLk (on Win and Linux) or fn+delete (on Mac).

Some UI keys:
* F3 - soft reset
* Shift+F3 - hard reset
* F4 - sprites/tiles/font viewer (Enter, ], [)
* F5 - pause emulation
* F6 - save state
* F7 - load state
* Tab - emulator settings
* ~ - menu
* PgDwn (Linux/Mac), fn-Downarrow (MacBooks) or Insert (Win) - hold down to fast-forward emulation at maximum speed, e.g., to speed up booting the Next
* Esc - exit (exits menus but also the entire emulator - see <code>-confirm_quit</code> option above)
* F11 - DivMMC NMI
* F12 - Multiface NMI

= Changing the UI toggle key =

Some laptops don't have a Scroll Lock key, so you may not be able to exit MAME if you run it in full-screen mode. In these cases, you can change the UI toggle key as follows:

* Run MAME without any command line arguments (except maybe -window) to open its GUI.
* Push TAB and enter the General Settings menu.
* Go to Input Assignments -> User Interface -> Toggle UI controls and select a new key. I use Right Alt / Alt GR.
* Return to the previous menu twice, then choose Save Settings

= Mounting SD card images under Linux =

Under Linux, you can use <code>losetup</code> to mount SD card images as loop devices. This lets you copy files to and from the image and perform other file management tasks as you would using any other filesystem.

Run the following commands as the root user to mount an image called sn-emulator-22.10a.img under the /mnt directory:

<pre>losetup --partscan --show --find cspect-next-2gb.img
mount /dev/loop0p1 /mnt/</pre>

After you are finished modifying the SD card image, cd out of /mnt, then unmount and detach the loopback device:

<pre>umount /mnt/
losetup -D</pre>

= Creating a NextZXOS SD card image under Linux =

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.

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.

Create a disk image of at least 256 MB. The current complete NextZXOS distro requires at least 130 MB of disk space. This command will create a 256 MB SD card image; change the <code>count</code> value to make the image file as big as you want in megabytes:

<pre>dd if=/dev/zero of=NextZXOS.img bs=1M count=256</pre>

The rest of the commands in this guide must be run as the root user or using sudo.

You will need to install the dosfstools and parted packages if they are not already installed. Debian and Ubuntu Linux users can install these using this apt command:

<pre>apt install dosfstools parted</pre>

Mount the SD card image loopback device:

<pre>losetup --partscan --show --find NextZXOS.img</pre>

Create a FAT32 partition:

<pre>parted /dev/loop0 mklabel msdos
parted /dev/loop0 mkpart primary fat32 1MB 100%</pre>

Format and mount the partition under /mnt:

<pre>mkfs.vfat -F 32 /dev/loop0p1
mount /dev/loop0p1 /mnt</pre>

You can now copy all of the files you extracted from sn-complete-WX.YZ.zip into /mnt.

After copying the files, unmount and detach the loopback device (the SD card image):

<pre>umount /mnt/
losetup -D</pre>

=MAME Plugins and Scripts=

Some MAME plugins and scripts that may be useful for Next developers and end users are listed [[MAME:Plugins_and_Scripts|here: MAME:Plugins_and_Scripts]]. They let you speed up the Next boot time, profile your NextBASIC or assembler code, and more.

=Continuous Integration MAME Builds=

MAME is updated on a release schedule, but due to the ongoing nature of development, including for the MAME Next machine, it can sometimes be useful to install a more recent build if it contains a new feature or bugfix you are interested in. Sometimes, this ongoing work is discussed on social media, such as the [https://discordapp.com/channels/556228195767156758/752197165891321886 Next Developer Discord].

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, 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>, <code>mame</code> or <code>mametiny</code>. You can always restore these if the CI build doesn't work, or if you don't like how it behaves.

Then visit one of the links above and find a workflow run item for your platform - these are flagged as <code>CI (Windows)</code>, <code>CI (Linux)</code>, or <code>CI (macOS)</code>. Click on it and 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 may need to take an additional step to trust the binary ("Run Anyway" on Windows; "System Preferences -> Privacy & Security -> Allow mame to Run" on macOS).

= More MAME links =

The official MAME source code repository is available [https://github.com/mamedev/mame/blob/master/src/mame/sinclair/specnext.cpp here].

holub, the author of the Next emulation, maintains a fork [https://github.com/holub/mame here] that may contain new fixes and features before they are merged into the official repository.

MAME [https://docs.mamedev.org/ documentation].

Report any issues with MAME on the [https://mametesters.org/ bugtracker].

Miscellaneous

2025-06-13T07:54:33Z

Orcmeal: hdfmonkey: Changed Janko’s author name at his request

=== ''[http://simon.mooli.org.uk/nextech/ Simon N Goodwin's Spectrum Next Page]'' ===
: A host of utilites for NextBasic written by Simon, NextPort, Nextramon,
: Next MGT Reader amongst other treasures.

=== ''[https://github.com/kounch/vscode_zx Visual Studio Code Tasks and Scripts]'' ===
: Some VSC goodies by kounch to work with NextBasic and ZX Basic

=== ''[https://github.com/stefanbylund/zxnext_bmp_tools Next BMP Tools]'' ===
: The Next BMP tools are BMP image conversion tools targeting the Sinclair ZX Spectrum Next written
: by Stefan Bylund

=== ''[https://wiki.twistedraven.net/index.php?title=Downloads Octarine Studio]'' ===
: Octarine Studio by Guy Black is a PC based editing tool that currently supports palettes and tiles.

=== ''[https://www.specnext.com/forum/viewtopic.php?f=7&t=351 UDGeedNext Sprite Editor]'' ===
: Windows based sprite editor written by some guy I have never heard of. Currently supports 8 bit
: palettes. 9 bit and 4 bit sprites should be added at some point....

=== ''[http://worldofpaul.com/speccyart/ Speccy Art]'' ===
: An online drawing experience that aims to help you create Sinclair ZX Spectrum-like images.
: Supports the classic ULA mode (256x192 pixels with 8x8 attribute squares and 15 classic ZX colours)
: Supports the Timex HiColour mode (256x192 pixels with 8x1 attribute rectangles and 15 classic ZX colours)
: Images can be saved and loaded through TAP files or exported into SCR/SHC files.

=== ''[https://github.com/varmfskii/zxnext_tools ZX Spectrum Next tools by Theodore (Alex) Evans]'' ===
: Multiple tools for various graphics conversions and processing
: zxnftp for transferring files between PC and Next via the ESP WiFi module

=== ''[https://gitlab.com/zxnexttools/nim Next Image Manipulator by Matt Davies]'' ===
: windows command line tool to convert various image and palette formats to custom "nip/nim" binary formats which are simple enough to parse (or include directly into source with assemblers supporting binary includes)
: this is early version (already working, build it from source), but further expansion to support also tiles/etc may happen in future

=== ''[https://github.com/gasman/hdfmonkey hdfmonkey]'' ===
: A Swiss Army Knife for working with FAT partitions on Spectrum emulator HDF images. The more recent [https://www.specnext.com/forum/viewtopic.php?p=16108 hdfmonkey jjjs builds by johnnyo] also support the [https://www.specnext.com/latestdistro/ imperfect SD card images of the distribution for emulators from specnext.com], and they include executable binaries for Windows, Linux, and macOS.

=== ''[https://zeroonetwenty.com/blueharvest/ Blue Harvest]'' ===
: A convenient macOS tool to keep SD cards free from macOS metadata. Free 30-day trial.

=== ''[https://github.com/MrKWatkins/ZXSpectrumNextTests ZXSpectrumNextTests by Kevin Watkins and Peter Helcmanovsky]'' ===
: Suite of tests exercising various aspects of ZX Spectrum Next
: Tests for: Next registers, Copper, Sprites, Layer2, ULA modes, Extended ULA, Layers mixing modes, Z80N instructions, ...
: ASM Sources for each test (sjasmplus assembler syntax)

=== ''[https://github.com/Threetwosevensixseven/ZXSpectrumNextTests ZXSpectrumNextTests by Robin Verhagen-Guest]'' ===
: Suite of tests exercising various aspects of ZX Spectrum Next (yes, one more :) )
: Tests for: DMA, MMU paging, Layers mixing modes
: ASM Sources for each test (Zeus assembler syntax)

=== ''<div id="WASPtools" name="WASPtools">WASPtools by Phoebus Dokos</div>'' ===
WASPtools is a suite of tools comprised of a palette manipulator, a sprite editor, a graphics converter, and tilemap editor (both virtual tilemaps for say Layer2, and the hardware tilemap mode).

=== ''[https://zx.remysharp.com Online sprite, palette and tilemap editor by Remy Sharp]'' ===
: Browser based tooling that works fully offline
: Sprite editor with import and export tools
: Tile map editor with 16x16 and 8x8 tile support
: Full 512 palette import and export
: Also includes image conversion tools from PNG to 8 bit BMP and SL2 formats

=== ''[https://marketplace.visualstudio.com/items?itemName=remysharp.nextbasic NextBASIC extension for VS Code by Remy Sharp]'' ===
: Syntax highlighting, folding and definition jumping
: Export and import .bas to .txt and visa versa
: Inline help, line number completion and inline error checking
: Launches Cspect with minimal configuration

=== ''[https://www.specnext.com/forum/viewtopic.php?f=17&t=1715 NextSync WiFi file transferring by Jari Komppa]'' ===
: Run "server" code on your local PC (python 3 required)
: Run ".sync" on the Next
: Changed files will be copied from PC to Next by ESP WiFi module

Miscellaneous

2025-06-12T21:28:44Z

Orcmeal: Added info on Janko’s hdfmonkey fork, and on Blue Harvest.

=== ''[http://simon.mooli.org.uk/nextech/ Simon N Goodwin's Spectrum Next Page]'' ===
: A host of utilites for NextBasic written by Simon, NextPort, Nextramon,
: Next MGT Reader amongst other treasures.

=== ''[https://github.com/kounch/vscode_zx Visual Studio Code Tasks and Scripts]'' ===
: Some VSC goodies by kounch to work with NextBasic and ZX Basic

=== ''[https://github.com/stefanbylund/zxnext_bmp_tools Next BMP Tools]'' ===
: The Next BMP tools are BMP image conversion tools targeting the Sinclair ZX Spectrum Next written
: by Stefan Bylund

=== ''[https://wiki.twistedraven.net/index.php?title=Downloads Octarine Studio]'' ===
: Octarine Studio by Guy Black is a PC based editing tool that currently supports palettes and tiles.

=== ''[https://www.specnext.com/forum/viewtopic.php?f=7&t=351 UDGeedNext Sprite Editor]'' ===
: Windows based sprite editor written by some guy I have never heard of. Currently supports 8 bit
: palettes. 9 bit and 4 bit sprites should be added at some point....

=== ''[http://worldofpaul.com/speccyart/ Speccy Art]'' ===
: An online drawing experience that aims to help you create Sinclair ZX Spectrum-like images.
: Supports the classic ULA mode (256x192 pixels with 8x8 attribute squares and 15 classic ZX colours)
: Supports the Timex HiColour mode (256x192 pixels with 8x1 attribute rectangles and 15 classic ZX colours)
: Images can be saved and loaded through TAP files or exported into SCR/SHC files.

=== ''[https://github.com/varmfskii/zxnext_tools ZX Spectrum Next tools by Theodore (Alex) Evans]'' ===
: Multiple tools for various graphics conversions and processing
: zxnftp for transferring files between PC and Next via the ESP WiFi module

=== ''[https://gitlab.com/zxnexttools/nim Next Image Manipulator by Matt Davies]'' ===
: windows command line tool to convert various image and palette formats to custom "nip/nim" binary formats which are simple enough to parse (or include directly into source with assemblers supporting binary includes)
: this is early version (already working, build it from source), but further expansion to support also tiles/etc may happen in future

=== ''[https://github.com/gasman/hdfmonkey hdfmonkey]'' ===
: A Swiss Army Knife for working with FAT partitions on Spectrum emulator HDF images. Note: A more recent version of hdfmonkey maintained by Janko also supports the [https://www.specnext.com/latestdistro/ imperfect distribution images for emulators from specnext.com], and it includes executable binaries for Windows, macOS, and Linux. See [https://www.specnext.com/forum/viewtopic.php?p=16108 this hdfmonkey thread in the forum] for details.

=== ''[https://zeroonetwenty.com/blueharvest/ Blue Harvest]'' ===
: A convenient macOS tool to keep SD cards free from macOS metadata. Free 30-day trial.

=== ''[https://github.com/MrKWatkins/ZXSpectrumNextTests ZXSpectrumNextTests by Kevin Watkins and Peter Helcmanovsky]'' ===
: Suite of tests exercising various aspects of ZX Spectrum Next
: Tests for: Next registers, Copper, Sprites, Layer2, ULA modes, Extended ULA, Layers mixing modes, Z80N instructions, ...
: ASM Sources for each test (sjasmplus assembler syntax)

=== ''[https://github.com/Threetwosevensixseven/ZXSpectrumNextTests ZXSpectrumNextTests by Robin Verhagen-Guest]'' ===
: Suite of tests exercising various aspects of ZX Spectrum Next (yes, one more :) )
: Tests for: DMA, MMU paging, Layers mixing modes
: ASM Sources for each test (Zeus assembler syntax)

=== ''<div id="WASPtools" name="WASPtools">WASPtools by Phoebus Dokos</div>'' ===
WASPtools is a suite of tools comprised of a palette manipulator, a sprite editor, a graphics converter, and tilemap editor (both virtual tilemaps for say Layer2, and the hardware tilemap mode).

=== ''[https://zx.remysharp.com Online sprite, palette and tilemap editor by Remy Sharp]'' ===
: Browser based tooling that works fully offline
: Sprite editor with import and export tools
: Tile map editor with 16x16 and 8x8 tile support
: Full 512 palette import and export
: Also includes image conversion tools from PNG to 8 bit BMP and SL2 formats

=== ''[https://marketplace.visualstudio.com/items?itemName=remysharp.nextbasic NextBASIC extension for VS Code by Remy Sharp]'' ===
: Syntax highlighting, folding and definition jumping
: Export and import .bas to .txt and visa versa
: Inline help, line number completion and inline error checking
: Launches Cspect with minimal configuration

=== ''[https://www.specnext.com/forum/viewtopic.php?f=17&t=1715 NextSync WiFi file transferring by Jari Komppa]'' ===
: Run "server" code on your local PC (python 3 required)
: Run ".sync" on the Next
: Changed files will be copied from PC to Next by ESP WiFi module

Beeper (hardware)

2024-02-19T16:01:41Z

Orcmeal: Added heading to clarify that the speaker mod is for KS1 Nexts only

The Spectrum Next can create sound using [[Turbo Sound Next]] (3 AY-3-8912 sound chips) controlled by the BASIC PLAY keyword and the signal from these goes to the HDMI port or the 'ear' socket. Additionally an internal speaker can be connected which will generate sound in the same manner as the original 48k Spectrum, controlled via the BEEP keyword, which will also output via HDMI/ear.

A speaker attaches to connector J3 on the circuit board and requires a 2.54mm Pitch, 4 Way, 1 Row through-hole pin header. If you're fitting the board inside an original rubber key case, you'll probably need a right-angled connector due to the height required.

The buzzer should be approximately 1 inch diameter with impedance of 16 ohm (which should equate to a basic 'PC BIOS' piezo type speaker). J3 pins 1 and 2 are negative, pins 3 and 4 are positive.

=== Increasing Speaker Volume ===
'''This modification only works on Kickstarter 1 (= Issue 2B) Nexts. It is ''not'' for Kickstarter 2 (= Issue 4) boards.'''

On the Issue 2B boards, [https://www.specnext.com/forum/viewtopic.php?t=1860&hilit=beeper many users found the above speaker too quiet]. For higher volume levels, use an integrated amplifier/speaker board like the [https://www.adafruit.com/product/3885 Adafruit STEMMA Speaker] instead. A [https://www.adafruit.com/product/3893 3-pin JST PH 2.0 mm female header cable] makes disconnecting it again easy.

With the right settings (see below), this will give you roughly original ZX Spectrum sound levels, though '''only for the beeper used in the classic ZX Spectrum 16/48k'''. AY sound volume on 128k games like Dizzy 6 or Next games like Baggers In Space is still fairly low but serviceable in a quiet environment. DAC sound (like in the TX-1696 demo) remains too quiet to be usable; use HDMI or the 3.5 mm audio jack instead. To use an internal speaker with those types of audio, you will need a more powerful speaker and amplifier board (and possibly some way to adjust its volume as you switch between audio types).

[[File:ZX-Spectrum-Next-Internal-Adafruit-Speaker-Amplifier.jpg|thumb|center|An Adafruit STEMMA Speaker with integrated amplifier connected to the Spectrum Next Issue 2B motherboard and held in place inside the case with self-adhesive velcro strips. Cable colors do not reflect GND and Vcc correctly, but the cable sleeves do.]]

Solder GND to [[Circuit_Diagrams#J15_-_Next_GPIO|J15 pin 20]], Vcc to J15 pin 19, and the signal input to J3 pin 4 (next to the speaker holes on the Next PCB). Attach the speaker board to the Next case using two pieces of self-adhesive velcro. Place it next to the PCB and near the ZX Spectrum Expansion Connector. See the photo above.

Remove the Expansion Connector cover for more volume, and turn the potentiometer on the speaker board all the way up.

Turn on your Next while holding down SPACE to enter the TBBlue boot ROM menu. Here, toggle ''BEEPer'' to ''Int'' to increase its volume to roughly match the original ZX Spectrum for classic 16/48k "beeper" games (AY and DAC sound will not play through the internal speaker in this case). You can also disable the internal speaker here.

NextBASIC

2024-01-13T01:04:17Z

Orcmeal:

NextBASIC is an extended version of the classic Spectrum BASIC which adds extra commands supporting the new features of the NEXT.

? after parameters indicate they are optional. Square brackets [] indicate scope of optional or repeated areas (parentheses are not used for this because they are part of the BASIC language). Bracketed sections in the effects only apply if the optional parameters are specified.

== Basic Interaction Commands ==
{| class="wikitable"
! Command !! Effect
|-
| BANK b LINE x,y || Copies lines x,y into bank b. Once this is done, these lines cannot be edited except by overwriting them with another BANK..LINE command. Cannot be used in a program.
|-
| BANK b LIST x? || Lists source code in bank b (from line x)
|-
| BANK b MERGE || Adds all basic lines in bank b to main program
|-
| CONTINUE || Repeats last command or restarts from error location
|-
| CLEAR x? || Resets variables, clears screen, resets plot cursor (and sets ramtop to X)
|-
| ERASE f, l || Deletes all program lines between f and l. Cannot be used in a program.
|-
| LIST x? || Lists source code (from line x)
|-
| LLIST x? || Lists source code to printer (from line x)
|-
| NEW || Clear stored program
|-
| RUN x? || CLEAR then run program (from line x)
|}

== Control Flow ==
{| class="wikitable"
! Command !! Effect
|-
| BANK b GO TO x || Jump execution to line x stored in bank b. b=-1 for main program
|-
| BANK b GO SUB x || Jump execution to line x stored in bank b, storing current location on gosub stack. b=-1 for main program
|-
| DEF FN func(param[,param..])=expr || Creates a user defined function based on a parametrised expression. Will not work if moved into any bank other than the main program
|-
| DIM a(x[,y]..) || Defines a as an array of length x (and second dimension length y, etc..)
|-
| FOR var = start TO end [STEP step]? || Starts FOR loop between given numeric values (with given step)
|-
| GO TO x || Jump execution to line X in the same bank
|-
| GO SUB x || Jump execution to line X in the same bank, storing current location (and bank) on gosub stack
|-
| IF c THEN statements [ELSE statements] || Run statements only if expression c is true
|-
| LET var = expr || Sets variable var to expr
|-
| LOCAL var || Declares local variable
|-
| NEXT var || Marks end of FOR loop regarding VAR
|-
| REM comment || Code comment, ignored
|-
| REPEAT || Begin of loop
|-
| REPEAT UNTIL condition || Marks the end of REPEAT loop
|-
| RETURN || Restore execution location (line and bank) from gosub stack
|-
| WHILE condition || Condition for staying in loop
|}

== Console I/O ==
{| class="wikitable"
! Command !! Effect
|-
| COPY || Prints screen
|-
| INKEY$ || Returns currently pressed key
|-
| INPUT specifier [connector specifier].. || Output expression(s) and read a variable
|-
| INVERSE x || Enable or disable switching ink/paper color when printing (x=0 or 1)
|-
| LPRINT specifier [connector specifier].. || Output expression(s) to printer
|-
| OVER x || Enable or disable overprinting (x=0 or 1)
|-
| PAUSE x || Waits x frames or until a key is pressed
|-
| PRINT specifier [connector specifier].. || Output expression(s)
|}

Possible specifiers for PRINT and INPUT statements are:
{| class="wikitable"
! Specifier !! Effect
|-
| var || In PRINT, shows contents of var; in INPUT, inputs into this var
|-
| (var) || Shows contents of var (in both PRINT and INPUT)
|-
| AT x,y || Moves text cursor to the given text cell
|-
| TAB x || Inserts spaces until text cursor is in column x
|-
| INK x, PAPER x || Changes the appropriate color for the duration of the print/input statement
|-
| LINE x$ || INPUT only, reads a string without the prompting quotes
|-
| #x || Selects input/output channel number
|}

And the connectors between these are:
{| class="wikitable"
! Specifier !! Effect
|-
| , || Separate with a tab
|-
| ' || Separate with a newline
|-
| ; || Use no separator
|}

== File I/O ==

{| class="wikitable"
! Command !! Effect
|-
| CAT || Displays disk/tape catalogue
|-
| FORMAT || Prepares inserted disk for usage, erasing it
|-
| LOAD fn || Load BASIC program from file named fn
|-
| LOAD fn DATA x() || Load data from fn into array x()
|-
| LOAD fn CODE addr || Load data from fn into memory at address addr
|-
| LOAD fn SCREEN$ || Load data from fn onto standard ULA screen
|-
| LOAD fn BANK b,addr || Load data from fn into memory bank b at addr
|-
| LOAD fn LAYER || Load data from fn onto current layer
|-
| MERGE fn || Loads BASIC lines from file named fn and integrates them with current program
|-
| SAVE fn (LINE l)? || Save BASIC program to file named fn (and set up autorun at line l)
|-
| SAVE fn (DATA/CODE/SCREEN$/BANK/LAYER..) || Save data as specified; CODE and BANK have an extra "length" parameter
|-
| VERIFY fn || Checks loaded basic program matches fn
|-
| VERIFY fn (DATA/CODE/BANK) || Checks data in memory/array matches contents of fn; does not work with SCREEN$/LAYER because the screen is inevitably changed during the verify operation
|}

== Inline data ==
{| class="wikitable"
! Command !! Effect
|-
| BANK b RESTORE x || Sets DATA read point to start of line x in bank b
|-
| DATA x[,y].. || Stores data in program for later READing
|-
| READ var || Read next value from DATA statement into variable
|-
| RESTORE x || Sets DATA read point to start of line x
|}

== Graphics ==
{| class="wikitable"
! Command !! Effect
|-
| BORDER n || Set ULA border to color N
|-
| BRIGHT n || Enable or disable bright colors. n must be 0 or 1. Not legal on non-ULA layers or if Enhanced ULA is enabled.
|-
| CIRCLE x,y,r || Draw circle centered at x, y with radius r
|-
| CLS || Clears screen
|-
| DRAW [modifier or x,y].. || Draw line from plot cursor to given coordinate
|-
| FLASH n || Enable or disable ink/paper cycling. n must be 0 or 1. Not legal on non-ULA layers or if Enhanced ULA is enabled.
|-
| INK c || Set ink (foreground) color for print and graphics commands. If Enhanced ULA is enabled, this can use any legal palette value. On Layer 2, it can use any value 0-255.
|-
| LAYER x || Selects active layer for graphics operations. LAYER 0 is an unenhanced ULA screen. LAYER 1 is the ULA screen but with enhancements and with the origin at the top left (not the bottom left). LAYER 2 is, well, [[Layer 2]].
|-
| LAYER 1,x || Sets mode for Layer 1 based on x. 1 = Standard Spectrum, 2 = Timex hires, 3 = Timex hicolour, 0 = Lores layer.
|-
| LAYER 2,x || Selects [[Layer 2]] and determines if it is displayed or not (x must be 0 or 1)
|-
| LAYER AT x, y || Sets the scroll display offset for the current layer.
|-
| LAYER BANK f, b || Only when [[Layer 2]] is selected, selects the first bank for layer 2 (f) and shadow layer 2 (b). Note that a layer 2 screen occupies 3 banks.
|-
| LAYER CLEAR || Resets all layer settings
|-
| LAYER DIM left, top, right, bottom || Sets visible area for current layer
|-
| LAYER ERASE x, y, w, h [,f]? || Fills a region at x,y, of size w,h, with palette index f (or the transparent value)
|-
| LAYER OVER || Sets layer ordering
|-
| LAYER PALETTE x || Choose which of the two palettes is used for the active layer (x must be 0 or 1)
|-
| LAYER PALETTE n, i, v || Sets palette index i in palette in to color value v. V is always 9 bit, even if PALETTE DIM 8 is set.
|-
| LAYER PALETTE n BANK b, offset || Loads current layer's palette n (0 or 1) from bytes starting at offset in bank b. If PALETTE DIM 8 is set, each byte is one color. If PALETTE DIM 9 is set, each color needs two bytes, but only one bit of the second is used.
|-
| PALETTE CLEAR || Resets all palettes and palette settings
|-
| PALETTE DIM x || Sets number of color bits in the active palette; x must be 8 or 9
|-
| PALETTE FORMAT x || Enables Enhanced ULA colors with x inks. X must be a bitmask which masks off bits on the right of a value (1, 3, 7, 15, 31, 63, 127 or 255)
|-
| PALETTE OVER x || Sets the global transparency color to x
|-
| PAPER c || Set paper (background) color for print and graphics commands. Follows the same rules as INK.
|-
| PLOT [modifier or x,y].. || Plot listed points as single pixels on current layer
|-
| POINT x, y, var || Stores the color at point x, y '''on the ULA screen''' in variable var
|-
| POINT x, y || Returns the color at point x, y '''on the ULA screen'''
|}

Modifiers for graphics commands can be inline INK, PAPER, INVERSE, and OVER. INVERSE 1 causes drawing to be in the paper color. OVER 1 causes pixels in the line to be flipped.

=== Sprites ===
{| class="wikitable"
! Command !! Effect
|-
| SPRITE BANK x || Populates all 64 sprite patterns from bank b, taking 256 bytes per sprite and thus using all data in bank b.
|-
| SPRITE BANK b, o, p, n || Define n sprite patterns, starting with p, with data from bank b starting at offset o.
|-
| SPRITE PALETTE x || Choose the first or second palette for sprites. X must be 0 or 1.
|-
| SPRITE PALETTE x BANK b, o || Load sprite palette x (0 or 1) from bank b at offset o. Data is read as with LAYER PALETTE.
|-
| SPRITE PALETTE n, i, v || Set sprite palette n, index i, to color v. V is always 9-bit, even if PALETTE DIM 8 is in effect.
|-
| SPRITE PRINT x || Enable or disable sprites. X must be 0 (disable) or 1 (enable).
|-
| SPRITE BORDER x || Enable or disable sprites crossing the border. X must be 0 (disable) or 1 (enable).
|-
| SPRITE s, x, y, i, f || Set sprite f to image i at position x,y with flags f. f is bitmapped as byte 3 of data packets sent to {{PortNo|$xx57}}.
|-
| SPRITE CLEAR || Reset all sprite attributes and global settings.
|}

=== Tilemap support ===

=== Sprites ===
{| class="wikitable"
! Command !! Effect
|-
| TILE [AT x,y]? || Draw the entire screen from the tilemap (from tile offset (x,y))
|-
| TILE w,h [AT x,y]? [TO x2,y2]? || Draw a section of the tilemap w,h wide (from tile offset x,y in the tilemap) (to tile offset x2,y2 on the screen)
|-
| TILE BANK n || Set bank n as the root of tile graphics (which may occupy up to 4 banks in the case of 16x16 tiles).
|-
| TILE DIM n, o, v, t || Set bank n offset o as the root of tilemap data, with tilemap width v and tile size t (t must be 8 or 16 for 8x8 or 16x16 tiles)
|}

== Memory and Port Access ==
{| class="wikitable"
! Command !! Effect
|-
| BANK 1346 FORMAT || Re-enable RAMdisk having been disabled by previous BANK 1346 USR
|-
| BANK 1346 USR || Disable RAMdisk, allowing banks 1, 3, 4, and 6 to be used
|-
| BANK b COPY TO c || Copy entire bank b to bank c
|-
| BANK b COPY start, len TO c, start || Copy len bytes from start in bank b, to start in bank c
|-
| BANK b ERASE x? || Erase all data in bank by overwriting with zeros (or x)
|-
| BANK b ERASE off, len, value || Overwrite len bytes of data at off in bank b with value
|-
| BANK b PEEK addr || Returns value at given address in bank b (address is from start of bank)
|-
| BANK b POKE addr, value || Sets address in bank b to value (address is from start of bank)
|-
| IN port || Returns current value at port
|-
| PEEK addr || Returns value at given address
|-
| POKE addr, value || Sets address to value
|-
| OUT port, value || Sends value to port
|-
| REG r [, v]? || Return the value in NextReg register r (or set it to value v if provided)
|}

== Functions/Expressions ==
{| class="wikitable"
! Command !! Effect
|-
| + - * / ^ || Standard arithmetic operators
|-
| = < > <= >= <> || Standard comparison operators (arithmetic for numbers, alphabetic for strings)
|-
| a(x) || Returns x'th element of array/string a
|-
| s(x? TO y?) || Return substring of s; if x or y are omitted, start or end is assumed
|-
| AND OR NOT || Standard boolean conjunctives
|-
| ABS x || Gets unsigned magnitude of x
|-
| ASN x, ACS x, ATN x || Returns inverse trigonometric ratio (arcsin, arccos, arctan)
|-
| ATTR x,y || Returns attribute cell value at cell x,y
|-
| BIN x || Converts binary number x to decimal
|-
| CHR$ x || Gets character for an ASCII code
|-
| CODE x || Gets ASCII code for a character
|-
| INT x || Rounds x down to integer
|-
| LEN x || Gets length of string
|-
| PI || Returns approximation of pi
|-
| RND || Returns a random number between 0 and 1
|-
| SCREEN$ x,y || Returns text character in text cell x,y
|-
| SIGN x || Divides x by its magnitude
|-
| SIN x, COS x, TAN x || Returns standard trigonometric ratio
|-
| SQR x || Returns square of x
|-
| STR$ x || Converts number into a string
|-
| USR x || If x is a string, gets the address of the first byte of the user defined graphic for the character. If x is a number, runs a machine code routine at address x and returns the value of BC after it exits.
|-
| VAL x || Converts string number or expression into a number
|}

== Basic Tokens ==
{| class="wikitable"
! Value (hex) !! Token
|-
| 0x87 || PEEK$
|-
| 0x88 || REG
|-
| 0x89 || DPOKE
|-
| 0x8a || DPEEK
|-
| 0x8b || MOD
|-
| 0x8c || <<
|-
| 0x8d || >>
|-
| 0x8e || UNTIL
|-
| 0x8f || ERROR
|-
| 0x90 || ON
|-
| 0x91 || DEFPROC
|-
| 0x92 || ENDPROC
|-
| 0x93 || PROC
|-
| 0x94 || LOCAL
|-
| 0x95 || DRIVER
|-
| 0x96 || WHILE
|-
| 0x97 || REPEAT
|-
| 0x98 || ELSE
|-
| 0x99 || REMOUNT
|-
| 0x9a || BANK
|-
| 0x9b || TILE
|-
| 0x9c || LAYER
|-
| 0x9d || PALETTE
|-
| 0x9e || SPRITE
|-
| 0x9f || PWD
|-
| 0xa0 || CD
|-
| 0xa1 || MKDIR
|-
| 0xa2 || RMDIR
|-
| 0xA3 || SPECTRUM
|-
| 0xA4 || PLAY
|-
| 0xA5 || RND
|-
| 0xA6 || INKEY$
|-
| 0xA7 || PI
|-
| 0xA8 || FN
|-
| 0xA9 || POINT
|-
| 0xAA || SCREEN$
|-
| 0xAB || ATTR
|-
| 0xAC || AT
|-
| 0xAD || TAB
|-
| 0xAE || VAL$
|-
| 0xAF || CODE
|-
| 0xB0 || VAL
|-
| 0xB1 || LEN
|-
| 0xB2 || SIN
|-
| 0xB3 || COS
|-
| 0xB4 || TAN
|-
| 0xB5 || ASN
|-
| 0xB6 || ACS
|-
| 0xB7 || ATN
|-
| 0xB8 || LN
|-
| 0xB9 || EXP
|-
| 0xBA || INT
|-
| 0xBB || SQR
|-
| 0xBC || SGN
|-
| 0xBD || ABS
|-
| 0xBE || PEEK
|-
| 0xBF || IN
|-
| 0xC0 || USR
|-
| 0xC1 || STR$
|-
| 0xC2 || CHR$
|-
| 0xC3 || NOT
|-
| 0xC4 || BIN
|-
| 0xC5 || OR
|-
| 0xC6 || AND
|-
| 0xC7 || <=
|-
| 0xC8 || >=
|-
| 0xC9 || <>
|-
| 0xCA || LINE
|-
| 0xCB || THEN
|-
| 0xCC || TO
|-
| 0xCD || STEP
|-
| 0xCE || DEF FN
|-
| 0xCF || CAT
|-
| 0xD0 || FORMAT
|-
| 0xD1 || MOVE
|-
| 0xD2 || ERASE
|-
| 0xD3 || OPEN #
|-
| 0xD4 || CLOSE #
|-
| 0xD5 || MERGE
|-
| 0xD6 || VERIFY
|-
| 0xD7 || BEEP
|-
| 0xD8 || CIRCLE
|-
| 0xD9 || INK
|-
| 0xDA || PAPER
|-
| 0xDB || FLASH
|-
| 0xDC || BRIGHT
|-
| 0xDD || INVERSE
|-
| 0xDE || OVER
|-
| 0xDF || OUT
|-
| 0xE0 || LPRINT
|-
| 0xE1 || LLIST
|-
| 0xE2 || STOP
|-
| 0xE3 || READ
|-
| 0xE4 || DATA
|-
| 0xE5 || RESTORE
|-
| 0xE6 || NEW
|-
| 0xE7 || BORDER
|-
| 0xE8 || CONTINUE
|-
| 0xE9 || DIM
|-
| 0xEA || REM
|-
| 0xEB || FOR
|-
| 0xEC || GO TO
|-
| 0xED || GO SUB
|-
| 0xEE || INPUT
|-
| 0xEF || LOAD
|-
| 0xF0 || LIST
|-
| 0xF1 || LET
|-
| 0xF2 || PAUSE
|-
| 0xF3 || NEXT
|-
| 0xF4 || POKE
|-
| 0xF5 || PRINT
|-
| 0xF6 || PLOT
|-
| 0xF7 || RUN
|-
| 0xF8 || SAVE
|-
| 0xF9 || RANDOMIZE
|-
| 0xFA || IF
|-
| 0xFB || CLS
|-
| 0xFC || DRAW
|-
| 0xFD || CLEAR
|-
| 0xFE || RETURN
|-
| 0xFF || COPY
|}

NextBASIC

2024-01-13T00:04:09Z

Orcmeal: Added REG command under "Memory and Port Access"

NextBASIC is an extended version of the classic Spectrum BASIC which adds extra commands supporting the new features of the NEXT.

? after parameters indicate they are optional. Square brackets [] indicate scope of optional or repeated areas (parentheses are not used for this because they are part of the BASIC language). Bracketed sections in the effects only apply if the optional parameters are specified.

== Basic Interaction Commands ==
{| class="wikitable"
! Command !! Effect
|-
| BANK b LINE x,y || Copies lines x,y into bank b. Once this is done, these lines cannot be edited except by overwriting them with another BANK..LINE command. Cannot be used in a program.
|-
| BANK b LIST x? || Lists source code in bank b (from line x)
|-
| BANK b MERGE || Adds all basic lines in bank b to main program
|-
| CONTINUE || Repeats last command or restarts from error location
|-
| CLEAR x? || Resets variables, clears screen, resets plot cursor (and sets ramtop to X)
|-
| ERASE f, l || Deletes all program lines between f and l. Cannot be used in a program.
|-
| LIST x? || Lists source code (from line x)
|-
| LLIST x? || Lists source code to printer (from line x)
|-
| NEW || Clear stored program
|-
| RUN x? || CLEAR then run program (from line x)
|}

== Control Flow ==
{| class="wikitable"
! Command !! Effect
|-
| BANK b GO TO x || Jump execution to line x stored in bank b. b=-1 for main program
|-
| BANK b GO SUB x || Jump execution to line x stored in bank b, storing current location on gosub stack. b=-1 for main program
|-
| DEF FN func(param[,param..])=expr || Creates a user defined function based on a parametrised expression. Will not work if moved into any bank other than the main program
|-
| DIM a(x[,y]..) || Defines a as an array of length x (and second dimension length y, etc..)
|-
| FOR var = start TO end [STEP step]? || Starts FOR loop between given numeric values (with given step)
|-
| GO TO x || Jump execution to line X in the same bank
|-
| GO SUB x || Jump execution to line X in the same bank, storing current location (and bank) on gosub stack
|-
| IF c THEN statements [ELSE statements] || Run statements only if expression c is true
|-
| LET var = expr || Sets variable var to expr
|-
| LOCAL var || Declares local variable
|-
| NEXT var || Marks end of FOR loop regarding VAR
|-
| REM comment || Code comment, ignored
|-
| REPEAT || Begin of loop
|-
| REPEAT UNTIL condition || Marks the end of REPEAT loop
|-
| RETURN || Restore execution location (line and bank) from gosub stack
|-
| WHILE condition || Condition for staying in loop
|}

== Console I/O ==
{| class="wikitable"
! Command !! Effect
|-
| COPY || Prints screen
|-
| INKEY$ || Returns currently pressed key
|-
| INPUT specifier [connector specifier].. || Output expression(s) and read a variable
|-
| INVERSE x || Enable or disable switching ink/paper color when printing (x=0 or 1)
|-
| LPRINT specifier [connector specifier].. || Output expression(s) to printer
|-
| OVER x || Enable or disable overprinting (x=0 or 1)
|-
| PAUSE x || Waits x frames or until a key is pressed
|-
| PRINT specifier [connector specifier].. || Output expression(s)
|}

Possible specifiers for PRINT and INPUT statements are:
{| class="wikitable"
! Specifier !! Effect
|-
| var || In PRINT, shows contents of var; in INPUT, inputs into this var
|-
| (var) || Shows contents of var (in both PRINT and INPUT)
|-
| AT x,y || Moves text cursor to the given text cell
|-
| TAB x || Inserts spaces until text cursor is in column x
|-
| INK x, PAPER x || Changes the appropriate color for the duration of the print/input statement
|-
| LINE x$ || INPUT only, reads a string without the prompting quotes
|-
| #x || Selects input/output channel number
|}

And the connectors between these are:
{| class="wikitable"
! Specifier !! Effect
|-
| , || Separate with a tab
|-
| ' || Separate with a newline
|-
| ; || Use no separator
|}

== File I/O ==

{| class="wikitable"
! Command !! Effect
|-
| CAT || Displays disk/tape catalogue
|-
| FORMAT || Prepares inserted disk for usage, erasing it
|-
| LOAD fn || Load BASIC program from file named fn
|-
| LOAD fn DATA x() || Load data from fn into array x()
|-
| LOAD fn CODE addr || Load data from fn into memory at address addr
|-
| LOAD fn SCREEN$ || Load data from fn onto standard ULA screen
|-
| LOAD fn BANK b,addr || Load data from fn into memory bank b at addr
|-
| LOAD fn LAYER || Load data from fn onto current layer
|-
| MERGE fn || Loads BASIC lines from file named fn and integrates them with current program
|-
| SAVE fn (LINE l)? || Save BASIC program to file named fn (and set up autorun at line l)
|-
| SAVE fn (DATA/CODE/SCREEN$/BANK/LAYER..) || Save data as specified; CODE and BANK have an extra "length" parameter
|-
| VERIFY fn || Checks loaded basic program matches fn
|-
| VERIFY fn (DATA/CODE/BANK) || Checks data in memory/array matches contents of fn; does not work with SCREEN$/LAYER because the screen is inevitably changed during the verify operation
|}

== Inline data ==
{| class="wikitable"
! Command !! Effect
|-
| BANK b RESTORE x || Sets DATA read point to start of line x in bank b
|-
| DATA x[,y].. || Stores data in program for later READing
|-
| READ var || Read next value from DATA statement into variable
|-
| RESTORE x || Sets DATA read point to start of line x
|}

== Graphics ==
{| class="wikitable"
! Command !! Effect
|-
| BORDER n || Set ULA border to color N
|-
| BRIGHT n || Enable or disable bright colors. n must be 0 or 1. Not legal on non-ULA layers or if Enhanced ULA is enabled.
|-
| CIRCLE x,y,r || Draw circle centered at x, y with radius r
|-
| CLS || Clears screen
|-
| DRAW [modifier or x,y].. || Draw line from plot cursor to given coordinate
|-
| FLASH n || Enable or disable ink/paper cycling. n must be 0 or 1. Not legal on non-ULA layers or if Enhanced ULA is enabled.
|-
| INK c || Set ink (foreground) color for print and graphics commands. If Enhanced ULA is enabled, this can use any legal palette value. On Layer 2, it can use any value 0-255.
|-
| LAYER x || Selects active layer for graphics operations. LAYER 0 is an unenhanced ULA screen. LAYER 1 is the ULA screen but with enhancements and with the origin at the top left (not the bottom left). LAYER 2 is, well, [[Layer 2]].
|-
| LAYER 1,x || Sets mode for Layer 1 based on x. 1 = Standard Spectrum, 2 = Timex hires, 3 = Timex hicolour, 0 = Lores layer.
|-
| LAYER 2,x || Selects [[Layer 2]] and determines if it is displayed or not (x must be 0 or 1)
|-
| LAYER AT x, y || Sets the scroll display offset for the current layer.
|-
| LAYER BANK f, b || Only when [[Layer 2]] is selected, selects the first bank for layer 2 (f) and shadow layer 2 (b). Note that a layer 2 screen occupies 3 banks.
|-
| LAYER CLEAR || Resets all layer settings
|-
| LAYER DIM left, top, right, bottom || Sets visible area for current layer
|-
| LAYER ERASE x, y, w, h [,f]? || Fills a region at x,y, of size w,h, with palette index f (or the transparent value)
|-
| LAYER OVER || Sets layer ordering
|-
| LAYER PALETTE x || Choose which of the two palettes is used for the active layer (x must be 0 or 1)
|-
| LAYER PALETTE n, i, v || Sets palette index i in palette in to color value v. V is always 9 bit, even if PALETTE DIM 8 is set.
|-
| LAYER PALETTE n BANK b, offset || Loads current layer's palette n (0 or 1) from bytes starting at offset in bank b. If PALETTE DIM 8 is set, each byte is one color. If PALETTE DIM 9 is set, each color needs two bytes, but only one bit of the second is used.
|-
| PALETTE CLEAR || Resets all palettes and palette settings
|-
| PALETTE DIM x || Sets number of color bits in the active palette; x must be 8 or 9
|-
| PALETTE FORMAT x || Enables Enhanced ULA colors with x inks. X must be a bitmask which masks off bits on the right of a value (1, 3, 7, 15, 31, 63, 127 or 255)
|-
| PALETTE OVER x || Sets the global transparency color to x
|-
| PAPER c || Set paper (background) color for print and graphics commands. Follows the same rules as INK.
|-
| PLOT [modifier or x,y].. || Plot listed points as single pixels on current layer
|-
| POINT x, y, var || Stores the color at point x, y '''on the ULA screen''' in variable var
|-
| POINT x, y || Returns the color at point x, y '''on the ULA screen'''
|}

Modifiers for graphics commands can be inline INK, PAPER, INVERSE, and OVER. INVERSE 1 causes drawing to be in the paper color. OVER 1 causes pixels in the line to be flipped.

=== Sprites ===
{| class="wikitable"
! Command !! Effect
|-
| SPRITE BANK x || Populates all 64 sprite patterns from bank b, taking 256 bytes per sprite and thus using all data in bank b.
|-
| SPRITE BANK b, o, p, n || Define n sprite patterns, starting with p, with data from bank b starting at offset o.
|-
| SPRITE PALETTE x || Choose the first or second palette for sprites. X must be 0 or 1.
|-
| SPRITE PALETTE x BANK b, o || Load sprite palette x (0 or 1) from bank b at offset o. Data is read as with LAYER PALETTE.
|-
| SPRITE PALETTE n, i, v || Set sprite palette n, index i, to color v. V is always 9-bit, even if PALETTE DIM 8 is in effect.
|-
| SPRITE PRINT x || Enable or disable sprites. X must be 0 (disable) or 1 (enable).
|-
| SPRITE BORDER x || Enable or disable sprites crossing the border. X must be 0 (disable) or 1 (enable).
|-
| SPRITE s, x, y, i, f || Set sprite f to image i at position x,y with flags f. f is bitmapped as byte 3 of data packets sent to {{PortNo|$xx57}}.
|-
| SPRITE CLEAR || Reset all sprite attributes and global settings.
|}

=== Tilemap support ===

=== Sprites ===
{| class="wikitable"
! Command !! Effect
|-
| TILE [AT x,y]? || Draw the entire screen from the tilemap (from tile offset (x,y))
|-
| TILE w,h [AT x,y]? [TO x2,y2]? || Draw a section of the tilemap w,h wide (from tile offset x,y in the tilemap) (to tile offset x2,y2 on the screen)
|-
| TILE BANK n || Set bank n as the root of tile graphics (which may occupy up to 4 banks in the case of 16x16 tiles).
|-
| TILE DIM n, o, v, t || Set bank n offset o as the root of tilemap data, with tilemap width v and tile size t (t must be 8 or 16 for 8x8 or 16x16 tiles)
|}

== Memory and Port Access ==
{| class="wikitable"
! Command !! Effect
|-
| BANK 1346 FORMAT || Re-enable RAMdisk having been disabled by previous BANK 1346 USR
|-
| BANK 1346 USR || Disable RAMdisk, allowing banks 1, 3, 4, and 6 to be used
|-
| BANK b COPY TO c || Copy entire bank b to bank c
|-
| BANK b COPY start, len TO c, start || Copy len bytes from start in bank b, to start in bank c
|-
| BANK b ERASE x? || Erase all data in bank by overwriting with zeros (or x)
|-
| BANK b ERASE off, len, value || Overwrite len bytes of data at off in bank b with value
|-
| BANK b PEEK addr || Returns value at given address in bank b (address is from start of bank)
|-
| BANK b POKE addr, value || Sets address in bank b to value (address is from start of bank)
|-
| IN port || Returns current value at port
|-
| PEEK addr || Returns value at given address
|-
| POKE addr, value || Sets address to value
|-
| OUT port, value || Sends value to port
|-
| REG r, v? || Return the value in NextReg register r (or set it to value v if provided)
|}

== Functions/Expressions ==
{| class="wikitable"
! Command !! Effect
|-
| + - * / ^ || Standard arithmetic operators
|-
| = < > <= >= <> || Standard comparison operators (arithmetic for numbers, alphabetic for strings)
|-
| a(x) || Returns x'th element of array/string a
|-
| s(x? TO y?) || Return substring of s; if x or y are omitted, start or end is assumed
|-
| AND OR NOT || Standard boolean conjunctives
|-
| ABS x || Gets unsigned magnitude of x
|-
| ASN x, ACS x, ATN x || Returns inverse trigonometric ratio (arcsin, arccos, arctan)
|-
| ATTR x,y || Returns attribute cell value at cell x,y
|-
| BIN x || Converts binary number x to decimal
|-
| CHR$ x || Gets character for an ASCII code
|-
| CODE x || Gets ASCII code for a character
|-
| INT x || Rounds x down to integer
|-
| LEN x || Gets length of string
|-
| PI || Returns approximation of pi
|-
| RND || Returns a random number between 0 and 1
|-
| SCREEN$ x,y || Returns text character in text cell x,y
|-
| SIGN x || Divides x by its magnitude
|-
| SIN x, COS x, TAN x || Returns standard trigonometric ratio
|-
| SQR x || Returns square of x
|-
| STR$ x || Converts number into a string
|-
| USR x || If x is a string, gets the address of the first byte of the user defined graphic for the character. If x is a number, runs a machine code routine at address x and returns the value of BC after it exits.
|-
| VAL x || Converts string number or expression into a number
|}

== Basic Tokens ==
{| class="wikitable"
! Value (hex) !! Token
|-
| 0x87 || PEEK$
|-
| 0x88 || REG
|-
| 0x89 || DPOKE
|-
| 0x8a || DPEEK
|-
| 0x8b || MOD
|-
| 0x8c || <<
|-
| 0x8d || >>
|-
| 0x8e || UNTIL
|-
| 0x8f || ERROR
|-
| 0x90 || ON
|-
| 0x91 || DEFPROC
|-
| 0x92 || ENDPROC
|-
| 0x93 || PROC
|-
| 0x94 || LOCAL
|-
| 0x95 || DRIVER
|-
| 0x96 || WHILE
|-
| 0x97 || REPEAT
|-
| 0x98 || ELSE
|-
| 0x99 || REMOUNT
|-
| 0x9a || BANK
|-
| 0x9b || TILE
|-
| 0x9c || LAYER
|-
| 0x9d || PALETTE
|-
| 0x9e || SPRITE
|-
| 0x9f || PWD
|-
| 0xa0 || CD
|-
| 0xa1 || MKDIR
|-
| 0xa2 || RMDIR
|-
| 0xA3 || SPECTRUM
|-
| 0xA4 || PLAY
|-
| 0xA5 || RND
|-
| 0xA6 || INKEY$
|-
| 0xA7 || PI
|-
| 0xA8 || FN
|-
| 0xA9 || POINT
|-
| 0xAA || SCREEN$
|-
| 0xAB || ATTR
|-
| 0xAC || AT
|-
| 0xAD || TAB
|-
| 0xAE || VAL$
|-
| 0xAF || CODE
|-
| 0xB0 || VAL
|-
| 0xB1 || LEN
|-
| 0xB2 || SIN
|-
| 0xB3 || COS
|-
| 0xB4 || TAN
|-
| 0xB5 || ASN
|-
| 0xB6 || ACS
|-
| 0xB7 || ATN
|-
| 0xB8 || LN
|-
| 0xB9 || EXP
|-
| 0xBA || INT
|-
| 0xBB || SQR
|-
| 0xBC || SGN
|-
| 0xBD || ABS
|-
| 0xBE || PEEK
|-
| 0xBF || IN
|-
| 0xC0 || USR
|-
| 0xC1 || STR$
|-
| 0xC2 || CHR$
|-
| 0xC3 || NOT
|-
| 0xC4 || BIN
|-
| 0xC5 || OR
|-
| 0xC6 || AND
|-
| 0xC7 || <=
|-
| 0xC8 || >=
|-
| 0xC9 || <>
|-
| 0xCA || LINE
|-
| 0xCB || THEN
|-
| 0xCC || TO
|-
| 0xCD || STEP
|-
| 0xCE || DEF FN
|-
| 0xCF || CAT
|-
| 0xD0 || FORMAT
|-
| 0xD1 || MOVE
|-
| 0xD2 || ERASE
|-
| 0xD3 || OPEN #
|-
| 0xD4 || CLOSE #
|-
| 0xD5 || MERGE
|-
| 0xD6 || VERIFY
|-
| 0xD7 || BEEP
|-
| 0xD8 || CIRCLE
|-
| 0xD9 || INK
|-
| 0xDA || PAPER
|-
| 0xDB || FLASH
|-
| 0xDC || BRIGHT
|-
| 0xDD || INVERSE
|-
| 0xDE || OVER
|-
| 0xDF || OUT
|-
| 0xE0 || LPRINT
|-
| 0xE1 || LLIST
|-
| 0xE2 || STOP
|-
| 0xE3 || READ
|-
| 0xE4 || DATA
|-
| 0xE5 || RESTORE
|-
| 0xE6 || NEW
|-
| 0xE7 || BORDER
|-
| 0xE8 || CONTINUE
|-
| 0xE9 || DIM
|-
| 0xEA || REM
|-
| 0xEB || FOR
|-
| 0xEC || GO TO
|-
| 0xED || GO SUB
|-
| 0xEE || INPUT
|-
| 0xEF || LOAD
|-
| 0xF0 || LIST
|-
| 0xF1 || LET
|-
| 0xF2 || PAUSE
|-
| 0xF3 || NEXT
|-
| 0xF4 || POKE
|-
| 0xF5 || PRINT
|-
| 0xF6 || PLOT
|-
| 0xF7 || RUN
|-
| 0xF8 || SAVE
|-
| 0xF9 || RANDOMIZE
|-
| 0xFA || IF
|-
| 0xFB || CLS
|-
| 0xFC || DRAW
|-
| 0xFD || CLEAR
|-
| 0xFE || RETURN
|-
| 0xFF || COPY
|}

Beeper (hardware)

2023-09-06T07:20:38Z

Orcmeal: Added note on low DAC volume and need for even more powerful amps. Clarified boot rom options.

The Spectrum Next can create sound using [[Turbo Sound Next]] (3 AY-3-8912 sound chips) controlled by the BASIC PLAY keyword and the signal from these goes to the HDMI port or the 'ear' socket. Additionally an internal speaker can be connected which will generate sound in the same manner as the original 48k Spectrum, controlled via the BEEP keyword, which will also output via HDMI/ear.

A speaker attaches to connector J3 on the circuit board and requires a 2.54mm Pitch, 4 Way, 1 Row through-hole pin header. If you're fitting the board inside an original rubber key case, you'll probably need a right-angled connector due to the height required.

The buzzer should be approximately 1 inch diameter with impedance of 16 ohm (which should equate to a basic 'PC BIOS' piezo type speaker). J3 pins 1 and 2 are negative, pins 3 and 4 are positive.

On the Issue 2B boards, [https://www.specnext.com/forum/viewtopic.php?t=1860&hilit=beeper many users found the above speaker too quiet]. For higher volume levels, use an integrated amplifier/speaker board like the [https://www.adafruit.com/product/3885 Adafruit STEMMA Speaker] instead. A [https://www.adafruit.com/product/3893 3-pin JST PH 2.0 mm female header cable] makes disconnecting it again easy.

With the right settings (see below), this will give you roughly original ZX Spectrum sound levels, though only '''for the beeper used in the classic ZX Spectrum 16/48k'''. AY sound volume on 128k games like Dizzy 6 or Next games like Baggers In Space is still fairly low but serviceable in a quiet environment. DAC sound (like in the TX-1696 demo) remains too quiet to be usable; use HDMI or the 3.5 mm audio jack instead. To use an internal speaker with those types of audio, you will need a more powerful speaker and amplifier board (and possibly some way to adjust its volume as you switch between audio types).

[[File:ZX-Spectrum-Next-Internal-Adafruit-Speaker-Amplifier.jpg|thumb|center|An Adafruit STEMMA Speaker with integrated amplifier connected to the Spectrum Next Issue 2B motherboard and held in place inside the case with self-adhesive velcro strips. Cable colors do not reflect GND and Vcc correctly, but the cable sleeves do.]]

Solder GND to [[Circuit_Diagrams#J15_-_Next_GPIO|J15 pin 20]], Vcc to J15 pin 19, and the signal input to J3 pin 4 (next to the speaker holes on the Next PCB). Attach the speaker board to the Next case using two pieces of self-adhesive velcro. Place it next to the PCB and near the ZX Spectrum Expansion Connector. See the photo above.

Remove the Expansion Connector cover for more volume, and turn the potentiometer on the speaker board all the way up.

Turn on your Next while holding down SPACE to enter the TBBlue boot ROM menu. Here, toggle ''BEEPer'' to ''Int'' to increase its volume to roughly match the original ZX Spectrum for classic 16/48k "beeper" games (AY and DAC sound will not play through the internal speaker in this case). You can also disable the internal speaker here.

Beeper (hardware)

2023-09-02T08:42:07Z

Orcmeal: Added info on low volume for AY sound even with amp board

The Spectrum Next can create sound using [[Turbo Sound Next]] (3 AY-3-8912 sound chips) controlled by the BASIC PLAY keyword and the signal from these goes to the HDMI port or the 'ear' socket. Additionally an internal speaker can be connected which will generate sound in the same manner as the original 48k Spectrum, controlled via the BEEP keyword, which will also output via HDMI/ear.

A speaker attaches to connector J3 on the circuit board and requires a 2.54mm Pitch, 4 Way, 1 Row through-hole pin header. If you're fitting the board inside an original rubber key case, you'll probably need a right-angled connector due to the height required.

The buzzer should be approximately 1 inch diameter with impedance of 16 ohm (which should equate to a basic 'PC BIOS' piezo type speaker). J3 pins 1 and 2 are negative, pins 3 and 4 are positive.

On the Issue 2B boards, [https://www.specnext.com/forum/viewtopic.php?t=1860&hilit=beeper many users found the above speaker too quiet]. For higher volume levels, use an integrated amplifier/speaker board like the [https://www.adafruit.com/product/3885 Adafruit STEMMA Speaker] instead. A [https://www.adafruit.com/product/3893 3-pin JST PH 2.0 mm female header cable] makes disconnecting it again easy.

With the right settings (see below), this will give you roughly original ZX Spectrum sound levels for the beeper used in the classic ZX Spectrum 16/48k. AY sound volume on 128k games like Dizzy 6 or Next games like Baggers In Space is still fairly low but serviceable in a quiet environment.

[[File:ZX-Spectrum-Next-Internal-Adafruit-Speaker-Amplifier.jpg|thumb|center|An Adafruit STEMMA Speaker with integrated amplifier connected to the Spectrum Next Issue 2B motherboard and held in place inside the case with self-adhesive velcro strips. Cable colors do not reflect GND and Vcc correctly, but the cable sleeves do.]]

Solder GND to [[Circuit_Diagrams#J15_-_Next_GPIO|J15 pin 20]], Vcc to J15 pin 19, and the signal input to J3 pin 4 next to the speaker holes on the PCB. Attach the speaker board to the Next case using two pieces of self-adhesive velcro. Place it next to the PCB and near the ZX Spectrum Expansion Connector. See the photo above.

Remove the Expansion Connector cover for more volume, and turn the potentiometer on the speaker board all the way up.

If you hold down SPACE after power cycling, you enter the TBBlue boot ROM menu. Here you can disable the internal speaker or, if you play classic 16/48k games that don't use AY sound, toggle ''BEEPer'' to ''Int'' to increase its volume to roughly match the original ZX Spectrum.

Beeper (hardware)

2023-08-31T19:59:53Z

Orcmeal: Added information on how to enter boot menu, and how to increase volume by setting "BEEPer" to "Int".

The Spectrum Next can create sound using [[Turbo Sound Next]] (3 AY-3-8912 sound chips) controlled by the BASIC PLAY keyword and the signal from these goes to the HDMI port or the 'ear' socket. Additionally an internal speaker can be connected which will generate sound in the same manner as the original 48k Spectrum, controlled via the BEEP keyword, which will also output via HDMI/ear.

A speaker attaches to connector J3 on the circuit board and requires a 2.54mm Pitch, 4 Way, 1 Row through-hole pin header. If you're fitting the board inside an original rubber key case, you'll probably need a right-angled connector due to the height required.

The buzzer should be approximately 1 inch diameter with impedance of 16 ohm (which should equate to a basic 'PC BIOS' piezo type speaker). J3 pins 1 and 2 are negative, pins 3 and 4 are positive.

On the Issue 2B boards, [https://www.specnext.com/forum/viewtopic.php?t=1860&hilit=beeper many users found the above speaker too quiet]. For volume levels similar to the original ZX Spectrum, use an integrated amplifier/speaker board like the [https://www.adafruit.com/product/3885 Adafruit STEMMA Speaker] instead. A [https://www.adafruit.com/product/3893 3-pin JST PH 2.0 mm female header cable] makes disconnecting it again easy.

[[File:ZX-Spectrum-Next-Internal-Adafruit-Speaker-Amplifier.jpg|thumb|center|An Adafruit STEMMA Speaker with integrated amplifier connected to the Spectrum Next Issue 2B motherboard and held in place inside the case with self-adhesive velcro strips. Cable colors do not reflect GND and Vcc correctly, but the cable sleeves do.]]

Solder GND to [[Circuit_Diagrams#J15_-_Next_GPIO|J15 pin 20]], Vcc to J15 pin 19, and the signal input to J3 pin 4 next to the speaker holes on the PCB. Attach the speaker board to the Next case using two pieces of self-adhesive velcro. Place it next to the PCB and near the ZX Spectrum Expansion Connector. See the photo above.

Remove the Expansion Connector cover for more volume, and turn the potentiometer on the speaker board all the way up.

If you hold down SPACE after power cycling, you enter the TBBlue boot ROM menu. Here you can disable the internal speaker or, if you play classic 16/48k games that don't use AY sound, toggle ''BEEPer'' to ''Int'' to increase its volume to roughly match the original ZX Spectrum.

Beeper (hardware)

2023-08-30T20:19:08Z

Orcmeal: Added option to use an integrated amplifier/speaker board

File:ZX-Spectrum-Next-Internal-Adafruit-Speaker-Amplifier.jpg

2023-08-30T20:03:44Z

Orcmeal:

An Adafruit STEMMA Speaker with integrated amplifier connected to the Spectrum Next motherboard and held in place inside the case with self-adhesive velcro strips. Cable colors do not reflect GND and Vcc correctly, but the cable sleeves do.

Circuit Diagrams

2023-08-25T13:53:14Z

Orcmeal:

== Schematics ==

The KS1 and KS2 schematics can be downloaded [https://gitlab.com/thesmog358/tbblue/-/tree/master/docs/schematics?inline=false here].

The three tail matrix keyboard schematic can be downloaded [https://github.com/Threetwosevensixseven/NXtel/wiki/images/NS58A-5-01-04.pdf here].

== J13 - Daughter board connector ==

{| width=100%
|valign=top width=50%| [[Image:DaughterLocation.jpg]]
|valign=top| [[Image:Circuit_daughter_board.png]]
|}

<br/>

== J15 - Next GPIO ==

{| width=100%
|valign=top width=50%| [[Image:NEXT_GPIO_location.jpg]]
|valign=top width=50%| [[Image:NEXT_GPIO.png|461px]]
|}

<br/>

== CN5 - Expansion bus (edge connector) ==

{| width=100%
|valign=top width=50%| [[Image:Expansion_bus_location.jpg]]
|valign=top| [[Image:Expansion_bus.png|461px]]
|}

<br/>

== J10/J11 - Memory Expansion Ports ==

{| width=100%
|valign=top width=50%| [[Image:Mem_Expansion_location.jpg]]
|valign=top| [[Image:Mem_Expansion.png|461px]]
|}

<br/>

== J4/J7 J8/J14 - Joystick Ports ==

{| width=100%
|valign=top width=50%| [[Image:Joystick_Ports_Location.jpg]]
|valign=top| [[Image:Joystick_Ports.png]]
|}

<br/>

== CN1 - VGA Video Port ==

{| width=100%
|valign=top width=50%| [[Image:Video_Port_Location.jpg]]
|valign=top| [[Image:Video_Port.png]]
|}

Notes:
* In VGA mode (scandoubler enabled), H-SYNC and V-SYNC are carried separately on their respective pins.
* In RGB mode (scandoubler disabled), H-SYNC carries composite sync, and V-SYNC carries 1.
* Pin 14 carries 3V3, which can be connected to SCART pin 16 to indicate RGB to the display.
* There is no convenient source of voltages between 9.5-12V to indicate 4:3 aspect ratio to the display on SCART pin 8, so this is usually left unconnected.

<br/>

== CN8 - Digital Port ==

{| width=100%
|valign=top width=50%|[[Image:Digital Port Location.jpg]]
|valign=top| [[Image:Next Digital Port.png]]
|}

<br/>

== CN2/CN6/CN7 - SD Reader (Mainboard) (CN6 on reverse) ==

{| width=100%
|valign=top width=50%| [[Image:SD_Reader_Port_Location.jpg]]
|valign=top| [[Image:SD_Reader_Main.png]]
|}

<br/>

== CN10/CN11/CN12 - SD Reader (Daughterboard) (CN12 on reverse) ==

{| width=100%
|valign=top width=50%| [[Image:SD_Reader_Daughter_Port_Location.jpg]]
|valign=top| [[Image:SD_Reader.png]]
|}

<br/>

== Accelerator Board ==

{| width=100%
|valign=top width=50%| [[Image:Accelerator_Port_Location.jpg]]
|valign=top| [[Image:Accelerator_Port.png]]
|}

<br/>

== Real Time Clock (RTC) ==

{| width=100%
|valign=top width=50%| [[Image:RTC_Port_Location.jpg]]
|valign=top| [[Image:RTC_Port.png]]
|}

<br/>

== CN9 - ESP8266-01/RS-232 Port ==
{| width=100%
|valign=top width=50%| [[Image:Wifi_Port_Location.jpg]]
|valign=top| [[Image:Next_ESP_Port.png]]
|}

<br/>