Since updating my romset to MAME32 0.89, I found a descrepancy between the audit results from ClrMame (which reported all ok, aside from missing samples of course) and MAME32 (which reported 5 missing). After having MAME itself do a verify scan on all roms, I set out to fix this... and upon some investigation, I found that 4 sets had multiples of the same file within the same zip - the first being the old file MAME32 was seeing, and the next four or five being the new files from the update. (Suffice it to say, this confused me greatly when I decompressed one of the affected ZIPs to a new folder, and WinZip asked if it could overwrite some files... ^^;)

It seems that ClrMame appeared to try and apply the updated roms to the sets, but without removing the old files first. I've fixed this by manually recompressing all of the affected sets to remove the duplicates, but I'm wondering if anyone else had this problem, and if the cause could be looked into, since nothing like this (that I've noticed) occurred with previous versions. (I updated ClrMame to 3.50a just prior to rebuilding for the 0.89 update.)

The sets I found affected: galaga88, ddux, titlefu [titlef], liberatr. (The fifth, liberat2 [liberatr] had no problem itself, but needed its parent fixed.)

I'm a bit worried about other sets being affected too, as this could eventually turn into a huge space-waster...

* StarCreator *