Alternatively, you can install JS Paint as a PWA (Progressive Web App),
but this does not yet support offline use
(as it doesn't include a Service Worker).
It's more like a bookmark (for now), except it runs in a special window.
The user interface for installing PWAs differs by browser and operating system.
On most desktop browsers, the install prompt is in the URL bar.
On mobile, the install prompt is generally found in the menu of browser options.
See
Installing PWAs for visual guidance.
Nmk004.bin «Genuine»
For years, developers had to rely on a "simulation" of the sound chip. MAME developers guessed how the audio logic worked by listening to real arcade boards, resulting in poor timing, missing sound effects, and incorrect musical pitches. It was widely assumed that the only way to ever get the raw code was via an expensive "acid decapping" process, where the chip's physical outer shell is melted away under a microscope to visually read the silicon bits. The Genius Audio Vulnerability Exploit
A common error screen encountered by retro-gaming enthusiasts reads: nmk004.bin NOT FOUND or Incorrect Checksum . This typically stems from two specific issues:
Because the internal ROM was microcode burned directly onto the silicon wafer during manufacturing, it could not be read using a standard EPROM reader. If arcade preservationists could not extract this code, the exact sound behaviors of the games could never be replicated perfectly. Arcade Games Dependent on nmk004.bin nmk004.bin
The nmk004.bin file is the raw binary dump of the internal microcontroller (MCU) used on NMK arcade system boards. Specifically, the chip functioned as a dedicated sound processor and security unit.
Because the internal ROM was electronically locked down by Toshiba’s factory security bits, emulator projects like MAME and FBNeo could not read the chip's internal structure. For over 20 years, developers had to rely on high-level guesswork ("simulation") to try and recreate the music, which often resulted in flat notes, missing sound effects, and glitches. 🔓 The Great Audio Hack: How the ROM Was Dumped For years, developers had to rely on a
The nmk004.bin file ensured that the music was rhythmic and the sound effects had "punch." In Hacha Mecha Fighter , a lesser-known but beloved horizontal shooter, the chip managed the chaotic audio environment of a cartoonish war zone. The fidelity of the explosions and the clarity of the music tracks were direct results of the efficient coding contained within that small binary file. It allowed the developers to create a dynamic soundscape where the music tempo could shift with the intensity of the gameplay, a feature that required precise timing logic hard-coded into the ROM. The Genius Audio Vulnerability Exploit A common error
The resulting audio was recorded into a high-fidelity WAV file and subsequently converted back into the precise 8 KB raw binary array we use today: nmk004.bin . Technical Specifications
The breakthrough came around 2014 through the extensive work of independent reverse-engineers and preservationists documented on platforms like Daifukkat.su . By executing a custom "Trojan" program on the original arcade hardware, developers forced the NMK004 chip to reveal its secret internal data structure byte-by-byte through audio note length delays. This painstaking process yielded the flawless 8KB file used globally today, ensuring the flawless preservation of arcade history. Arcade Games Dependent on nmk004.bin
They used a "Trojan" ROM—a modified game ROM that tricked the NMK004 into executing code that "played" the internal data out through the sound ports as audio pulses, which were then recorded and converted back into digital data. Affected Games
If your arcade software throws an error saying nmk004.bin MISSING or nmk004.zip NOT FOUND , use these quick configuration steps to resolve the problem: 1. Determine Your ROM Set Type
Feel free to copy these to your site!
Some of them are rubbish, but a few of them I'm quite happy with.
Right click on the image and select "Save image as..." to download it,
then copy and paste the HTML code below it into your site,
and update the src attribute to point to where you're hosting the image.
Here are some buttons I collected
I don't know where most of these came from, and I've repurposed some of them.