I generally keep my ROM sets backed up on DVD with some sets spanning multiple DVDs and I'll keep a folder of updated files on my hard drive when a .DAT is updated with new or changed data. The problem is, whenever a new .DAT comes out, I have to put the DVD's in one at a time to scan them with a full scan and then use the update folder for the new and changed files since the last DAT.

If the DATs had the ability to keep track of when an entry was added or modified and there was a way in the application to supply a start date to filter the scans, this would eliminate the need to go back to the original DVDS when I only need to scan for what has been added or modified within a specific timeframe.

Since a datfile is a plain text file with no checksums or similar and freely editable, there is no guarantee at all that an additional 'valid_from' and/or 'valid_to' flag really flags new stuff correctly. Besides of that, datfile authors have to handle it manually/semi automatically, in other words: additional work for them...which I doubt they will invest.


Roman Scherzer

I have an even better idea. When updating a previous dat with a newer version, clrmamepro could give the option to create an additional difference dat by comparing the old dat with the newer one.

> Since a datfile is a plain text file with no checksums or similar and freely
> editable, there is no guarantee at all that an additional 'valid_from' and/or
> 'valid_to' flag really flags new stuff correctly. Besides of that, datfile
> authors have to handle it manually/semi automatically, in other words:
> additional work for them...which I doubt they will invest.
>
>
> Roman Scherzer
>

no need, use mamediff instead


Roman Scherzer