Guest wrote:what should I do? delete 2500 bad roms? before upgrading to version 2.01 they were all green (good)!
No, you should not delete any ROM unless you're absolutely sure they're "bad". In practice this is more difficult than it sounds, as you've experienced yourself.
You should realise that what is considered good and bad changes. Some ROM dumps that were labeled as good by old versions of GoodSNES were later labeled as bad. IIRC the reverse has happened too (although rare).
Perhaps you could post some info about one of the dumps that were labeled as bad by RomCenter (snes.dll), but as good by GoodSNES 2.01.
Dweezledap wrote:Since I don't have the complete SNES sets I have no way to verify how accurate the datafile is.
Perhaps you should ask for testers.
Dweezledap wrote:The only thing that comes to mind right now is perhaps it has to do with the change from crc to sha-1
That's very unlikely. It's "just" another checksum algorithm. AFAIK there weren't any clashes with CRC, so I don't know how it could make a difference.
Dweezledap wrote:[GoodSNES quote]
Basically what this means is you need to convert all your roms to deinterleaved (binary) format.
That quote does not imply that at all! It just means that GoodSNES doesn't recognise dumps in non-standard made-up formats. Cowering's decision was actually a good thing as it may help getting rid of those files. I mean, making them disappear from the internet.
Dweezledap wrote:A great tool for converting your roms is uCON64.
Thank you :-)
Dweezledap wrote:As for the RomCenter SNES datafile:
The SNES plugin has not been updated since before the 2.01 release of GoodSNES. This MAY be why it is showing the 280 roms as bad.
The SNES plug-in has not been updated, because until now I haven't received any feedback that it fails. Besides, the plug-in doesn't have to be updated just because here have been some new dumps. It recognises dumps in all the known copier formats, so unless it makes mistakes, there's no need to update it. Please note that it's far from perfect -- it's not difficult to make it fail. But making it fail-safe is not worth the effort.
Dweezledap wrote:A work around would be to remove the following line from the datafile "plugin=snes.dll".
Also you will have to use uCON64 to remove any header information, as well as converting your roms to deinterleaved format.
*If* you choose to not use the SNES plug-in. It's true that having all ROM dumps in headerless non-interleaved format makes calculating the CRC value fail-safe. The problem is how to get all your ROM dumps in that format. I would use uCON64 (of course), but I don't recommend using that tool for this task to anyone. I would certainly keep a copy of the original files. Perhaps NSRT has a higher success rate, mainly because people use it for this purpose.
Guest wrote:I downloaded ucon, now how can I "clean" up my roms collection? what is the correct input command?
It depends what you mean with cleaning up. You *can* for example convert all files to SWC format (headered, non-interleaved) with a command like:
Code: Select all
ucon64 -swc c:\snesromsinallkindsofformats -o c:\snesromsinswcformat
You could follow that command with this command:
Code: Select all
ucon64 -stp -hd c:\snesromsinswcformat -o c:\snesromslikeiwantthem
The first command will convert all files to SWC format and put the converted files in c:\snesromsinswcformat. It leaves the original files as they are. I
strongly advise to work with different directories (note the option -o).
The second command removes the headers from all files (-hd forces uCON64 to handle all files as having a header of 512 bytes, just in case) and puts the modified files in c:\snesromslikeiwantthem.
Dweezledap wrote:SNES can be one of the most screwed up collections because of all the different formats.
Right :-)
Dweezledap wrote:It won't be easy but with a little time and some reading/research you should be able to fix your set.
Exactly. And you'll certainly learn something in the process.
[quote="Guest"]what should I do? delete 2500 bad roms? before upgrading to version 2.01 they were all green (good)![/quote]
No, you should not delete any ROM unless you're absolutely sure they're "bad". In practice this is more difficult than it sounds, as you've experienced yourself.
You should realise that what is considered good and bad changes. Some ROM dumps that were labeled as good by old versions of GoodSNES were later labeled as bad. IIRC the reverse has happened too (although rare).
Perhaps you could post some info about one of the dumps that were labeled as bad by RomCenter (snes.dll), but as good by GoodSNES 2.01.
[quote="Dweezledap"]Since I don't have the complete SNES sets I have no way to verify how accurate the datafile is.[/quote]
Perhaps you should ask for testers.
[quote="Dweezledap"]The only thing that comes to mind right now is perhaps it has to do with the change from crc to sha-1[/quote]
That's very unlikely. It's "just" another checksum algorithm. AFAIK there weren't any clashes with CRC, so I don't know how it could make a difference.
[quote="Dweezledap"][GoodSNES quote]
Basically what this means is you need to convert all your roms to deinterleaved (binary) format.[/quote]
That quote does not imply that at all! It just means that GoodSNES doesn't recognise dumps in non-standard made-up formats. Cowering's decision was actually a good thing as it may help getting rid of those files. I mean, making them disappear from the internet.
[quote="Dweezledap"]A great tool for converting your roms is uCON64.[/quote]
Thank you :-)
[quote="Dweezledap"]As for the RomCenter SNES datafile:
The SNES plugin has not been updated since before the 2.01 release of GoodSNES. This MAY be why it is showing the 280 roms as bad.[/quote]
The SNES plug-in has not been updated, because until now I haven't received any feedback that it fails. Besides, the plug-in doesn't have to be updated just because here have been some new dumps. It recognises dumps in all the known copier formats, so unless it makes mistakes, there's no need to update it. Please note that it's far from perfect -- it's not difficult to make it fail. But making it fail-safe is not worth the effort.
[quote="Dweezledap"]A work around would be to remove the following line from the datafile "plugin=snes.dll".
Also you will have to use uCON64 to remove any header information, as well as converting your roms to deinterleaved format.[/quote]
*If* you choose to not use the SNES plug-in. It's true that having all ROM dumps in headerless non-interleaved format makes calculating the CRC value fail-safe. The problem is how to get all your ROM dumps in that format. I would use uCON64 (of course), but I don't recommend using that tool for this task to anyone. I would certainly keep a copy of the original files. Perhaps NSRT has a higher success rate, mainly because people use it for this purpose.
[quote="Guest"]I downloaded ucon, now how can I "clean" up my roms collection? what is the correct input command?[/quote]
It depends what you mean with cleaning up. You *can* for example convert all files to SWC format (headered, non-interleaved) with a command like:
[code]ucon64 -swc c:\snesromsinallkindsofformats -o c:\snesromsinswcformat[/code]
You could follow that command with this command:
[code]ucon64 -stp -hd c:\snesromsinswcformat -o c:\snesromslikeiwantthem[/code]
The first command will convert all files to SWC format and put the converted files in c:\snesromsinswcformat. It leaves the original files as they are. I [b]strongly[/b] advise to work with different directories (note the option -o).
The second command removes the headers from all files (-hd forces uCON64 to handle all files as having a header of 512 bytes, just in case) and puts the modified files in c:\snesromslikeiwantthem.
[quote="Dweezledap"]SNES can be one of the most screwed up collections because of all the different formats.[/quote]
Right :-)
[quote="Dweezledap"]It won't be easy but with a little time and some reading/research you should be able to fix your set.[/quote]
Exactly. And you'll certainly learn something in the process.