Install to a spare slot first
Connect the device over PROG and open Device Memory Slots in Gtuner IV. Install the work into an available slot using the supported install command or drag-and-drop. Before overwriting an occupied slot, save the source file and any author-specific settings you may want to restore. Use a spare slot as the test target when updating an existing project.
ConsoleTuner distinguishes internal slots from extended storage supplied by microSD. Some work includes additional data, such as macros or compiled files to be placed on the card. Read the author’s dependencies and confirm the storage needed by that particular package instead of assuming that every resource is one standalone file.
Select and verify the active slot
Use the physical slot buttons to select the slot you programmed. The device’s display gives you a quick way to confirm the active selection. When diagnosing a problem, unload the current slot and repeat one input in Device Monitor. Then select the intended slot and repeat the same input to isolate what the programmed work changes.
If Gtuner IV shows the item in the slot but the expected change is absent, check the display before installing a second copy. The correct item can be programmed while a different slot is active.
Keep notes you can use later
Give each maintained slot a purpose, such as a controller layout, a clean baseline or a test build. Gtuner IV supports custom slot annotations. Record the work version and any companion translator or macro there or in your project notes. These notes are especially useful when two slots have similar names but different settings.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.