Zero arguments: disassemble one instruction at the current PC
One argument (address): disassemble one instruction at the address
Two arguments (address, size): disassemble 'size' instructions at 'address'
Three arguments (address, size, flags): disassemble 'size' instructions at 'address'
- If bit-3 is set (i.e. & 0x04): also print binary representation of instructions
- If bit-2 is set (i.e. & 0x02): prefix each instruction with its memory address
- If bit-1 is set (i.e. & 0x01): prefix each instruction with an index from the start of disassembly
Currently, plugins frequently call ConfigSaveSection(), which results in
the configuration being rewritten. I intend to submit patches to remove
these calls.
In exchange, the front-end should save the configuration at the latest
safe opportunity, to capture any changes before most chances of crashes,
power outages, kill -9, etc.
The '--nosaveoptions' option does not work currently, due to various
reasons.
1. The core saves its configuration when loaded (addressed in a separate
PR).
2. Plugins often save their configuration (to be addresses separately,
if this change is acceptable).
3. The UI does not parse --nosaveoptions early enough to avoid saving
the configuration (addressed in this patch).
This does not fully make --nosaveoptions work, but it is an incremental
improvement.
Definition of DD IPL rom and disk is done through the mupen64plus.cfg
file as follow:
[64DD]
IPL-ROM="path/to/64DD_IPL_ROM.bin"
Disk="path/to/64DDDisk.ndd"
Setting an empty IPL-ROM disable the 64DD.
Setting an empty Disk acts as if the 64DD had no disk plugged in.
You can also specify these at program startup using command-line
arguments --dd-ipl-rom and --dd-disk.
Definition of GB carts loaded inside transferpak is done through the
mupen64plus.cfg file as follow :
[TransferPak]
GB-rom-1 = "path/to/gb_rom.gb"
GB-ram-1 = "path/to/gb_rom.sav"
GB-rom-2 ...
GB-ram-2 ...
Setting an empty GB ROM acts as if GB cart was removed form TransferPak.
Setting an empty GB RAM let the Core generate a blank save file.
These parameters are modifiable during emulator execution. You just need
to trigger the GB cart change button, and these parameters will be
reloaded.
You can also specify these at program startup using command-line
arguments --gb-{rom,ram}-{1,2,3,4}
