Differences

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

--- submission:general [2023/04/11 22:33] – hiccup
+++ submission:general [2024/08/12 16:15] (current) – [Required Dump Info] hiccup
@@ Line 9: / Line 9: @@
 ==== Required Dump Info ====
-The most basic information necessary for verifying a game dump are the hashes/fingerprints generated from the ROM file as well as the dumping tool including hardware, firmware, and software version. **You can use [[https://www.romhacking.net/utilities/931/|GameHeader]] to get all this info in one go, on windows (or Linux/macOS using wine/mono)**. Or you can use common/built-in utilities:
+The most basic information necessary for verifying a game dump are the hashes/fingerprints generated from the ROM file as well as the dumping tool including hardware, firmware, and software version.
+**You can use [[https://www.romhacking.net/utilities/931/|GameHeader]] to get all this info in one go, on Windows (or Linux/macOS using wine/mono), or a common tool like 7-Zip, HashTab or HxD**. Or you can use built-in utilities:
 Size/hashes:
-  * **Size**: The size of the ROM in bytes. You can view this in your file manager, or on GNU/Linux and macOS, in the terminal run <code bash> wc -c ROMFILENAME</code>
+  * **Size**: The size of the ROM in bytes. You can view this in your file manager, or on GNU/Linux and macOS, in the terminal run ''wc -c ROMFILENAME''
-  * **CRC32**: On GNU/Linux and macOS, in the terminal run <code bash>crc32 ROMFILENAME</code>On Windows, use [[https://github.com/namazso/OpenHashTab|OpenHashTab]] or [[https://mh-nexus.de/en/hxd/|HxD]].
+  * **CRC32**: On GNU/Linux and macOS, in the terminal run ''crc32 ROMFILENAME''.
-  * **MD5**: On GNU/Linux, in the terminal run <code bash>md5sum ROMFILENAME</code>On macOS, in the terminal run <code bash>md5 ROMFILENAME</code>On Windows, in a PowerShell window run <code powershell>Get-FileHash ROMFILENAME -Algorithm MD5</code>
+  * **MD5**: On GNU/Linux, in the terminal run ''md5sum ROMFILENAME''On macOS, in the terminal run ''md5 ROMFILENAME''. On Windows, in a PowerShell window run ''Get-FileHash ROMFILENAME -Algorithm MD5''
-  * **SHA-1**: On GNU/Linux and macOS, in the terminal run <code bash>shasum -a 1 ROMFILENAME</code>On Windows, in a PowerShell window run <code powershell>Get-FileHash ROMFILENAME -Algorithm SHA1</code>
+  * **SHA-1**: On GNU/Linux and macOS, in the terminal run ''shasum -a 1 ROMFILENAME''. On Windows, in a PowerShell window run ''Get-FileHash ROMFILENAME -Algorithm SHA1''
-  * **SHA-256**: On GNU/Linux and macOS, in the terminal run <code bash>shasum -a 256 ROMFILENAME</code>On Windows, in a PowerShell window run <code powershell>Get-FileHash ROMFILENAME -Algorithm SHA256</code>
+  * **SHA-256**: On GNU/Linux and macOS, in the terminal run ''shasum -a 256 ROMFILENAME''. On Windows, in a PowerShell window run ''Get-FileHash ROMFILENAME -Algorithm SHA256''
 If the game is made up of a folder with subfolders, follow the [[https://dumping.guide/directory_dir2dat_guide|Dir2Dat guide]] for generating the hashes.
@@ Line 25: / Line 27: @@
 PCB photos are an important, but often overlooked aspect of preservation. Along with providing some evidence that the game is genuine, they also help with verifying version numbers, manufacturing dates, and documenting component usage across games.
-Photos should include all sides of packaging, physical media, and the PCB, with all text clearly readable, including any imprinted/stamped text and any serials on ROM chips hidden under batteries. You may need to take photos at an angle to capture some of this information. However taking apart DS/3DS carts to get PCB photos is generally unnecessary.
+Photos should include all sides of packaging, physical media, and the PCB, with all text clearly readable, including any imprinted/stamped text and any serials on ROM chips hidden under batteries. You may need to take photos at an angle to capture some of this information. However taking apart DS/3DS carts to get PCB photos is generally unnecessary. If possible, details/other labels that are underneath labels should also be photographed.
 ==== Common dump info structure ====
@@ Line 34: / Line 36: @@
 Game name:
-Dump tool:
+Dumper (person who dumped the ROM):
+Affiliation (if applicable):
+Dump tool:
 Dump date (YYYY-MM-DD):
 Dump logs:
@@ Line 45: / Line 49: @@
 SHA-256 hash:
-Links to PCB photos/ box scans:
+Links/attachments to Cart/PCB/box photos/scans:
 </code>
@@ Line 68: / Line 72: @@
 Please note if you have modified the physical media in any way.
-DS/DSi/3DS dumps should include hashes for the originally dumped (encrypted) file, plus if it is a new ROM, the decrypted equivalent. Make a copy of the file, then use [[https://github.com/SabreTools/NDecrypt|ndecrypt]]. You can use the ''-h'' flag to hash the ROM at the same time as decrypting it, saving time. Note that wooddumper produces decrypted files by default, so re-encryption with ndecrypt is needed for that instead.
+DS/DSi/3DS dumps should include hashes for the originally dumped (encrypted) file, plus if it is a new ROM, the decrypted equivalent. Make a copy of the file, then use [[https://github.com/SabreTools/NDecrypt|ndecrypt]]. You can use the ''-h'' flag to hash the ROM at the same time as decrypting it, saving time. Note that wooddumper and GodMode9i produce decrypted files by default, so re-encryption with ndecrypt is needed for that instead.
 ==== Submission ====