Home - BeBytes Info - Submit App - Your Account - Links - Contact Us

Version 1.7.1
Contact Publisher
Version History
Other Reviews
Send Updates
  Submitted by: Wildman

Date Posted:
Last Updated:
Page Views:
User Rating:
awaiting votes..  

About VirtualBoyAdvance:

Welcome to version 1.7.1 of VisualBoyAdvance-SDL. This is a GB/GBC/GBA
emulator for Windows, Linux and BeOS.


- configurable GB/GBA keys, including joystick support
- option to use BIOS file
- zip/gzip file support
- directory selection for save state, battery and screen capture
- fullscreen mode (selectable resolution)
- video sizes 1x, 2x, 3x and 4x
- graphic filters Normal, TV Mode, 2xSaI, Super 2xSaI and more
- interframe blending support
- same emulation core as VisualBoyAdvance: GB and GBA emulation
- built-in ARM/THUMB assembly debugger
- 10 save states accesible through keyboard
- automatic battery file load/save
- auto-fire support
- pause, reset through keyboard
- 16, 24 and 32 bit desktop support
- GDB remote debugging (see below for information)
- auto frameskipping and throttle
- AGBPrint support for development
- RTC support

Compiling the sources

See the INSTALL file for compiling instructions. Please note the following
requisites to compile:

- GCC must be 3.x or greater in order to compile GBA.cpp with -O2. Earlier
versions have a problem during optimization that requires an absurd
ammount of memory and usually ends up crashing the compiler/computer
- On Windows, Microsoft Visual C++ 6 or later is needed. Please note that
some of the source code will not compile with the shipped header files.
You will need to install the most recent Platform SDK from Microsoft.


The easiest installation is to place all files in the distribution in the
same directory.

Per game settings

Version 1.5 introduced the support for per game settings for GBA games. You
can defined the following settings on a per game basis by using an INI file
called vba-over.ini in the same directory as the emulator:

rtcEnabled=<0 for false, anything else for true>
flashSize=<65536 or 131072>
saveType=<0 for automatic, 1 for EEPROM, 2 for SRAM, 3 for Flash or 4 for

Use the 4 letter game code to separate settings for each game. Example:




Please support VisualBoyAdvance by making a donation. You can donate money
using PayPal (www.paypal.com). Use the contact form to find how you can
send donations. Also, it is recommended that you use the VisualBoyAdvance
forum on www.ngemu.com message board.


See online FAQ for more information: http://vba.ngemu.com/faq.shtml

Please don't email about what you think it is problem before consulting
the FAQ.

System requirements

Windows: PIII 500Mhz machine for GBA emulation. GB emulation requires far less.

Linux: minimum requirement should be similar to Windows version. SDL 1.2.2
runtime library must be installed prior to running the program. You can
download it from http://www.libsdl.org

Key combinations during emulation:

- F1...F10: load save state 1...10
- Shift+F1...F10: save state 1...10
- Alt+1...4: auto-fire A,B,L,R
- Ctrl+1...8: enable/disable graphical layers (BG0, BG1, BG2, BG3, OBJ, WIN0,
- Ctrl+N: pause on next frame
- Ctrl+R: reset
- Ctrl+P: pause
- Ctrl+B: rewind (if enabled and available)
- F11: enter built-in debugger
- ESC: exit emulator

Emulation key settings:

- Movement: arrow keys
- Button A: Z
- Button B: X
- Button L: A
- Button R: S
- Button Start: ENTER
- Button Select: BACKSPACE
- Speed up: SPACE
- Screen capture: F12
- Motion Left: NUMPAD 4
- Motion Right: NUMPAD 6
- Motion Up: NUMPAD 8
- Motion Down: NUMPAD 2

GDB support

VisualBoyAdvance now provides GDB remote debugging support. This gives
developers the full power of GDB to debug GBA applications.

In order to use this, you will need a cross-compiled GDB for either the arm-elf
or arm-thumb-elf target (used for the --target= option of GDB configure

You can also use GDB frontends like DDD, CodeMedic, etc... or even GDB/Insight
for GUI debugger (if using anything other than GDB/Insight, please make sure
to point to the right GDB executable).

The emulator provides two transport protocols for remote debugging:

- TCP: allows debugging through TCP using port 55555 (or any specified) port.
The advantage of using TCP is that it allows true remote debugging but it is
slower compared to the pipe method (pipe method does not work on Windows -
probably a restriction imposed by the CYGWIN port of GDB).
- PIPE: allows debugging through a PIPE between the emulator and GDB. This is a
lot faster than TCP and recommened on Unix systems.

Using TCP transport

To use the TCP transport, use the flag -Gtcp[:portnum] where portnum is an
optional port number to be used instead of 55555. VBA will wait for a GDB
connection on the specified port (printed on screen). Start GDB by passing the
.elf file, the

Latest Version

Details about this version:
(no information provided)

1.7.1 Intel (BeOS 5)     (241.3K)
0.9.1 Intel (BeOS 5)     (241.3K)

Most Popular
1. BeAIM - 4846
2. BePDF - 4531
3. Paladin - 4419
4. OpenTracker - 4175
5. AMD PCnet32 - 4143
6. nVidia 3D Driver - 3878
7. nVidia Driver - 3869
8. VMWare PCnet/PCI - 3793
9. Firefox - 3666
10. Duke Nukem 3D - 3501
11. ATI Radeon - 3479
12. Basilisk II - 3446
13. Sequitur - 3409
14. Traker.Newfs - 3409
15. SPICE - 3361
16. AbiWord - 3157

Account Status
  You are not logged in.