You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful if GodMode9 allowed the user to save the result of a SHA256/SHA1 sum, even if the file is located in read-only location (e.g. GAMECART). l
E.g. it would save the file to SD:/gm9/out, or allow the user to select the location. This is useful when hashing gamecart roms (without first transferring to SD card).
My current workaround is to take a screenshot of the hash result when its displayed on screen, then use OCR on PC to convert it to text quickly (for comparison with a known hash).
This might also be achievable via scripting, but I haven't got the hang of the GM9 scripting yet.
I know with sha1/sha256 you can usually tell if it differs from another hash looking at the first few character, but it seems sensible to actually compare the whole thing.
The text was updated successfully, but these errors were encountered:
It is achievable via scripting. Also keep in mind the issue with 4GiB carts here (one missing byte, thus wrong checksum). Anyways, writing the hash to the standard output folder would be an option. I'll look into that.
It would be useful if GodMode9 allowed the user to save the result of a SHA256/SHA1 sum, even if the file is located in read-only location (e.g. GAMECART). l
E.g. it would save the file to SD:/gm9/out, or allow the user to select the location. This is useful when hashing gamecart roms (without first transferring to SD card).
My current workaround is to take a screenshot of the hash result when its displayed on screen, then use OCR on PC to convert it to text quickly (for comparison with a known hash).
This might also be achievable via scripting, but I haven't got the hang of the GM9 scripting yet.
I know with sha1/sha256 you can usually tell if it differs from another hash looking at the first few character, but it seems sensible to actually compare the whole thing.
The text was updated successfully, but these errors were encountered: