Not all ROMsets are created equal. Due to the age of version 0.34, many ZIP files floating around the internet are corrupt or misnamed. Here is how to ensure you are getting the mame 034 romset top quality:
In the sprawling world of arcade emulation, few version numbers carry as much weight as MAME 0.34 (often stylized as MAME .34). Released in the early 2000s, this specific ROMset has become a legendary benchmark for retro gamers, bartop cabinet builders, and purists who crave the raw, unadulterated arcade experience of the late 80s and early 90s.
When enthusiasts search for the "mame 034 romset top" , they aren’t just looking for a list of files. They are hunting for the best curated collection of games from an era when MAME was lightweight, fast, and focused exclusively on the classics—before the project became bogged down by obscure Japanese quiz games and complex CHD hard drive files.
This article explores what makes the MAME 0.34 ROMset the "top" choice for millions, the definitive games you must play, and how to build the ultimate retro cabinet around this iconic collection.
The “top” games in MAME 0.34 are the best-playable, most iconic arcade games from ~1980–1997 that run without CHDs: Pac-Man, Donkey Kong, Street Fighter II, Final Fight, Metal Slug, King of Fighters ’97, Galaga, Golden Axe, and TMNT. This romset is a snapshot of arcade history just before CPS2, 3D, and hard drive-based games. It remains popular for low-powered retro gaming devices.
If you meant “top” as in complete list of all games – MAME 0.34 supports roughly 1,300+ unique ROMs (including clones). A full XML listing is available via mame -listxml in the 0.34 command line version.
This report analyzes the top arcade games within the MAME 0.34 romset, a historic set released around late 1998/early 1999. MAME 0.34 is significant for being an early, stable version often used in retro handhelds, old PCs, and "mame4all" projects because of its low performance requirements and high compatibility with golden-era 80s and early 90s games. 1. Context: The MAME 0.34 Era (c. 1998–1999)
MAME 0.34 (released circa November 1998) represents a time when emulation was focusing on consolidating the 80s arcade library and breaking into the early 90s Capcom CPS-1/CPS-2 era.
Performance: Requires very low processing power, ideal for ARM-based handhelds, Raspberry Pi (using MAME2003 cores), or older desktop hardware.
ROMset Structure: Generally, this era prefers "split" sets (parents and clones) for managing limited storage, although merged sets are fine for full-set collections.
Key Support: Excellent support for Neo Geo, Capcom CPS-1, Konami, and Sega System 16/18 games. 2. Top "Must-Play" MAME 0.34 Games
These games were well-emulated, popular in arcades, and are considered essential staples of the 0.34 romset. Classic & Golden Age (Early-Mid 1980s)
Pac-Man / Ms. Pac-Man (pacman, mspacman): The foundational arcade experience.
Galaga (galaga): Considered perhaps the most addictive shooter of the era.
Donkey Kong (dkong): Nintendo's masterpiece of vertical platforming.
Robotron: 2084 (robotron): Williams Electronics' frantic twin-stick shooter.
Defender (defender): Complex, high-intensity scrolling shooter. Dig Dug (digdug): Strategic top-down maze game. Mr. Do! (mrdo): A unique, highly polished maze-platformer.
Galaga (1981): A high-risk, high-reward shooter that still has major appeal today,. Action & Beat-'em-Ups (Late 1980s-Early 1990s)
MAME 0.34 is a classic romset frequently used with older or low-resource handheld emulators like the GP2X, MAME4ALL (on early Android/Pi), and some RetroPie cores. Because MAME is version-sensitive, using the exact 0.34 romset is crucial for these older setups to function without "missing file" errors. Key Features of MAME 0.34 Release Date: Originally released around November 1998 ( 0.34b80.34 b 8 ) and December 1998 ( 0.34rc10.34 r c 1 Game Support: Includes roughly 1,139 supported game sets.
Hardware Compatibility: Specifically designed for systems with limited RAM, though some larger ROMs in the set may still be unplayable on very old hardware. Essential Tips for Your Setup mame 034 romset top
Non-Merged Sets: For custom collections, look for "non-merged" romsets. These contain every file needed for a specific game in one zip, so you don't have to worry about "parent" or "clone" dependencies.
BIOS Files: For games like Neo-Geo titles, you must place the neogeo.zip BIOS file in the same folder as your game ROMs for them to launch.
Managing Your List: Since a full set can be overwhelming, tools like the Arcade Database can help you identify specific file names and dependencies if you only want to download "the good stuff".
Performance Tweak: If games like Metal Slug run slowly, use the internal MAME menu (usually the Tab key) to find "Overclock" settings, though you may need a script to save these settings permanently.
High Scores: To save your progress, enable the Hiscore Support plugin through the MAME "Plugin Options" menu. Top Recommended Games for this Set
Community favorites often found in curated "Best of" versions of these early sets include:
The MAME 0.34 romset is a "legacy" collection. It dates back to the late 1990s. While modern MAME is currently at version 0.260+, version 0.34 remains popular for low-power devices. This includes older handhelds, early Raspberry Pi models, and Wii homebrew. 🕹️ Why Use MAME 0.34? Low Overhead: Runs smoothly on hardware with weak CPUs.
MAME4iOS / MAME4All: Many mobile emulators are built on this specific code branch.
Fast Loading: Smaller rom sizes and simpler drivers mean near-instant boot times.
Core Essentials: It contains the "Golden Age" hits without the bloat of modern CHD files. 🏆 Top Games in the 0.34 Romset
The 0.34 set contains roughly 1,000 to 1,500 unique titles. Here are the "must-haves" that defined the era and run perfectly on this version: The Heavy Hitters
Pac-Man / Ms. Pac-Man: The quintessential arcade experience.
Donkey Kong: The debut of Mario and the gold standard for platforming.
Galaga: The definitive fixed-shooter with the "captured fighter" mechanic.
Street Fighter II (Series): Includes World Warrior and Champion Edition.
Mortal Kombat: The original digitized fighter that changed the industry. Action & Beat 'Em Ups
Teenage Mutant Ninja Turtles: The 4-player classic (often listed as tmnt).
The Simpsons Arcade Game: High-quality animation and cooperative play.
Final Fight: The blueprint for the urban side-scrolling brawler. Golden Axe: High-fantasy hack-and-slash action. High-Speed Classics Not all ROMsets are created equal
OutRun: Sega’s iconic driving game with selectable music tracks.
Spy Hunter: Combat driving with a legendary Peter Gunn soundtrack.
Pole Position: The pioneer of the "behind-the-car" racing perspective. 🛠️ Technical Compatibility Tips Modern MAME MAME 0.34 (Legacy) ROM Naming Short (8.3) names Very short, specific names BIOS Files Integrated/Required Required (e.g., neogeo.zip) Samples High quality Required for sound in early games Speed Cycle-accurate (Slow) Performance-focused (Fast)
📍 Crucial Note: ROMs are version-specific. A ROM file from a modern "0.250" set will likely fail to load in a 0.34 emulator because the file signatures (hashes) and internal zip contents have changed over the last 25 years. 💡 How to Get the Best Experience
Get the Samples: Early games (like Donkey Kong or Galaga) use "samples" for sound effects. Without the samples folder, these games will be silent.
NeoGeo Support: To play Metal Slug or King of Fighters, you must have neogeo.zip in your ROMs folder.
Controller Mapping: On older versions, you often need to press Tab on a keyboard once the game starts to configure your buttons.
To help you get your setup running perfectly, could you tell me:
What device are you using (Raspberry Pi, old PC, or mobile)? Are you missing audio in certain games?
The pursuit of the MAME 0.34 ROMset is a deep dive into the "Golden Age" of arcade emulation. While modern MAME (Multiple Arcade Machine Emulator) versions have surpassed 0.250+, the 0.34 set remains a "top" priority for retro-gaming enthusiasts for one primary reason: performance on low-power hardware.
Here is an in-depth guide on why this specific ROMset is a legend in the emulation community, how it differs from modern sets, and why it’s the top choice for specific gaming builds. 1. Why MAME 0.34? The "Sweet Spot" of Retro Gaming
Released in the late 1990s, MAME 0.34 represents a pivotal moment in emulation history. It was one of the first versions to successfully stabilize core arcade hits from the late 70s to the mid-90s. Today, the MAME 0.34 ROMset is the top choice for:
Original Nintendo Wii Homebrew: The popular MAME Wiis port is based on the 0.34 engine.
Old-School Handhelds: Devices like the GP2X or older Dingoo handhelds rely on this set.
Legacy PCs: If you are reviving a Pentium III or a "beige box" PC for a dedicated arcade cabinet, 0.34 offers the lowest CPU overhead. 2. The Difference Between "Top" Sets: 0.34 vs. Modern MAME
The "Top" designation for a ROMset usually refers to its completeness and compatibility.
Modern MAME (0.200+): Focuses on "documentation" and "accuracy." This requires significant processing power to mimic the original hardware's quirks.
MAME 0.34: Focuses on "playability." It uses speed hacks and less demanding code to ensure games run at full 60 FPS on hardware that modern MAME would crawl on.
Because of this, the 0.34 set is significantly smaller (under 1GB) compared to modern sets that exceed 60GB. It contains approximately 1,300 to 1,500 unique games, focusing on the essentials: Pac-Man, Donkey Kong, Street Fighter II, and Galaga. 3. Key Components of a "Top" 0.34 ROMset The “top” games in MAME 0
When searching for a high-quality 0.34 collection, you need to ensure it is a Full Non-Merged Set. Here’s what that means for your setup:
Non-Merged: Each ZIP file contains every file needed to run that specific game. You don't need a "parent" ROM to play a "clone" (e.g., you can play the Japanese version of a game without having the US version in the folder).
Samples Included: Many early arcade games (like Donkey Kong or Galaxian) used analog sound hardware that couldn't be emulated initially. You need a separate "Samples" folder for these sounds to work.
Cleanup: A top-tier set will have removed "Mechanical" games (slot machines) that don't work with a controller, leaving only the playable arcade classics. 4. Hardware Compatibility
If you are building an arcade project, the MAME 0.34 ROMset is most commonly associated with MAME4ALL.
MAME4ALL is a high-performance port found on various platforms. If your emulator's documentation says it is "based on 0.34/0.35," using ROMs from a newer set will likely result in "Required Files Missing" errors. This is because ROM dumps are constantly refined; the files inside a Street Fighter II ZIP today are different from the files used in 1998. 5. Essential Titles in the 0.34 Collection
Even though it’s an older set, you aren't missing out on the heavy hitters. A "Top" 0.34 set includes:
Capcom CPS-1: Street Fighter II, Final Fight, Ghouls 'n Ghosts. Konami Classics: Frogger, Scramble, Time Pilot. Midway/Williams: Defender, Joust, Robotron: 2084. Namco: Dig Dug, Pole Position, Ms. Pac-Man. Summary: Is it right for you?
The MAME 0.34 ROMset is the "Top" choice if you are prioritizing efficiency over accuracy. It’s the perfect match for older consoles, handhelds, or vintage PCs where every megabyte of RAM and every MHz of CPU speed counts.
For those building a modern Raspberry Pi 4 or PC-based cabinet, you may want to look toward 0.78 (MAME 2003 Plus) or current versions. But for the dedicated "retro" tinkerer, 0.34 remains the gold standard of the lightweight era. 34 set? AI responses may include mistakes. Learn more
The Keeper of the Copper Gates: A Story of MAME 0.34
In the sprawling digital metropolis of Retro Gaming City, the skyline is dominated by the gleaming, skyscraping towers of the modern era. These are the versions of MAME (Multiple Arcade Machine Emulator) that exist today—versions 0.250 and beyond. They are colossal, housing dictionaries of data for tens of thousands of arcade games, demanding high-end PCs and terabytes of storage to function.
But deep in the basement of the city’s archives, lit only by the hum of a cathode ray tube monitor, sits a man named Elias. He is an "Archaeologist of the Code," and his treasure isn't the modern, bloated software. His obsession is a small, unassuming folder labeled MAME 0.34.
To the uninitiated, MAME 0.34 is just a number. But Elias knows it as the "Copper Gate"—a legendary milestone in emulation history released in the earlier days (specifically, August 2001). Here is the story of why this specific version, and its accompanying ROMset, remains a pillar of emulation history.
The mame 034 romset top is not just a collection of files; it is a time capsule. It represents the moment when emulation became accessible to the average user without sacrificing quality. Whether you are building a Raspberry Pi bartop for your man cave, reviving an old laptop as a retro console for your kids, or simply seeking the purest form of Final Fight without the CHD headaches, version 0.34 remains the champion.
By focusing on this specific set, you bypass the bloat of modern MAME and dive straight into the arcade's Golden Age. So find that 3GB ZIP folder, boot up your frontend, and prepare to lose a few hours to the high-score screen of Galaga.
Long live the 0.34.
Note: This report does not provide ROMs. Ownership of original arcade boards is legally required in many jurisdictions.
testssl.sh is free and open source software. You can use it under the terms of GPLv2, please review the License before using it.
Development takes place at github. We're now @ 3.2.3 (stable) and 3.3dev.
There was a last release of 3.0.10 (oldstable) but that was the last one in the 3.0.x branch.
Supported will always be the current dev version and the version before (n-1 rule). As soon as the dev version becomes the stable release, this will be the n-1 version and receives bugfixes only. The dev version has historically not delivered really broken software (no facebook paradigm). Consider it like a rolling release: It'll definitely change-- that is the point of development-- things might break for you if you e.g. expect the output or features all to be the same. But other than that: The dev version itself won't break (TM).
3.2 is the stable branch. There was one final 3.0.10 release, a.k.a the old stable. If you need longer support for 3.0.x there's a possibility for paid maintenance support. We are focussing on 3.3dev, further development will take place in that branch. We aim to not break things badly but, as said, things will change. If you want to make use of new features like QUIC, TLS 1.3 0-RTT, newer SSLlabs rating, check for the Opossum vulnerability and more, you should consider this branch.
-testssl.sh is pretty much portable/compatible. It is working on every Linux, Mac OS X, FreeBSD distribution, on MSYS2/Cygwin (slow).
It is supposed also to work on any other unixoid systems.
A newer OpenSSL version (1.0) is recommended though. /bin/bash is a prerequisite –
otherwise there would be no sockets.
openssl <verify|ocsp|pkey> . In principle any OpenSSL or even LibreSSL can be used as a helper. It's recommended to
use the one supplied as it makes sure special tests or features like IPv6, proxy support, STARTTLS MySQL or PostgreSQL are supported. (The one supplied stems
originally from github.com/PeterMosmans/openssl. openssl-1.0.2k-chacha.pm.ipv6.Linux+FreeBSD.tar.gz is a Linux- and FreeBSD-only tarball. The directory openssl-1.0.2i-chacha.pm.ipv6.contributed/ contains contributed builds for ARM7l and Darwin binaries).
curl -L https://testssl.sh or wget -O - https://testssl.sh pulls the current stable code from here curl -L https://testssl.sh/dev/ or wget -O - https://testssl.sh/dev/ pulls the current development code from githubuserid@somehost:~ % testssl.sh
"testssl.sh [options] <URI>" or "testssl.sh <options>"
"testssl.sh <options>", where <options> is:
--help what you're looking at
-b, --banner displays banner + version of testssl.sh
-v, --version same as previous
-V, --local pretty print all local ciphers
-V, --local <pattern> which local ciphers with <pattern> are available? If pattern is not a number: word match
<pattern> is always an ignore case word pattern of cipher hexcode or any other string in the name, kx or bits
"testssl.sh <URI>", where <URI> is:
<URI> host|host:port|URL|URL:port port 443 is default, URL can only contain HTTPS protocol)
"testssl.sh [options] <URI>", where [options] is:
-t, --starttls <protocol> Does a default run against a STARTTLS enabled <protocol,
protocol is <ftp|smtp|lmtp|pop3|imap|xmpp|telnet|ldap|nntp|postgres|mysql>
--xmpphost <to_domain> For STARTTLS enabled XMPP it supplies the XML stream to-'' domain -- sometimes needed
--mx <domain/host> Tests MX records from high to low priority (STARTTLS, port 25)
--file/-iL <fname> Mass testing option: Reads one testssl.sh command line per line from <fname>.
Can be combined with --serial or --parallel. Implicitly turns on "--warnings batch".
Text format 1: Comments via # allowed, EOF signals end of <fname>
Text format 2: nmap output in greppable format (-oG), 1 port per line allowed
--mode <serial|parallel> Mass testing to be done serial (default) or parallel (--parallel is shortcut for the latter)
--warnings <batch|off> "batch" doesn't continue when a testing error is encountered, off continues and skips warnings
--connect-timeout <seconds> useful to avoid hangers. Max <seconds> to wait for the TCP socket connect to return
--openssl-timeout <seconds> useful to avoid hangers. Max <seconds> to wait before openssl connect will be terminated
single check as <options> ("testssl.sh URI" does everything except -E and -g):
-e, --each-cipher checks each local cipher remotely
-E, --cipher-per-proto checks those per protocol
-s, --std, --standard tests certain lists of cipher suites by strength
-p, --protocols checks TLS/SSL protocols (including SPDY/HTTP2)
-g, --grease tests several server implementation bugs like GREASE and size limitations
-S, --server-defaults displays the server's default picks and certificate info
-P, --server-preference displays the server's picks: protocol+cipher
-x, --single-cipher <pattern> tests matched <pattern> of ciphers
(if <pattern> not a number: word match)
-c, --client-simulation test client simulations, see which client negotiates with cipher and protocol
-h, --header, --headers tests HSTS, HPKP, server/app banner, security headers, cookie, reverse proxy, IPv4 address
-U, --vulnerable tests all (of the following) vulnerabilities (if applicable)
-H, --heartbleed tests for Heartbleed vulnerability
-I, --ccs, --ccs-injection tests for CCS injection vulnerability
-T, --ticketbleed tests for Ticketbleed vulnerability in BigIP loadbalancers
-BB, --robot tests for Return of Bleichenbacher's Oracle Threat (ROBOT) vulnerability
-R, --renegotiation tests for renegotiation vulnerabilities
-C, --compression, --crime tests for CRIME vulnerability (TLS compression issue)
-B, --breach tests for BREACH vulnerability (HTTP compression issue)
-O, --poodle tests for POODLE (SSL) vulnerability
-Z, --tls-fallback checks TLS_FALLBACK_SCSV mitigation
-W, --sweet32 tests 64 bit block ciphers (3DES, RC2 and IDEA): SWEET32 vulnerability
-A, --beast tests for BEAST vulnerability
-L, --lucky13 tests for LUCKY13
-F, --freak tests for FREAK vulnerability
-J, --logjam tests for LOGJAM vulnerability
-D, --drown tests for DROWN vulnerability
-f, --pfs, --fs, --nsa checks (perfect) forward secrecy settings
-4, --rc4, --appelbaum which RC4 ciphers are being offered?
tuning / connect options (most also can be preset via environment variables):
--fast omits some checks: using openssl for all ciphers (-e), show only first preferred cipher.
-9, --full includes tests for implementation bugs and cipher per protocol (could disappear)
--bugs enables the "-bugs" option of s_client, needed e.g. for some buggy F5s
--assume-http if protocol check fails it assumes HTTP protocol and enforces HTTP checks
--ssl-native fallback to checks with OpenSSL where sockets are normally used
--openssl <PATH> use this openssl binary (default: look in $PATH, $RUN_DIR of testssl.sh)
--proxy <host:port|auto> (experimental) proxy connects via <host:port>, auto: values from $env ($http(s)_proxy)
-6 also use IPv6. Works only with supporting OpenSSL version and IPv6 connectivity
--ip <ip> a) tests the supplied <ip> v4 or v6 address instead of resolving host(s) in URI
b) arg "one" means: just test the first DNS returns (useful for multiple IPs)
-n, --nodns <min|none> if "none": do not try any DNS lookups, "min" queries A, AAAA and MX records
--sneaky leave less traces in target logs: user agent, referer
--ids-friendly skips a few vulnerability checks which may cause IDSs to block the scanning IP
--phone-out allow to contact external servers for CRL download and querying OCSP responder
--add-ca <cafile> path to <cafile> or a comma separated list of CA files enables test against additional CAs.
--basicauth <user:pass> provide HTTP basic auth information.
output options (can also be preset via environment variables):
--quiet don't output the banner. By doing this you acknowledge usage terms normally appearing in the banner
--wide wide output for tests like RC4, BEAST. PFS also with hexcode, kx, strength, RFC name
--show-each for wide outputs: display all ciphers tested -- not only succeeded ones
--mapping <openssl| openssl: use the OpenSSL cipher suite name as the primary name cipher suite name form (default)
iana|rfc -> use the IANA/(RFC) cipher suite name as the primary name cipher suite name form
no-openssl| -> don't display the OpenSSL cipher suite name, display IANA/(RFC) names only
no-iana|no-rfc> -> don't display the IANA/(RFC) cipher suite name, display OpenSSL names only
--color <0|1|2|3> 0: no escape or other codes, 1: b/w escape codes, 2: color (default), 3: extra color (color all ciphers)
--colorblind swap green and blue in the output
--debug <0-6> 1: screen output normal but keeps debug output in /tmp/. 2-6: see "grep -A 5 '^DEBUG=' testssl.sh"
file output options (can also be preset via environment variables)
--log, --logging logs stdout to '${NODE}-p${port}${YYYYMMDD-HHMM}.log' in current working directory (cwd)
--logfile|-oL <logfile> logs stdout to 'dir/${NODE}-p${port}${YYYYMMDD-HHMM}.log'. If 'logfile' is a dir or to a specified 'logfile'
--json additional output of findings to flat JSON file '${NODE}-p${port}${YYYYMMDD-HHMM}.json' in cwd
--jsonfile|-oj <jsonfile> additional output to the specified flat JSON file or directory, similar to --logfile
--json-pretty additional JSON structured output of findings to a file '${NODE}-p${port}${YYYYMMDD-HHMM}.json' in cwd
--jsonfile-pretty|-oJ <jsonfile> additional JSON structured output to the specified file or directory, similar to --logfile
--csv additional output of findings to CSV file '${NODE}-p${port}${YYYYMMDD-HHMM}.csv' in cwd or directory
--csvfile|-oC <csvfile> additional output as CSV to the specified file or directory, similar to --logfile
--html additional output as HTML to file '${NODE}-p${port}${YYYYMMDD-HHMM}.html'
--htmlfile|-oH <htmlfile> additional output as HTML to the specified file or directory, similar to --logfile
--out(f,F)ile|-oa/-oA <fname> log to a LOG,JSON,CSV,HTML file (see nmap). -oA/-oa: pretty/flat JSON.
"auto" uses '${NODE}-p${port}${YYYYMMDD-HHMM}'. If fname if a dir uses 'dir/${NODE}-p${port}${YYYYMMDD-HHMM}'
--hints additional hints to findings
--severity <severity> severities with lower level will be filtered for CSV+JSON, possible values <LOW|MEDIUM|HIGH|CRITICAL>
--append if (non-empty) <logfile>, <csvfile>, <jsonfile> or <htmlfile> exists, append to file. Omits any header
--outprefix <fname_prefix> before '${NODE}.' above prepend <fname_prefix>
Options requiring a value can also be called with '=' e.g. testssl.sh -t=smtp --wide --openssl=/usr/bin/openssl <URI>.
<URI> always needs to be the last parameter.
userid@somehost:~ %
testssl.sh --starttls smtp <smtphost>.<tld>:587 testssl.sh --starttls ftp <ftphost>.<tld>:21 testssl.sh -t xmpp <jabberhost>.<tld>:5222 testssl.sh -t xmpp --xmpphost <XMPP domain> <jabberhost>.<tld>:5222 testssl.sh --starttls imap <imaphost>.<tld>:143The ports in those examples above are just the standard ports. Also here you're free to check any port. //refactor those, see e.g. https://content-security-policy.com/unsafe-hashes/ or just drop tis shit
3.2
3.0