Non-TOSEC database

[Crashdisk]

Hi peo,
that's not quite true, I get very few disks out of the TOSEC collection. The Non-TOSEC project has 2 goals:
1-Identify uninteresting (highscore, minor alterations,...) or damaged disks that are not in TOSEC and that I don't want to integrate into TOSEC.
2-Identify disks that correspond to categories I'm not responsible for. This pre-identification will save time when the time comes to integrate them, and will also provide more reliable information on authors and dates when they have just been released.

Some disks have sometimes been discarded by mistake (more or less ... oops).

If you have disks from older versions that have disappeared from the latest official version, you can share them in The Zone, for example, to reintegrate them into TOSEC or ... Non-TOSEC.

[peo]

@Crashdisk I have usually got about 250 left-overs when scanning adf files from older Amiga TOSEC floppy collections (complete sets from various releases). I still have to sort away the (true, md5) duplicates between the left-overs before I can post what remains after also scanning against Non-TOSEC. I can post lists (and probably md5s) of the unsorted stuff earlier if that could be of any use for you.
I have just completed the hunt for the few thousand of missing files between the last full I had and the omst recent one. If I have not included any other files than the adfs, I have a total of 94673 files sorted by my application.

[Crashdisk]

Exploiting a hash list is laborious. There's no rush, so take your time.
A "few thousand files missing" ... we must have worked well then ^^

[peo]

My long reply was destroyed by having to log in again.. so the short version:
How do you handle md5 checksum duplicates within the same set (as "TOGA") or in separate sets (as "TOGA" <-> "Games/Public Domain/ADF") where the same md5 appears under different names ?

mysql> select dat,name,crc from roms where md5="6c474c7a7496d15ce7d0afe2ac857ec9";

+------+-------------------------------------------------------------------------+----------+

| dat  | name                                                                    | crc      |

+------+-------------------------------------------------------------------------+----------+

| 2300 | Trap Runner v1.0 (2018-12-30)(Night OWL Design - Retroguru)(FW).adf     | e820d14f |

| 2308 | TOGA 2019-01 (2019-01-16)(The Other Group of Amigoids)(Disk 5 of 5).adf | e820d14f |

| 2308 | TOGA 2019-04 (2019-04-19)(The Other Group of Amigoids)(Disk 3 of 5).adf | e820d14f |

+------+-------------------------------------------------------------------------+----------+

The (at least part of) reason I have only 94674 (found the last file) in my collection is that I only keep one copy of each unique file. There might be other problems with my scanner application, because I'm missing about 800 files in total (which might or might not be only the duplicates under different sets or names).
A quick check found 34 duplicated items, with all of them having one extra (execpt the "6c474c7a7496d15ce7d0afe2ac857ec9" mentioned above with two extras)

[Crashdisk]

At TOSEC, we don't like duplicates, but I've made an exception for the TOGA collection, which sometimes distributes disks that aren't their own.

A disk like "Trap Runner" should be in its own category, but on the other hand, the TOGA collection wouldn't be complete without it. As for the case of duplication within TOGA itself, this is a mistake on their part :

Toga-0119e         Trap Runner – Final release 1.0 of this well done platformer game. BOOTABLE
Toga-0419c         Trap Runner – Latest version of this cool classic platformer game by RetroGuru.  BOOTABLE