USB Target

The USB target puts your game on a bootable USB stick. Plug it into a PC, start the PC from the stick, and your game runs full screen with no operating system to install. When the player quits, the PC powers off. Nothing on the PC's own drives is used or changed.

This target is new. So far it has only been run on one real PC (NVIDIA graphics, UEFI start-up), so try your stick on the PC it's meant for before relying on it.



What You Need

Building

Choose Target > USB (ISO), then:

These go on the stick from your program's folder: the Media folder, LICENSE.txt, game.ini and any userlib .so files beside the program. Other files don't, so keep what your game loads in Media. The debugger isn't available on this target, and a UseConsole program can't go on a stick, because there's no terminal for it.



Writing the Stick

This wipes everything on the stick. In GNOME's Disks app, pick the stick, open its menu and choose Restore Disk Image. Or in a terminal, after checking which device is the stick with lsblk:

sudo dd if=YourGame.iso of=/dev/sdX bs=4M conv=fsync status=progress


What's on the Stick

The system is about 500 MB, so a 1 GB stick has room for it and a small game. Each game is added to a ready-made system image, so the system isn't rebuilt for every game. The stick has no network drivers, so a game can't go online from it.



Starting From the Stick

Most PCs need telling once to start from USB, usually by pressing a key such as F12, F8 or Esc just after switching on. The key varies between makers. The BambooBasic logo shows while the system starts, then your game appears.

Secure Boot on the Arch edition: A stick made with the Arch edition only starts with Secure Boot turned off, so tell your players. Turn it off in the PC's firmware settings, usually opened with F2 or Del just after switching on, and turn it back on afterwards if you like. This is because Secure Boot only starts boot loaders signed with a key the PC trusts, which on most PCs means one signed by Microsoft. Debian provides a signed loader, so a stick from the Debian and Ubuntu edition doesn't need this. Arch doesn't provide one, and the stick can't use one without it.



game.ini

This optional text file goes in your program's folder, with one setting on each line:

OnQuit=poweroff
Screen=SAMSUNG
SoundCard=1,3


Screens

Every connected screen is switched on, and the game runs full screen on one of them. The others stay black. Without a Screen setting, the game uses the connected screen with the highest connector number, which you can't easily predict. If it matters, name the screen. A game that calls sysSetMonitor overrides this, but the sound still follows the screen chosen here, so it's better to use Screen on this target.

On a PC with two screens, the first logos can appear on a different screen from the game. The PC chooses that screen itself while it starts up. On a PC with one screen, everything appears on that screen.



Sound

Sound goes to one output, chosen once as the game starts, in this order:

  1. The SoundCard setting, if there is one
  2. Speakers or headphones plugged into the PC
  3. The screen the game is on, if it has speakers (HDMI or DisplayPort)
  4. Another screen with an HDMI or DisplayPort connection
  5. Any other sound output

Plug in headphones before starting the PC, as they aren't noticed afterwards. A screen can report that it has sound and still have no speakers, so on a two-screen PC the game may be silent until you name the screen that does have them, using Screen. A PC with no sound output at all runs the game silently.



Differences From the Desktop

What Hasn't Been Tried Yet

BambooBasic © 2026 Michael Denathorn