Roman,

Is there currently an option to rename an exe-based datfile? I like to have the version number in the title of the datfile and, at the moment, when a new version of Mame is released, I do 1 of the following :

- Delete the existing datfile and recreate a new one with the new exe.
- Rename all of the files in the datfiles, fastscans, logs, scans & settings directories (and edit the file in the datfiles dir to reflect the new description). Then, load the datfile, get the message that the exe has changed, and let CMPro get the new information.

The 2nd one *almost* works, but the files saved in the logs & fastscans directories use the old file name. (ahh...I've just found where it's getting these filenames... Scanner_FastScan & Scanner_LogFile settings in the settings file)

So, is it possible to include a Rename function for exe-based datfiles, or should I just stick with my 1st option (delete then re-create)?

Renaming of an exe-based datfile is currently only possible if you manually edit the dat/settings file. People should use something like "Current MAME" for the descriptionstring.

Roman Scherzer
ClrMamePro

> Renaming of an exe-based datfile is currently only possible if you manually edit
> the dat/settings file. People should use something like "Current MAME" for the
> descriptionstring.
>
> Roman Scherzer
> ClrMamePro
>
Thanks for the reply, Roman.

I know it's not really important to have the version number in there, but I still like to see it. I was about to write a quick tool to give me a report on the datfiles, so I'll add this functionality into that program ;)

Either that, or with the exe-based datfiles, the 'version' field is not used. I might just add this line to the created datfile, and update it as necessary. Do you see any potential issues with this?

> > Renaming of an exe-based datfile is currently only possible if you manually
> edit
> > the dat/settings file. People should use something like "Current MAME" for the
> > descriptionstring.
> >
> > Roman Scherzer
> > ClrMamePro
> >
> Thanks for the reply, Roman.
>
> I know it's not really important to have the version number in there, but I
> still like to see it. I was about to write a quick tool to give me a report on
> the datfiles, so I'll add this functionality into that program ;)
>
> Either that, or with the exe-based datfiles, the 'version' field is not used. I
> might just add this line to the created datfile, and update it as necessary. Do
> you see any potential issues with this?
>


well...then use the versionstring ;) manually patch it.

Roman Scherzer
ClrMamePro