<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://retronian.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://retronian.com/" rel="alternate" type="text/html" hreflang="en" /><updated>2026-04-10T05:04:14+00:00</updated><id>https://retronian.com/feed.xml</id><title type="html">Retronian</title><subtitle>Retro gaming, handheld game consoles, custom OS, and 3D printed accessories.</subtitle><author><name>Retronian</name></author><entry><title type="html">What’s the Best Way to Name Game Files for Emulators?</title><link href="https://retronian.com/2026/04/05/how-to-name-game-files-for-emulators/" rel="alternate" type="text/html" title="What’s the Best Way to Name Game Files for Emulators?" /><published>2026-04-05T00:00:00+00:00</published><updated>2026-04-05T00:00:00+00:00</updated><id>https://retronian.com/2026/04/05/how-to-name-game-files-for-emulators</id><content type="html" xml:base="https://retronian.com/2026/04/05/how-to-name-game-files-for-emulators/"><![CDATA[<p><strong>Conclusion:</strong> Follow <a href="https://datomatic.no-intro.org/stuff/The%20Official%20No-Intro%20Convention%20(20071030).pdf">The Official No-Intro Convention</a>.</p>

<p>There’s a project called <a href="https://no-intro.org/">No-Intro</a> that catalogs digital games and provides databases, and the document linked above comes from them.</p>

<p>It’s the standard naming convention across various emulator-related communities, starting with RetroArch. Following it makes it easier for programs that automatically assign things like box art to identify your games, so sticking to it is probably the safe choice.</p>

<p>Here’s a rough summary of what it says.</p>

<h2 id="rom-file-naming-convention">ROM File Naming Convention</h2>

<ul>
  <li>Only 7-bit ASCII characters are allowed.
    <ul>
      <li>a–z</li>
      <li>A–Z</li>
      <li>0–9</li>
      <li>space</li>
      <li><code class="language-plaintext highlighter-rouge">$ ! # % ' ( ) + , - . ; = @ [ ] ^ _ { } ~</code></li>
    </ul>
  </li>
  <li>The following ASCII characters cannot be used:
    <ul>
      <li><code class="language-plaintext highlighter-rouge">\ / : * ? " &lt; &gt; | </code> + “`”</li>
    </ul>
  </li>
  <li>Filenames cannot begin with a space or <code class="language-plaintext highlighter-rouge">.</code></li>
  <li>Generally, proper nouns, adjectives, and verbs are all capitalized.</li>
  <li>Articles and conjunctions are lowercased, except at the start of the title.
    <ul>
      <li>Examples:
        <ul>
          <li>Adventure of the Hero</li>
          <li>Riding in a Car</li>
          <li>Travel from Earth to the Moon</li>
          <li>From Earth…</li>
          <li>Into the Darkness…</li>
        </ul>
      </li>
    </ul>
  </li>
  <li>Writing the entire title in uppercase should be avoided as much as possible, unless it’s an acronym.</li>
  <li>If the first word is a common article, it is moved to the end of the main title and separated by a comma. (Retronian’s note: “Seriously?”)
    <ul>
      <li>Example 1: The Legend of Zelda → Legend of Zelda, The</li>
      <li>Example 2: A Man Born in Hell → Man Born in Hell, A</li>
    </ul>
  </li>
  <li>Subtitles and pre-titles are always separated from the main title by a hyphen “ - “. Titles that use other separators (for example colons or “~ subtitle ~” style) are converted to the hyphen style.
    <ul>
      <li>Example 1: Castlevania II - Belmont’s Revenge</li>
      <li>Example 2: Double Dragon - The Ultimate Team</li>
      <li>Example 3: Legend of Zelda, The - A Link to the Past</li>
    </ul>
  </li>
  <li><strong>Japanese characters should be romanized using the Hepburn system.</strong></li>
</ul>

<h2 id="things-that-caught-my-eye">Things That Caught My Eye</h2>

<p>The Legend of Zelda → Legend of Zelda, The — seriously, for real?</p>

<p>And, obviously, you can’t use Japanese characters in filenames. The hyphen style for subtitles is a good thing to keep in mind.</p>]]></content><author><name>Retronian</name></author><category term="emulation" /><category term="guide" /><category term="tips" /><summary type="html"><![CDATA[The Official No-Intro Convention is the de facto standard for naming ROM files used across emulator communities like RetroArch.]]></summary></entry><entry><title type="html">How to Read Retro Handheld Performance Specs</title><link href="https://retronian.com/2026/04/04/understanding-retro-handheld-performance-specs/" rel="alternate" type="text/html" title="How to Read Retro Handheld Performance Specs" /><published>2026-04-04T00:00:00+00:00</published><updated>2026-04-04T00:00:00+00:00</updated><id>https://retronian.com/2026/04/04/understanding-retro-handheld-performance-specs</id><content type="html" xml:base="https://retronian.com/2026/04/04/understanding-retro-handheld-performance-specs/"><![CDATA[<p>“Allwinner H700 Quad-core ARM Cortex-A53 1.5GHz”, “SigmaStar SSD202D Dual-core ARM Cortex-A7 1.2GHz” — the specs of retro handheld game consoles are confusing, aren’t they? Let me try to explain what they mean.</p>

<h2 id="manufacturer-soc-cpu-core">Manufacturer, SoC, CPU Core</h2>

<p>Take “Allwinner H700 Quad-core ARM Cortex-A53 1.5GHz” as an example. It breaks down like this:</p>

<ul>
  <li><strong>Allwinner</strong> — manufacturer</li>
  <li><strong>H700</strong> — SoC</li>
  <li><strong>Quad-core</strong> — number of CPU cores</li>
  <li><strong>ARM Cortex-A53</strong> — CPU core</li>
  <li><strong>1.5GHz</strong> — clock speed</li>
</ul>

<h2 id="manufacturer">Manufacturer</h2>

<p>Simply the company that makes the chip.</p>

<p>Major manufacturers:</p>

<ul>
  <li><strong>Allwinner</strong>: Cheap. Frequently used in the Anbernic XX series.</li>
  <li><strong>Rockchip</strong>: The standard choice for mid-range and higher.</li>
  <li><strong>UNISOC</strong>: Relatively new, high-performance.</li>
  <li><strong>MediaTek</strong>: Smartphone class.</li>
  <li><strong>SigmaStar</strong>: Ultra low power. Used in the Miyoo Mini family.</li>
</ul>

<h2 id="soc-system-on-a-chip">SoC (System on a Chip)</h2>

<p>A single chip that combines the CPU, GPU, memory controller, power management, and so on.</p>

<p>Major SoCs and the devices they’re in:</p>

<ul>
  <li><strong>H700</strong>: RG35XX series</li>
  <li><strong>A33</strong>: Miyoo A30</li>
  <li><strong>RK3326</strong>: RG351 / RGB20S</li>
  <li><strong>RK3566</strong>: RG353 / RGB30</li>
  <li><strong>RK3399</strong>: RG552</li>
  <li><strong>T820</strong>: RG556 and others</li>
  <li><strong>SSD202D</strong>: Miyoo Mini</li>
</ul>

<h2 id="number-of-cpu-cores">Number of CPU Cores</h2>

<p>Literally the number of cores.</p>

<ul>
  <li>Dual-core: 2</li>
  <li>Quad-core: 4</li>
  <li>Octa-core: 8</li>
</ul>

<h2 id="cpu-core">CPU Core</h2>

<p>This lives inside the SoC. These are almost all designs from ARM.</p>

<p>Major CPU cores (higher numbers are stronger):</p>

<ul>
  <li>Cortex-A7</li>
  <li>Cortex-A35</li>
  <li>Cortex-A53</li>
  <li>Cortex-A55</li>
  <li>Cortex-A72</li>
  <li>Cortex-A76</li>
</ul>

<h2 id="clock-speed">Clock Speed</h2>

<p>How fast the CPU runs. Basically, retro handhelds with the same CPU core tend to have the same clock speed, but apparently manufacturers sometimes overclock it through their settings, or intentionally lower it for better power efficiency.</p>

<h2 id="so-what-should-you-actually-look-at">So What Should You Actually Look At?</h2>

<p>As long as the SoC is the same, the other pieces are basically fixed. So if you know “this device uses the H700” or “it has an SSD202D”, you already know most of what there is to know about its performance.</p>

<p>Snapdragon, which shows up often in Android-based devices, has its own separate flavor of complexity — I’ll save that for another time.</p>

<h2 id="bonus-whats-the-difference-between-an-soc-system-on-a-chip-and-an-sbc-single-board-computer">Bonus: What’s the Difference Between an SoC (System on a Chip) and an SBC (Single Board Computer)?</h2>

<p>An SoC is where the main functions are packed into a single chip. An SBC is where all the various things a computer needs (including the chips) are arranged on a single board.</p>]]></content><author><name>Retronian</name></author><category term="hardware" /><category term="performance" /><category term="guide" /><summary type="html"><![CDATA[A quick guide to making sense of confusing retro handheld spec sheets like 'Allwinner H700 Quad-core ARM Cortex-A53 1.5GHz'.]]></summary></entry></feed>