Explore LODEX

R36S: check ROM folders, file formats and BIOS requirements

Tutorial · Retro handhelds

R36S: check ROM folders, file formats and BIOS requirements

Identify the emulated system and dArkOSRE version before choosing a folder, extension or BIOS; check each entry in that version’s documentation.

R36S and a microSD file organisation illustration
LODEX illustration — simplified representation.

At a glance

TimeDepends on the checks required

DifficultyIntermediate (LODEX estimate)

ConsoleR36S

SystemdArkOSRE-R36 / ArkOS reference depending on version

Compatible devices

Compatible consoles

R36S with identified system and hardware variant; the exact folder list depends on the installed version.

What you need

Required — Access to the microSD card, a computer and documentation for the emulated system; legally held files.

Explanatory diagram of ROM folders and BIOS checks
Explanatory diagram — simplified representation; read alongside the steps below. Click to enlarge.

Before choosing a folder

First identify the system emulated by the game. Its name determines the documentation entry to consult: do not infer its folder, extension or BIOS from another system.

  • Record the installed dArkOSRE-R36 version.
  • Record your R36S hardware variant if known.
  • Prepare only files you legally own.
  • Do not download or redistribute copyrighted ROM or BIOS files.

General ROM and BIOS locations

In ArkOS, ROMs are generally placed in /roms when accessed over the network, or the EASYROMS partition when directly accessing the microSD card. The documented general rule places BIOS files in the bios folder on the ROM/EASYROMS partition unless an emulator entry explicitly specifies another location.

dArkOSRE-R36 is a customised dArkOS version optimised for R36S devices and clones. Its repository distinguishes variants and support states. Check the actual structure in your build before applying the general rule.

What to check for each system

For each system, record four details separately from the matching ArkOS documentation entry: ROM folder, listed extensions, BIOS status and its location if different from the general bios folder. A documented extension describes an accepted format; it does not guarantee every game will work with your build or emulator.

SystemFolderListed formatsBIOS files
3DO3do.iso, .bin, .chd, .cueSeveral BIOS files are listed; consult the relevant entry for applicable names and location.
Amigaamiga.adf, .hdf, .lha, .zipSpecific Kickstart files are listed; consult the relevant entry for applicable names and location.
NES / Famicomnes or famicom.nes, .zip, .7zNo BIOS is listed for this entry.
Nintendo DSnds.nds, .zipOptional BIOS files are mentioned; consult the relevant entry for applicable names and location.

These examples do not replace the entry for your system. Do not infer exact BIOS names, required or optional status, or special locations from a neighbouring example.

Location exceptions not to generalise

  • Adventure Vision places its BIOS archive in the console folder rather than the general bios.
  • Some MESS systems require an exact ROM name and hash files.
  • For PC98, BIOS files go in the np2 subfolder of bios.

These exceptions apply to their specific documented entries. They do not establish another system’s location.

Step-by-step checking method

  1. Identify the emulated system.
  2. Check the dArkOSRE-R36 version and, if known, R36S hardware variant.
  3. Open ArkOS documentation and find the exact system entry.
  4. Record the listed ROM folder.
  5. Check the corresponding area in your installation: /roms over the network or the EASYROMS partition when accessing the microSD card directly.
  6. Compare the file extension with those listed for the system.
  7. Read the entire BIOS note: it may specify required, optional or absent BIOS files, or a location exception.
  8. If an exact BIOS, ROM or hash filename is required, copy that information only from the relevant entry.
  9. If your directory structure differs from the general rule, do not move files randomly: check the system entry and your build’s documentation.

Check the result

The check is consistent when the identified system, ROM folder, extension and BIOS note all match the same documentation entry and the structure actually visible in your installation.

  • Confirmed match: the folder and extension match the system entry and the applicable BIOS status or location is respected.
  • Unresolved match: the version, variant, folder, extension or BIOS status does not clearly match the documentation. Do not conclude compatibility.
  • Missing information: the system or exact required name is not covered by the examples here. Consult the complete documentation entry matching your configuration.

Why the dArkOSRE-R36 version matters

The dArkOSRE-R36 repository lists hardware variants with distinct support states. A project release also ties a version to changes in hardware and emulator support. Match folder, format and BIOS guidance to the installed version and variant rather than treating it as universal for every R36S.

Sources

Verify folder, format and BIOS guidance in the documentation for the installed version. To move from checking to copying files, see the guide to adding games and BIOS files to R36S with dArkOSRE.

Leave a Reply

Discover more from LODEXGAMES

Subscribe now to keep reading and get access to the full archive.

Continue reading