Hi Roman

U're right about new CM copyright, but according your last modify u cannot publish dats they manage emu stuff maybe u don't own (like Goodtools).

Waitin' your reply.

Bye

> U're right about new CM copyright, but according your last modify u cannot
> publish dats they manage emu stuff maybe u don't own (like Goodtools).


It's not allowed to use any datfile on data you don't own legally. That doesn't mean datfiles are forbidden. Datfiles are just a collection of file attributs which are freely available since you can't reconstruct any of the original data from it. Hashvalues aren't a unique identification of the original data either.

Besides the goodtool's datfile aren't up2date anyway and will be removed sooner or later.

I'll convert all my dat in other format too to avoid troubles.
Bye

> > U're right about new CM copyright, but according your last modify u cannot
> > publish dats they manage emu stuff maybe u don't own (like Goodtools).
>
>
> It's not allowed to use any datfile on data you don't own legally. That doesn't
> mean datfiles are forbidden. Datfiles are just a collection of file attributs
> which are freely available since you can't reconstruct any of the original data
> from it. Hashvalues aren't a unique identification of the original data either.
>
> Besides the goodtool's datfile aren't up2date anyway and will be removed sooner
> or later.
>

> I'll convert all my dat in other format too to avoid troubles.

eh? I guess you haven't understand anything what I told you. You can write datfiles for whatever you want. There are not restrictions about datfiles...
Please learn to read carefully. It's about which files you scan, not which datfile you use.

> > I'll convert all my dat in other format too to avoid troubles.
>
> eh? I guess you haven't understand anything what I told you. You can write
> datfiles for whatever you want. There are not restrictions about datfiles...
> Please learn to read carefully. It's about which files you scan, not which
> datfile you use.
>

Hi
I known how to read.
From CM 3.66a:

- You're not allowed to use clrmamepro for managing filesets and files which you don't legally own. (So u cannot use CM
to manage (using or creating a dat) on stuff without legal owning).
- This also includes building up collections of such files.
(What could i build up on such files? Maybe a dat.)

U wrote those words above.

See u next time.

Bye :)

> > > I'll convert all my dat in other format too to avoid troubles.
> >
> > eh? I guess you haven't understand anything what I told you. You can write
> > datfiles for whatever you want. There are not restrictions about datfiles...
> > Please learn to read carefully. It's about which files you scan, not which
> > datfile you use.
> >
>
> Hi
> I known how to read.
> From CM 3.66a:
>
> - You're not allowed to use clrmamepro for managing filesets and files which you
> don't legally own. (So u cannot use CM
> to manage (using or creating a dat) on stuff without legal owning).
> - This also includes building up collections of such files.
> (What could i build up on such files? Maybe a dat.)
>
> U wrote those words above.
>
> See u next time.


Oh boy...you don't get it. You're a helpless fella...

Using dats on filedata you own legally is absolutely ok. The data provided in the dats (no matter which dat) is perfectly ok.
Scanning/rebuilding/merging files you don't own legally is forbidden, no matter which datfile you use.

I guess you have problems understanding the terms datfile and filecollections / filesets.

> > > > I'll convert all my dat in other format too to avoid troubles.
> > >
> > > eh? I guess you haven't understand anything what I told you. You can write
> > > datfiles for whatever you want. There are not restrictions about datfiles...
> > > Please learn to read carefully. It's about which files you scan, not which
> > > datfile you use.
> > >
> >
> > Hi
> > I known how to read.
> > From CM 3.66a:
> >
> > - You're not allowed to use clrmamepro for managing filesets and files which
> you
> > don't legally own. (So u cannot use CM
> > to manage (using or creating a dat) on stuff without legal owning).
> > - This also includes building up collections of such files.
> > (What could i build up on such files? Maybe a dat.)
> >
> > U wrote those words above.
> >
> > See u next time.
>
>
> Oh boy...you don't get it. You're a helpless fella...
>
> Using dats on filedata you own legally is absolutely ok. The data provided in
> the dats (no matter which dat) is perfectly ok.
> Scanning/rebuilding/merging files you don't own legally is forbidden, no matter
> which datfile you use.
>
> I guess you have problems understanding the terms datfile and filecollections /
> filesets.
>

Ok dude u're right like your wrong definitions.

Bye.

> Ok dude u're right like your wrong definitions.

There are no wrong definitions. A datfile is a datfile, filesets are filesets and filecollections are filecollections. If you don't understand this, while all the other do, I can't help you. If you already have fears breaking any licence, I expect you DO scan files you don't own legally. So I guess I have to report you in any way......8)

So...once again (and this DOES match the docs)

Datfile - plain textfile which contains file attributs like size, hashvalues and names grouped by sets. No binary data of the listed files included.

Fileset - a set of files, usually kept in a folder or a zipfile.

Filecollections/filesetcollection - actual files on your harddisk.

You can use clrmamepro with any datfile you want. Loading a datfile into clrmamepro is no problem.
As soon as use (scan/rebuild/merge/etc) clrmamepro on files on your harddisk which you don't own legally (and this of course doesn't include the datfile, since you do own that legally in any case), you're on the 'bad guy' side.


By the way...this hasn't changed since 1997.