Handlers follow the support-folder rule#
VMC files, VMCDIR.TXT, BIOS.BIN, OSD.BIN, patch files, and many handler assets belong where POPStarter will look for the current backend and game. The wrong folder can look exactly like an incompatible game.
Virtual memory card basics#
SLOT0.VMCandSLOT1.VMCare the normal per-game VMC files.$NOVMC0and$NOVMC1can disable individual virtual slots when a game or test requires that behavior.- SMB shares must be writable because POPStarter creates and updates VMC files over the network.
- For multi-disc games, use
VMCDIR.TXTin later-disc folders to point saves back to disc 1's VMC folder.
POPS folder priority#
USB split folders and HDD common folders are easy to misread. POPS_IOX.PAK and IGR textures can live in the main POPS folder, while per-game handlers and compatibility files often need to be copied into the specific folder being launched from.
| Backend | VCD location | Typical support/handler location |
|---|---|---|
| USB | mass:/POPS or mass:/POPS0..9 | mass:/POPS#/<VCD basename>/ for per-game files. |
| HDD | hdd0:/__.POPS | hdd0:/__common/POPS/<VCD basename>/. |
| SMB | Share POPS/ | Share POPS/<VCD basename>/. |
BIOS and OSD handlers#
The recovered wiki coverage separates BIOS handler and OSD handler behavior. Keep those files as explicit per-game experiments, not global defaults. If both handler names appear in a source, preserve the source-specific priority note instead of guessing.
The recovered VMC/handler notes flag OSD.BIN and BIOS.BIN precedence as important enough to track. This site keeps it as a handler topic until package-level inspection confirms every edge case.
IGR textures#
IGR texture loading is part of the later POPStarter line. Texture files such as IGR_BG.TM2 belong to presentation, not compatibility. POPSLoader packages can also include similarly named texture patch artifacts, so keep texture files separate from compatibility PATCH_#.BIN meaning.
Do not merge support-file families#
PATCH_5.BIN as a compatibility mode, POPSLoader IGR texture resources, VMC routing files, and BIOS/OSD handlers are different families. Similar filenames do not prove similar behavior.