User Tools

Site Tools

Trace:
merge_types

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
merge_types [2022/11/20 11:19] – johnsancmerge_types [2023/07/04 08:36] (current) – johnsanc
Line 10: Line 10:
 A non-merged set is ideal for those who only want to use specific games on their PC, Raspberry Pi, etc. Since all games are self-contained, there is no need to search for the dependent parent files, BIOS files, and device files. A non-merged set is ideal for those who only want to use specific games on their PC, Raspberry Pi, etc. Since all games are self-contained, there is no need to search for the dependent parent files, BIOS files, and device files.
  
-<WRAP round info>Even though non-merged games normally do not include BIOS or DEVICE files within the game, RomVaut does include these within the game's set. This ensures that every single game can be copied and ran independently without the need for any extra files.</WRAP>+<WRAP info>Even though non-merged games normally do not include BIOS or DEVICE files within the game, RomVaut does include these within the game's set. This ensures that every single game can be copied and ran independently without the need for any extra files.</WRAP>
  
 ===== Split Set ===== ===== Split Set =====
 A split set is one where the parent set contains all of the normal data it should, and the clone sets contain only what has changed as compared to the parent set. This saves some space, but isn’t quite as efficient as a merged set. The clone sets can't operate without their parent set. A split set is one where the parent set contains all of the normal data it should, and the clone sets contain only what has changed as compared to the parent set. This saves some space, but isn’t quite as efficient as a merged set. The clone sets can't operate without their parent set.
  
-<WRAP round info>The parent and clones in split sets do not include BIOS or DEVICE files - they are separate files within the set. This is per MAME design. For example: 100lions.zip, which has no BIOS in the parent; and galaga.zip, which has no device files in the parent.</WRAP>+<WRAP info>The parent and clones in split sets do not include BIOS or DEVICE files - they are separate files within the set. This is per MAME design. For example: 100lions.zip, which has no BIOS in the parent; and galaga.zip, which has no device files in the parent.</WRAP>
  
  
Line 21: Line 21:
 A merged set takes the parent set and its clone sets and puts them all inside the parent set's folder or archive. Using Pac-Man as an example: A merged set takes the Puckman, Midway Pac-Man (USA) sets, along with various bootleg versions, and combines it all into puckman.zip (the parent's archive). A merged set takes the parent set and its clone sets and puts them all inside the parent set's folder or archive. Using Pac-Man as an example: A merged set takes the Puckman, Midway Pac-Man (USA) sets, along with various bootleg versions, and combines it all into puckman.zip (the parent's archive).
  
-<WRAP round info>The parent games in a merged set do not include BIOS or DEVICE files - they are separate files within the set. This is per MAME design. For example: 100lions.zip, which has no BIOS in the parent; and galaga.zip, which has no device files in the parent.</WRAP>+<WRAP info>The parent games in a merged set do not include BIOS or DEVICE files - they are separate files within the set. This is per MAME design. For example: 100lions.zip, which has no BIOS in the parent; and galaga.zip, which has no device files in the parent.</WRAP>
  
  
merge_types.txt · Last modified: 2023/07/04 08:36 by johnsanc