The end of the ROMDB in openMSX? help needed

Prophet (2415)

10-10-2022, 20:19

the openMSX romdb in it's current form is close to 18 years old, the XML output is used for auto recognizing mapper types and gives openMSX feedback on what program/game is on the cart

During the last 2 years corruption has creeped up on the SQLLite database. I expect about 2~5% of corruption on the romdb which still is a lot considering that there are over 7000 entries.

Anyway - I don't feel like cleaning up the mess anymore or reprogramming the web interface to use another SQL solution. If anyone wants to take over the record keeping (adding/fixing of entries) let me know.

!login ou Inscrivez-vous pour poster

Par gdx

Enlighted (6429)

11-10-2022, 00:22

To bad. I hope someone will take up the torch. Otherwise, there is an alternative in yaml format here which could be interesting when it will be complete. This list was created for another reason but it could be used by openMSX or other projects.

Par Manuel

Ascended (19677)

11-10-2022, 00:35

I guess the database can be rebuilt with the XML data that comes with openMSX.

Par Vampier

Prophet (2415)

11-10-2022, 13:49

the xml data reflects the corruption already - comparing old SQLLite data to each other is easier.

Par Metalion

Paragon (1628)

11-10-2022, 20:07

I seem to remember that someone, long ago, proposed for the mapper information to be included in the rom file. Just a header with a few bytes, containing the necessary information. Problem solved. The idea was simple and failproof.

And yet, I also remember that there was so much bickering and fighting about it, that it was dropped.
To this day, I still don't understand why we did not choose such a great idea.

Par Vampier

Prophet (2415)

15-10-2022, 20:26

https://msx.org/forum/msx-talk/general-discussion/ideapropos...

you mean this one?

Par Vampier

Prophet (2415)

09-11-2022, 22:36

Since no one seems to care about auto picking mappers for openMSX I declare this database as dead.

Par Manuel

Ascended (19677)

09-11-2022, 23:17

Can you make clear what is wrong with the current XML file, so what is corrupted? Just a few examples would be enough to get an idea.

Par Vampier

Prophet (2415)

13-01-2023, 03:37

All roms need to be verified - for some reason due to database corruption several ROMs ended up under the wrong title. Everything related to the ROM (mapper/sha1 etc) is correct except the title.