Hello, all. Just wondering if anyone else has realized that the the DS-Scene Rom Tool's databases have conflicting entries. I found this while comparing good, bad, and trusted dumps on No-Intro's Dat-o-matic. As in, on the Dat-o-matic, there are 2 entries for both 4225 - Kingdom Hearts 358/2 Days and 5473 - Kingdom Hearts Re:Coded, one BAD (Because of an underdumped header for both of them) and the other TRUSTED DUMP (meaning not verified, but trusted), for each. On DS-Scene both these games are the equivalent of the ones tagged BAD on No-Intro, so in my opinion they should be listed as XXXX releases. BUT, while using the DS-Scene Rom Tool, 358/2 Days uses the CRC32 of the TRUSTED DUMP (Which it shouldn't be) and Re:Coded uses the CRC32 of the BAD dump (Which it should be). I find that release entries should be added for the "good" dumps and the release numbers for the "bad" dumps should be changed to XXXX. Because of these problems, I can't have a "perfect" rom that is recognized by the DS-Scene Rom Tool. Just sayin'! Here are the CRCs: - 4225 BAD: CA3BC6C0 - 4225 TRUSTED DUMP: CD0E9477 - 5473 BAD: 0FAB9957 - 5473 TRUSTED DUMP: 28ACD394
Side Notes: These TRUSTED DUMP roms' release group could be marked as iND (If added, and I find that they should be), the CRCs are all for decrypted roms, and 4225 is put as 4223 on No-Intro.
This post has been edited by Triforce, Mon, November 7th, 2011 at 20:05
Reason: removed font
Signature
Code
.assembly HelloWorld { } .assembly extern mscorlib { } .class HelloWorld { .method static void Main() cil managed { .entrypoint .maxstack 1 ldstr "Hello, world of DS-Scene.net!" call void [mscorlib]System.Console::WriteLine(string) call int32 [mscorlib]System.Console::Read() pop ret } }
Comment on: DS-Scene Rom Tool Database Issues... entries for DS-Scene databases.
Oh, and I almost forgot! It would be great if someone knew of a way to get a hold of DS-Scene admins or something like that to notify them about the problem. Also, I just found mistakes with the DS-Scene AP Patch and the CMP Cheat Database: the CRC32s they use to recognize and load data for a rom (Patch, Cheat, and Info data) are different between the databases. ie:
4225 - Kingdom Hearts 358/2 Days: - Info: CD0E9477 (The TRUSTED DUMP one) - Patch: CA3BC6C0 (The BAD dump one) - Cheats: It only shows the CRC for the header, but after testing, it's for the BAD dump (This header is underdumped, so I can safely claim this)
5473 - Kingdom Hearts Re:Coded: - Info: 0FAB9957 (The BAD dump one) - Patch: 0FAB9957 (The BAD dump one) - Cheats: Once again, it only shows the CRC for the header, but after testing, it's for the BAD dump (As already stated, this header is underdumped, so I can safely claim this)
Now my hopes of having a "perfect" rom with cheat compatibility and a proper AP patch that still gets all these aspects properly recognized by the DS-Scene Rom Tool have surely been crushed!!! Ah well, c'est la vie des conservateurs et conservatrices de la scène pour DS!
----------- auto merged post -----------
To be able to contact whoever is in charge of the constantly updated databases, or to find someone who knows how to, because I obviously don't! Good day to you all.
This post has been edited by Triforce, Mon, November 7th, 2011 at 20:05
Reason: removed font
Signature
Code
.assembly HelloWorld { } .assembly extern mscorlib { } .class HelloWorld { .method static void Main() cil managed { .entrypoint .maxstack 1 ldstr "Hello, world of DS-Scene.net!" call void [mscorlib]System.Console::WriteLine(string) call int32 [mscorlib]System.Console::Read() pop ret } }
Comment on: DS-Scene Rom Tool Database Issues... entries for DS-Scene databases.
Thanks, I've edited the CRC32 for the XPA release 4225 so it's recognized by the tool now. You'll have to click the refresh button on the DS-Scene tab to get it to show up.
The no-intro trusted dump you mention has not been scene released so it hasn't been added to our list. We don't list web/p2p releases as it's impossible to keep track of everything that could potentially be out there.
If the trusted CRC dump you speak of gets scene released then it would replace the bad one that's currently listed as 4225. Anything wrong with the CMP or the AP databases can be directed to the people that maintain them.
There seem to be a few games in no-intro's collection that have header fixes found in their forums. The rom tool has actually had a collection "thing" for a while that will organise your roms but due to such conflicting CRC information and dodgy patches hanging around, I was a bit reluctant to release it. It's been sat here for a while so maybe I will release it as a separate beta update so we can get a community test going which should capture all of these issues.
If anyone feels like they can destroy their rom collection in the nature of science then let me know here and I'll roll up a beta pack to distribute.
ok, call me a noob, but ive been trying for 3 hours to put the rom tool on my sons 3ds and cant get it to work. Ive looked all over for soemthing that says how to install this and have had no luck. I copied the whole folder to his main root of the sd card but when i load the cart it wont run. Any help for a noob?
Signature
Comment on: DS-Scene Rom Tool Database Issues... entries for DS-Scene databases.
Sorry xxtoddxx, but the DS-Scene Rom Tool isn`t a 3DS games or anything lol . It`s a program for your computer that you load the roms into to be checked.
Signature
Code
.assembly HelloWorld { } .assembly extern mscorlib { } .class HelloWorld { .method static void Main() cil managed { .entrypoint .maxstack 1 ldstr "Hello, world of DS-Scene.net!" call void [mscorlib]System.Console::WriteLine(string) call int32 [mscorlib]System.Console::Read() pop ret } }
multi 
options 
Just sayin'! 
Sun, November 6th, 2011 at 21:28
top 
Good day to you all.
![[User Posted Image]](http://files-ds-scene.net/retrohead/pullblox.jpg)
