Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All Threads*Show in Threaded Mode


SubjectClrMamePro 3.30 released Reply to this message
Posted byRoman
Posted on04/15/04 03:27 PM



3.30

misc: new, faster zipscanner is enabled by default.

If you want to do an additional zipstructure test (like the
old engine), you can enable it in Settins->zip options.

Recommended if you want to do a final full scan, like when
scanning with sha1 enabled or similar things before burning ;)

misc: statistics time info differs fastscantime from scantime
misc: a little more source clean up
misc: preserve archive date/time default state is now "disabled"
misc: some text renames here and there...


Roman Scherzer
ClrMamePro


Subjectquestion new Reply to this message
Posted byIceMan
Posted on04/15/04 05:32 PM



I like the preserve date/time change, sounds useful for my fixes as I mentioned earlier!

Anyway, I CLRMAMEd the whole set and get a handful of messages like:

wrong name: D:\Emulator\mame32\roms\EARTHINV.ZIP [wrong: EARTHINV] [right: searthin] [not fixed]

But I chose Yes To All but none were renamed/deleted/anything! Am I missing something?

Cheers for the speedy new version anyway!

Ice




SubjectRe: question new Reply to this message
Posted byRoman
Posted on04/15/04 05:50 PM



> But I chose Yes To All but none were renamed/deleted/anything! Am I missing
> something?

Yes ;)
The renaming fails if the "new name" already exists. The sets+name check is fuzzy...it takes the best fit name which doesn't have to be correct though. To prevent overwriting an already existing set, the rename fails. You can use Scanner->Advanced->Move Not Renamed Sets To Backup instead. An enabled fixmissing will find possible missing files there then....after the namefix moved it there.

Roman Scherzer
ClrMamePro


Subjectthanks, that sorted it! (nt) new Reply to this message
Posted byIceMan
Posted on04/15/04 06:07 PM



> > But I chose Yes To All but none were renamed/deleted/anything! Am I missing
> > something?
>
> Yes ;)
> The renaming fails if the "new name" already exists. The sets+name check is
> fuzzy...it takes the best fit name which doesn't have to be correct though. To
> prevent overwriting an already existing set, the rename fails. You can use
> Scanner->Advanced->Move Not Renamed Sets To Backup instead. An enabled
> fixmissing will find possible missing files there then....after the namefix
> moved it there.
>
> Roman Scherzer
> ClrMamePro
>





View All Threads*Show in Threaded Mode