Downloads of v 0.235:


Last Update:

13 Sep 2021

Package Maintainer(s):

Software Author(s):

  • hundreds of developers


mame arcade emulator game games gaming nintendo nes snes famicom gameboy sega portable binary

MAME (Portable)

  • 1
  • 2
  • 3

0.235 | Updated: 13 Sep 2021



Downloads of v 0.235:



Software Author(s):

  • hundreds of developers

  • 1
  • 2
  • 3
MAME (Portable) 0.235

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install MAME (Portable), run the following command from the command line or from PowerShell:


To upgrade MAME (Portable), run the following command from the command line or from PowerShell:


To uninstall MAME (Portable), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade mame -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade mame -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install mame
    name: mame
    version: '0.235'
    state: present

See docs at

chocolatey_package 'mame' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.235'

See docs at

cChocoPackageInstaller mame
    Name     = "mame"
    Version  = "0.235"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'mame':
  ensure   => '0.235',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 13 Sep 2021.



To use choco:// protocol URLs, install (unofficial) choco:// Protocol support

What is MAME

MAME originally stood for Multiple Arcade Machine Emulator.

MAME's purpose is to preserve decades of software history. As electronic technology continues to rush forward, MAME prevents this important "vintage" software from being lost and forgotten. This is achieved by documenting the hardware and how it functions. The source code to MAME serves as this documentation. The fact that the software is usable serves primarily to validate the accuracy of the documentation (how else can you prove that you have recreated the hardware faithfully?). Over time, MAME absorbed the sister-project MESS (Multi Emulator Super System), so MAME now documents a wide variety of (mostly vintage) computers, video game consoles and calculators, in addition to the arcade video games that were its initial focus.


MAME's main purpose is to be a refefence to the inner workings of the emulated machines. This is done both for educational purposes and for preservation purposes, in order to prevent historical software from disappearing forever once the hardware it runs on stops working. Of course, in order to preserve the software and demonstrate that the emulated behavior matches the original, you must also be able to actually use the software. This is considered a nice side effect, and is not MAME's primary focus.

It is not our intention to infringe on any copyrights or patents on the original games. All of MAME's source code is either our own or freely available. To operate, the emulator requires images of the original ROMs, CDs, hard disks or other media from the machines, which must be provided by the user. No portions of the original game code are included in the executable.


MAME is free. Its source code is free. The project as whole is under distributed under the GNU General Public License, version 2 (GPL-2.0), but most of code (including core functionality) is available under the BSD-3-clause license.

Legal ROM Sources:

MAME is mostly programmed in C with some core components in C++. MAME can currently emulate over 32000 individual systems from the last 5 decades. Supported systems


Click here to Patreon-ize the package maintainer.

$ErrorActionPreference = 'Stop'
$packageName    = 'mame' 
$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$TodaysVersion  = ($env:ChocolateyPackageVersion -replace '[.]','')

$packageArgs = @{
  packageName    = $packageName
  Destination    = $toolsDir
  FileFullPath64 = "$toolsDir\mame" + $TodaysVersion + "b_64bit.exe"

Get-ChocolateyUnzip @packageArgs

Install-ChocolateyShortcut -shortcutFilePath "$env:Public\Desktop\MAME.lnk" -targetPath "$toolsDir\mame.exe" -WorkingDirectory "$toolsDir"
Install-ChocolateyShortcut -shortcutFilePath "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\MAME.lnk" -targetPath "$toolsDir\mame.exe" -WorkingDirectory "$toolsDir"

Remove-Item $toolsDir\mame*_64bit.exe | Out-Null

icacls.exe $toolsDir /grant $WhoAmI":"'(OI)(CI)'F /T | Out-Null
$ErrorActionPreference = 'Stop'
$packageName= 'mame' 

Remove-Item "$ENV:Public\Desktop\MAME.lnk" -Force -ErrorAction SilentlyContinue
Remove-Item "$ENV:ProgramData\Microsoft\Windows\Start Menu\Programs\MAME.lnk" -Force -ErrorAction SilentlyContinue
==================== MAME ====================

The source code to MAME® is provided under the GNU General Public License version 2 or later as of Git revision 35ccf865aa366845b574e1fdbc71c4866b3d6a0f and the release of MAME 0.172. Source files may also be licensed as specified in the file header. This license does not apply to prior versions of MAME.

Copyright (C) 1997-2020  MAMEDev and contributors

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

MAME® is a registered trademark of Gregory Ember. The "MAME" name and MAME logo may not be used without first obtaining permission of the trademark holder.

The code in MAME is the work of hundreds of developers, each of whom owns the copyright to the code they wrote. There is no central copyright authority you can license the code from. The proper way to use the MAME source code is to examine it, using it to understand how the games worked, and then write your own emulation code. Sorry, there is no free lunch here.

bcurran3 07/16/2020

==================== MAME ====================
md5: 29A77390254B0DCF1AAF60305F113E7E | sha1: C228B692F395447C257D6647F01A4CB423053827 | sha256: E7F3603631E9114A455364645716281C56BD70AAB0B0053B9410AC0A0B502CBB | sha512: 2FFA5C73C1C498730334FECF0176622FCED06BFC381873C0E26ED06017962B1CD92659ACD8ABC6B3F21177B31D8191235825033928AC69175816F0A56DB664CD
==================== MAME ====================

The MAME binary is downloaded by BCURRAN3 directory from the MAME developer site at and packaged for Chocolatey.

==================== MAME ====================

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
MAME (Portable) 0.231 334 Tuesday, May 11, 2021 Approved
MAME (Portable) 0.230 215 Friday, April 9, 2021 Approved
MAME (Portable) 0.222 644 Friday, July 17, 2020 Approved
MAME (Portable) 0.220 268 Tuesday, May 5, 2020 Approved
MAME (Portable) 0.206 776 Wednesday, February 13, 2019 Approved
MAME (Portable) 0.205 235 Sunday, January 6, 2019 Approved
MAME (Portable) 0.199 626 Thursday, July 19, 2018 Approved
MAME (Portable) 0.198 320 Saturday, June 9, 2018 Approved

This package has no dependencies.

Discussion for the MAME (Portable) Package

Ground Rules:

  • This discussion is only about MAME (Portable) and the MAME (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or MAME (Portable), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus