kaichou123
commented
4 years ago 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
andrebrait
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:
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 :-)