This menu will vary dynamically depending on various conditions. For instance, if there is no Game Profile currently selected the Boot options will not show.
The current Default Boot Profile. This is the profile EmVoy boots into in the absence of a command line switch specifying this. The boot profile System must match that of the emulator to boot the game from this menu. If there's a mismatch, you'll be prompted and you can change to a matching system via Change Boot Profile.
This is the current Game Profile being used and when it was last updated. It consists of the game name and the time of Game Profile creation. NB. If you delete an emulator then later create another one which fills the same slot, the Game Profile name will not reflect this until it is edited again. In the example above, if you were to delete or replace Emu 2 (Mednafen) with another emulator (e.g. WinVice64) - the Game Profile would try and boot the gamefile via WinVice. That's what the two "(Updted)" are for - so you can compare when the Game Profile was last updated with when the emulator was last updated.
The short version: Once you have your emulators setup - try and leave that emulator mapped against that number. Editing OK, but be careful with delete.
The Emulator number and name mapped against the Game Profile. Also, shows the date the emulator profile was last updated.
The default Emu mapped against this Game Profile. When the gamefile is booted via command line, EmVoy checks to see if a Default Emu is set (via Game Profiles>Make this Default Profile for Gamefile) and then uses this emu to boot the game. In the example above, Beyblade will boot into ePSXe rather than Mednafen when booted via command line. However, if you boot the game from the admin menu, it will use Emu rather than DefEm.
You can specify command line paramters for the emulator in a Game Profile. This will replace those specified in the Emulator Profile. Game-specific cmd line params are shown here. In this example, Mednafen will launch "Mednafen.exe -nogui"
You can specify to launch Support Apps before Emu launch in the Boot Profile, Emulator Profile and the Game Profile. This displays info regarding this (B=boot; E=Emu and G=Game). If specified in Game Profile, this replaces any specified in the Boot and Emulator Profile. In the example above, the Boot profiles directs support apps 9 and 1 start; the emulator profile support app2 and the game profile 8 and 9. This will result in only 8 and 9 booting. However, if 8+9 wasn't specified, it'd boot with 9,1 and 2 (as EmVoy boots all support apps in both boot and emulator profiles).
Whether to keep, ask or delete quicklaunch folder. Set in Boot Profiles, but can be modified within Game Profiles - this here is the final outcome of both.
Whether DTools is used to mount image. Specified in Emulator and Game profile (latter superseding former). This represents final outcome.
Save emulator settings on exit game. Set in Emulator profile.
Whether Leave Disc Image Mounted set to true in DTools Hacks. Means when you boot a game from EmVoy admin menu, skips mounting and unmounting the image.
Shows whether an image is mounted in DTools presently. You can see info about the mounted image on the DTools Hacks menu.
Shows whether Keep backups of game settings enabled in Emulator or Game Profile (again, latter supersedes the former).
Covered here
Covered here
Covered here
Covered here
Use full-boot command lines to boot game. See Emulator setups.
Use setup boot for game.
Covered here
As one would expect. :)