Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request #26

Open
kaichou123 opened this issue May 18, 2020 · 5 comments
Open

Feature Request #26

kaichou123 opened this issue May 18, 2020 · 5 comments

Comments

@kaichou123
Copy link

Hello,

I've been working on a python project as I have time, but it's slow going, when I ran across your script. You're script is so much farther along and does a lot of what I'd like to do. Do you think you could add MD5 hash verification and missing roms to your scripts? I can share what I've created thus far, it is a hack'n'slash script, but you are welcome to glean whatever you want from it.

-Create a missing ROMs list, and maybe something to help me rename the roms I have appropriately. Still trying to figure out how to handle the different versions of files.
-Verify the MD5/CRC32 Hash and compare it to the info from No-Intro DATs
-Filter out Beta/proto and various other keywords to create a rom-set


From Andre Brait


My script already checks file hashes using SHA-1 and it's already capable of handling renaming and generating a list of missing ROMs, though I don't exactly document it.

In order to do that, just get a "Standard DAT" on DAT-O-Matic, instead of a "Parent/Clone XML" DAT. Use it with the tool and it will:

  • Scan your ROMs and check if they match some of the ROMs from the DAT using SHA-1 (which is the most reliable method so far, though I'll add MD5 and size+CRC32 on v2.0)
  • Rename (if you choose to move them), or copy with the new name, the files that matched.
  • Generate a file called "generate.log" in the script's folder letting you know what was missing (when used with a Parent/Clone XML DAT, this serves a different function, but with a Standard DAT, it'll be the same as a missing files list).

This is all going to work a lot better on v2.0 ;-)

Thanks for the email and I would like to see your tool if you want. Maybe there's something I can use :-)

@kaichou123
Copy link
Author

Thank you! I'll repost on the issues page.

Thats great! Why didn't I think of using that to identify the file? I've been basing it on names, but you totally should use the hash.

-I got to the point where my script fully works on non-zipped files. I started to work on figuring out the best way to deal with zipped, 7zip, winrar files. Didn't get very far.
-win32gui to give me a directory and file selector. Though I started to look at Python GUI's.
-I went down a different road than the .dat file. It's been a few months since I worked with these files, but I seem to recall that they used to have an option to download everything as a CSV file. So I had used that since I was more familiar with it. However i can't find where to download the csv files anymore.
-I did a lot of fighting on figuring out how to get things in the right format for comparing things. Lists vs generator vs dictionary vs who knows what else. So far that's been the biggest bane of my existence since different libraries output to different types. Thus my noviceness.

If you have any questions on how my script works, let me know.

@ghost
Copy link

ghost commented May 30, 2021

I am running into a little issue. The generate.log that is created never has any content. It is always 0 bytes in size. How can I fix that? Also is 2.0 still in progress?

@andrebrait
Copy link
Owner

andrebrait commented May 30, 2021 via email

@ghost
Copy link

ghost commented May 30, 2021

It shows me what roms are found and copied however it does not show me what is missing...

@andrebrait
Copy link
Owner

andrebrait commented Jun 8, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants