Duncan's WIP

[Duncan Twain]

finished new tool features, started fixing same-content-file-different-name

Software working fine. Managed to correct 13341 files so far (including manual verification). Still plenty left to amend.

[Crashdisk]

Your tool reminds me of something... It will be released publicly ?

[Cassiel]

"Commodore C64 - Collections - Derbyshire Ram (TOSEC-v2015-05-25_CM)" has lots of 'double description' errors where sets do not have a unique name, can you please fix.

Also (not a big deal for this release, but something to look at later) I've noticed the latest improved TDE picks up a bunch of new naming errors previously missed. Something to look at for next time. 

[Duncan Twain]

"Commodore C64 - Collections - Derbyshire Ram (TOSEC-v2015-05-25_CM)" has lots of 'double description' errors where sets do not have a unique name, can you please fix.

That probably because there are multiple filetypes in that folder present. Not much to do about, it's a bit overkill IMHO to create subfolders [D64], [G64], etc.

Also (not a big deal for this release, but something to look at later) I've noticed the latest improved TDE picks up a bunch of new naming errors previously missed. Something to look at for next time. 

Do you mean names like this: "(B)arty-Demo", that's the name of the demo and I know I've fixed a couple (as in created more DatExplorer errors. I think it's a bug in DatExplorer that it can't handle special characters in titles). Or did you mean something else?

Regards,
Duncan..

[Cassiel]

Either way it needs [a] or whatever. Same filename throws up errors in CMP (and others) and will rename file to whatever-0 or something. No good.

Re TDE, no I mean real errors. Use most recent TDE and you see what I mean... wrong country codes for example (UK rather than GB) previously missed because missread as Media Label and accepted.

[Duncan Twain]

aha, will try to fix; or next release.

fixed and uploaded

[Cassiel]

Derbyshire Ram? You going to upload?

What's with the new [BAS] DATs? Why they have PRG files in, are they misnamed?

OK, enough questions... 

[Cassiel]

Forgot to post WIP news, done now:
http://www.tosecdev.org/news/wip/114-wip-20150527a

[Duncan Twain]

Derbyshire Ram? You going to upload?

What's with the new [BAS] DATs? Why they have PRG files in, are they misnamed?

OK, enough questions... 

Those PRG files are actually are a specific type of PRG file, that's the reason to place them apart.

[Duncan Twain]

Derbyshire Ram? You going to upload?

hmm, that will be tricky (ie will need to write some code to do that in bulk). How bad is it to keep it for now?

[Duncan Twain]

Forgot to post WIP news, done now:
http://www.tosecdev.org/news/wip/114-wip-20150527a

Erhm, there have been no additions. My sole intention was to have only fixes in this release!

[Cassiel]

Derbyshire Ram? You going to upload?

What's with the new [BAS] DATs? Why they have PRG files in, are they misnamed?

OK, enough questions... 

Those PRG files are actually are a specific type of PRG file, that's the reason to place them apart.

So shouldn't they be in the [PRG] DATs still, but with [BASIC Format] or something as [moreinfo]?

The [XXX] split with DATs is for file format. These look like they still *.prg files where you would expect them to be *.bas.

[Cassiel]

Forgot to post WIP news, done now:
http://www.tosecdev.org/news/wip/114-wip-20150527a

Erhm, there have been no additions. My sole intention was to have only fixes in this release!

Damn copy & paste! Fixed.

[Cassiel]

Derbyshire Ram? You going to upload?

hmm, that will be tricky (ie will need to write some code to do that in bulk). How bad is it to keep it for now?

The DAT can't be included as it is, throws up errors. I have split between [D64] and [G64] since this makes sense anyway since it's 10,000 odd files.

[Duncan Twain]

Thanks, will do the dame here to avoid it happening in the future.