DOSBox Pure Keyboard Controls on RG CubeXX: On-Screen Keyboard, Gamepad Mapping, and Saving Per-Game Controls

Short Answer

For occasional DOS typing, use DOSBox Pure’s on-screen keyboard. In DOSBox Pure 0.9.9, its default gamepad shortcut is L3—press the left analog stick—but this shortcut can be remapped or disabled.

For keys you press often, use DOSBox Pure’s internal Gamepad Mapper. It can assign keyboard, mouse, or joystick functions to handheld inputs, with up to four functions on one gamepad input. Changes apply and save when the mapper closes.

Use RetroArch remaps for a different task: changing how physical buttons feed the core. These remaps can use game, content-directory, or core scope and are stored as .rmp files. They are not the same as DOSBox Pure’s internal mapper data.

For substantial typing with a physical keyboard, enable RetroArch Game Focus so frontend hotkeys and keyboard-to-RetroPad bindings do not intercept keys intended for the core. Scroll Lock is RetroArch’s default keyboard toggle for Game Focus, but the binding can be changed.

This guide is based on DOSBox Pure 0.9.9 source code and official DOSBox Pure, Libretro, and KNULLI documentation. It does not present these procedures as a hands-on RG CubeXX test.

Problem: DOS Games Often Need More Keys Than a Handheld Provides

Many DOS games need occasional text, function keys, commands, or key combinations that do not fit naturally on a handheld controller. One game may need only Enter and Escape, while another may depend on letters, modifiers, or substantial typing.

The difficulty is not simply “how to bind a key.” DOSBox Pure and RetroArch provide different input layers, and each is suited to a different job. Using the wrong layer can make a change broader than intended or create confusion about where it is saved.

Cause: Four Input Methods Solve Different Problems

On-screen keyboard: Occasional text, function keys, prompts, or rarely used commands.
DOSBox Pure Gamepad Mapper: Frequently used DOS keyboard, mouse, or emulated joystick functions assigned directly to gamepad inputs.
RetroArch remap: Changes to how a physical control is delivered to the core, with game, content-directory, or core scope.
Physical keyboard with Game Focus: Substantial typing, many modifiers, or a wide range of keys sent directly to the core.

DOSBox Pure can detect some games and apply controller mappings. If it does not find a suitable mapping, it can use generic keyboard mappings. Do not assume an automatic mapping exists for every DOS game; inspect and adjust the mapping when needed.

Solution 1: Use the On-Screen Keyboard for Occasional Keys

In DOSBox Pure 0.9.9, L3 opens the on-screen keyboard by default. L3 normally means pressing the left analog stick inward.

Launch the DOS game.
Press L3.
Move the on-screen cursor to the required key.
Enter the key or short text.
Close the keyboard and return to the game.

The tagged 0.9.9 documentation says L2 and R2 adjust the on-screen cursor’s movement speed. It also describes the keyboard moving between the top and bottom of the screen based on cursor position.

L3 is only the default. The activation control can be changed through the mapper, and the on-screen keyboard can be disabled through a Core Option. If L3 does nothing, check those settings before assuming the stick click is defective. Labels can vary with frontend configuration and software version.

The on-screen keyboard is practical for a short name, Y or N, an occasional function key, or another brief command. Modifier-heavy or text-heavy games can remain awkward.

If the problem is an overly fast analog pointer rather than keyboard access, see KNULLI DOSBox Pure Mouse Too Fast on RG CubeXX? Firefly Settings.

Solution 2: Map Frequently Used Keys in DOSBox Pure

Use DOSBox Pure’s internal mapper when a game repeatedly needs keys such as Space, Enter, Escape, Ctrl, a function key, or a letter command.

DOSBox Pure 0.9.9 documents two ways to open it:

Select CONTROLLER MAPPER from the DOSBox Pure start menu.
Open the on-screen keyboard and select PAD MAPPER.

Then configure the gamepad:

Open CONTROLLER MAPPER or PAD MAPPER.
Select the gamepad button or direction you want to change.
Assign the required keyboard, mouse, or emulated joystick function.
If the game needs a combination, add more functions to that input. DOSBox Pure 0.9.9 supports up to four functions per gamepad input.
Close the mapper when finished so the changes apply and save.
Return to the game and verify every changed input.

Review the current mapping before replacing it. DOS games use different layouts, and an automatically detected profile may already be active.

If an automatic launch choice skips the DOSBox Pure start menu, the tagged 0.9.9 documentation says you can force the menu to appear by holding L2 or R2 while selecting Restart in the core menu. The exact frontend presentation can differ.

Solution 3: Use a RetroArch Remap for Frontend Input Routing

RetroArch remaps operate outside DOSBox Pure’s internal DOS mapper. They change how physical controls are delivered through RetroArch to the core.

Use a RetroArch remap when you need to:

swap or redirect buttons at the frontend/core boundary;
use a game, content-directory, or core-wide scope;
save the change in RetroArch’s .rmp system; or
correct which RetroPad input reaches DOSBox Pure before assigning its DOS-side function.

KNULLI documents this workflow:

Start the game.
Open the RetroArch Quick Menu with the configured KNULLI hotkey.
Open Controls → Manage Remap Files.
Check Active Remap File before making changes.
Choose Save Game Remap File, Save Content Directory Remap File, or Save Core Remap File for the required scope.
Return to Controls, open the relevant port controls, and change the required input.
Return to the game and verify the result.

KNULLI documents the remap priority from narrowest to broadest:

A game remap overrides broader remaps.
A content-directory remap overrides core and default remaps.
A core remap overrides the default common.rmp.

The matching active .rmp is loaded again when the corresponding game, directory, or core is launched. Choose the narrowest useful scope. If only one DOS game needs the change, prefer a game remap over a core-wide remap.

Solution 4: Use Game Focus with a Physical Keyboard

A physical keyboard is usually more practical for text adventures, configuration utilities, command-line work, or games that depend on many letters and modifier combinations. Whether a particular keyboard connection works depends on the device and KNULLI configuration in use.

RetroArch recommends Game Focus for cores that read keyboard input directly:

Connect a keyboard supported by your device and KNULLI setup.
Launch the DOS content.
Toggle Game Focus. RetroArch’s default keyboard toggle is Scroll Lock.
Type in the DOS game.
Toggle Game Focus off when you need normal RetroArch keyboard shortcuts again.

With Game Focus active, RetroArch hotkeys and keyboard-to-RetroPad bindings are disabled so the core can receive keyboard input. If Scroll Lock does not work, the binding may have changed or the keyboard may not expose that key. Find the named Game Focus control in RetroArch’s hotkey settings instead of relying only on the default.

How Per-Game Mappings Are Saved: PADMAP.DBP vs .rmp

The DOSBox Pure mapper and RetroArch remaps store different layers of input configuration.

DOSBox Pure Internal Mapper: `C:\PADMAP.DBP`

DOSBox Pure 0.9.9’s implementation reads and writes internal mapper data as C:\PADMAP.DBP inside the emulated DOS environment. Closing the mapper applies and saves its changes.

This is DOSBox Pure internal mapper data. It is not a RetroArch .rmp remap.

The implementation evidence for the internal path is high confidence. A universal host-visible filesystem location is not established. How this data appears outside the emulated environment can vary with ZIP, DOSZ, directory, or installed-system content layouts. Do not publish one universal RG CubeXX host path for PADMAP.DBP without layout-specific verification.

RetroArch Remaps: `.rmp`

RetroArch stores frontend remaps as .rmp files. KNULLI documents game, content-directory, and core scopes and reloads the active remap matching the launched content.

An .rmp file does not replace PADMAP.DBP. In practical terms:

Use DOSBox Pure’s mapper to make a gamepad input produce a DOS keyboard, mouse, or joystick function.
Use a RetroArch .rmp to change which physical/RetroPad input reaches the core and how broadly that frontend change applies.

For the separate Core Options workflow, see saving per-game Core Options.

Verification: Confirm the Right Input Layer and Save Scope

After making a change:

Test every altered button or direction in the game.
Check that normal gameplay inputs still work and no destructive combination is easy to trigger.
Close the DOSBox Pure mapper before evaluating its result, because tagged 0.9.9 documentation says changes apply and save when it closes.
If you used a RetroArch remap, reopen Manage Remap Files and confirm the intended game, content-directory, or core remap is active.
Close and relaunch the same content.
Verify that the intended control behavior returns after relaunch.
If the change affects too many games, replace a broad content-directory or core remap with a game remap.

These verification steps are documentation-based guidance. This article does not claim that the sequence was locally tested on an RG CubeXX.

Troubleshooting Checklist

L3 Does Not Open the On-Screen Keyboard

Confirm that L3 is still assigned as the activation button.
Check whether the on-screen keyboard was disabled in DOSBox Pure Core Options.
Check whether the internal mapper or a RetroArch remap changed the stick-click input.
Remember that L3 is the DOSBox Pure 0.9.9 default, not a guaranteed binding after customization.

The Gamepad Uses Unexpected Generic Keys

The game may not have been detected or may not have a suitable automatic profile.
Open DOSBox Pure’s Controller Mapper and inspect the current mapping.
Assign the important keyboard functions manually where needed.

A DOSBox Pure Mapper Change Does Not Take Effect

Close the mapper so the changes can apply and save.
Confirm that you changed the intended gamepad input.
Relaunch the same content and check the mapping again.
Do not assume a fixed host path for PADMAP.DBP while diagnosing persistence.

A RetroArch Remap Affects Too Many Games

Open Controls → Manage Remap Files and inspect the active remap.
Replace a core or content-directory remap with a game remap if only one title needs the change.
Check for a higher-priority game or content-directory .rmp that overrides a broader file.

A Physical Key Triggers a RetroArch Action

Enable Game Focus before typing.
If only a few keys conflict, inspect the conflicting frontend hotkey or keyboard-to-RetroPad bindings.
Disable Game Focus again when you need normal frontend keyboard control.

Key Combinations Are Still Awkward

Use the internal mapper’s support for up to four functions on one input only where the combination is safe and useful.
Avoid destructive or easy-to-trigger combinations on buttons used during normal play.
Use a physical keyboard for text-heavy or modifier-heavy games when the hardware and KNULLI setup support one.

Limitations and Version Scope

This guide targets DOSBox Pure 0.9.9 and uses externally researched source code and official documentation. It is not a hands-on RG CubeXX test.

Later previews or releases can reorganize option names, mapper screens, or labels. KNULLI hotkeys and RetroArch menu wording can also differ after customization or between releases. Use the named functions—On-Screen Keyboard, Controller Mapper, PAD MAPPER, Game Focus, and Manage Remap Files—as landmarks when presentation differs.

Handheld mapping also has practical limits. Games that expect sustained typing, several modifiers, or most of a full keyboard can remain awkward even after careful mapping.

FAQ

Does L3 Always Open the DOSBox Pure On-Screen Keyboard?

No. L3 is the default in DOSBox Pure 0.9.9, but the activation control can be remapped and the on-screen keyboard can be disabled.

What Should I Use for One Key I Press Repeatedly?

Use the DOSBox Pure internal Gamepad Mapper. It assigns a DOS keyboard, mouse, or joystick function directly to a gamepad input and applies/saves changes when the mapper closes.

Can One Handheld Button Perform More Than One Function?

Yes. DOSBox Pure 0.9.9 supports up to four functions on one gamepad input. Verify the combination carefully in the game before relying on it.

Is PADMAP.DBP a RetroArch Remap File?

No. PADMAP.DBP belongs to DOSBox Pure’s internal mapper. RetroArch remaps use the .rmp extension.

Where Is PADMAP.DBP on the RG CubeXX Filesystem?

DOSBox Pure 0.9.9 reads and writes it internally as C:\PADMAP.DBP. Its host-visible location or container can vary with the content layout, so this guide does not give one universal filesystem path.

How Do I Save a RetroArch Control Change for One Game?

Open Quick Menu → Controls → Manage Remap Files and choose Save Game Remap File. Confirm that the game-specific .rmp is active.

Why Does My Physical Keyboard Trigger RetroArch Shortcuts?

RetroArch may be interpreting the key as a hotkey or keyboard-to-RetroPad binding. Enable Game Focus—Scroll Lock by default—while entering keyboard input directly into the core.

Which Method Should I Try First?

Use the on-screen keyboard for occasional input, DOSBox Pure’s internal mapper for frequently used DOS keys, a RetroArch remap for frontend/core routing, and a physical keyboard with Game Focus for substantial typing.