Differences

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

--- side_buttons [2020/08/19 20:58] – [Update DATs] johnsanc
+++ side_buttons [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-===== The Side Buttons =====
+~~NOTOC~~
-==== Update DATs ====
+====== The Side Buttons ======
+\\
+-----
+===== Update DATs =====
 {{:buttons:btnupdatedats.png|Update Dats}}
 **Click  'Update DATs':** Scan the DATRoot directory and load in and new or updated DAT files.
-**Shift/Right Click  'Update DATs':** Will perform a full reload of all the DATs in DATRoot. Generally this should not be needed, so only use this for troubleshooting if a DAT does not seem to be processed correctly. For example, there may be changes between versions of RomVault that impact the way DATs are processed or directory settings applied. In this case a full reload ensures all DATs are processed the exact same way.
 When a new DAT comes out (Like going from MAME 0.223 to MAME 0.224), simply delete the MAME 0.223 DAT and replace it (in the same directory) with the DAT for MAME 0.224. Then Click on 'Update DATs'. Once this completes you will see exactly what has changed in the new DAT. You do not need to re-scan your ROMs as they have not changed. You just need to click on 'Find Fixes' followed by 'Fix ROMs' to update your MAME set the best it can be to match the updated DAT.
-----
+**Shift/Right Click  'Update DATs':** Will perform a full reload of all the DATs in DATRoot. Generally this should not be needed, so only use this for troubleshooting if a DAT does not seem to be processed correctly or after upgrading RomVault to a newer version. For example, there may be changes between versions of RomVault that impact the way DATs are processed or how directory settings applied. In this case a full reload ensures all DATs are processed the exact same way.
-==== Scan ROMs ====
+-----
+===== Scan ROMs =====
 {{:buttons:btnscanroms.png|Scan Roms}}
@@ Line 22: / Line 24: @@
 We could have approached this another way, as we knew we had a partial MAME ROM set, we could have manually made all the directories RomRoot/Arcade/MAME (Matching the directory structure we setup in Datroot) and just copied the MAME ROMs we had directly into that directory, and then scanned and fixed as before. Doing this is preferable if we know we have a set that is close to being correct, as Scanning these ROMs in the correct directory will then hopefully get you close to where you are wanting to be, and the 'Find Fixes' / 'Fix ROMs' steps will only have to fix/move the files that need to be corrected. (Instead of having to move every single file over from Tosort.)
-----
+-----
-==== Find Fixes ====
+===== Find Fixes =====
 {{:buttons:btnfindfixes.png|Find Fixes}}
@@ Line 32: / Line 33: @@
 This stage is just checking to see what repairs need to be done. No files are moved at this stage. You can now look in the UI to see what can/will be fixed when you hit the next button.
-----
+-----
+===== Fix ROMs =====
-==== Fix ROMs ====
 {{:buttons:btnfixfiles.png|Fix Files}}
@@ Line 46: / Line 46: @@
+-----
-----
+===== Generate Reports =====
-==== Reports ====
 {{:buttons:btnreport.png|Reports}}
-**Click 'Reports': ** Select an output directory, and RomVault will make a complete set of Fix DAT's
+**Click 'Generate Reports': ** Select an output directory, and RomVault will make a complete set of Fix DAT's
-Fix DAT's are a list of DAT that only contain the files you are missing, than can then be used to go out and find these missing files.
+Fix DAT's are a list of DAT that only contain the files you are missing. These DATs can then be used to help you find the files you're missing.