Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

2761

clrmame Discussion / Re: Fix a single set

« on: 03 February 2011, 20:15 »

by the way...to enable all clones (and only clones) you need to enter

%c=?*

in the select sets field, followed by clicking on apply. Parent sets only is the same plus the logical not checkbox....

2762

clrmame Discussion / Re: Fix a single set

« on: 03 February 2011, 08:08 »

Works fine here...I did a quick test with the romset looping (freely available at mamedev.org) and removed one file from the zip.
A scan shows the removed rom as missing (see attached before.jpg).
After that I used the popupmenu function "delete->all listed incomplete sets".
After the information prompts, I did another new scan and it shows correctly looping as completely missing now (since the incomplete set was removed completely, see attched after.jpg).

2763

clrmame Discussion / Re: Fix a single set

« on: 02 February 2011, 21:54 »

turn off fix missing in the scanner... otherwise you readd the files directly right after deleting them with the menu options.

if you want to rebuild clones only, you have to disable all parents... setinformation-> select sets -> %c=1 iirc ( can check tomorrow).

2764

clrmame Discussion / Re: Fix a single set

« on: 02 February 2011, 21:06 »

as I said, I do see a possible need in a "fix this <selected item>"  option....it's added to my wishlist already

Rebuilder is file based, ie it doesn't know about sets or better about complete sets.
It takes a file from the source and creates all instances of that hash match in the destination. If a file is shared in 1000 sets, you get the file added to such 1000 sets (even if it's the only match).

Generally Scanner/Rebuilder/Merger work on active sets...in Set-Information you can limit the number of active sets in various ways (e.g. regular expressions, via manual enable/disable, via lists, via 'avail sets' button or variable usage etc).

Actually the "delete->all listed incomplete sets" should do what you want...Selected after a scan (!) which lists the incomplete sets it runs through all rompaths and removed the ones which are listed as incomplete. Be sure to have "sets" enabled during the scan.
Please retest this.

2765

clrmame Discussion / Re: Disabling 'Recompress Files' is not byte-exact

« on: 02 February 2011, 20:00 »

1) No recompress means that only compressed data block within a zip is copied without decompress/recompress. The file structure (i.e. localfile header, central dir entry, zip eof etc) are newly created of course. Since such structures have a fixed length, you shouldn't end with a different length. Comments get ripped out and data descriptor tags (rarely used and not needed), too.

Of course a hash of the zip itself changes but noone cares about the hash of a zip....besides maybe torrentzip users ....but noone actually cares about this.

2) no

2766

clrmame Discussion / Re: Fix a single set

« on: 02 February 2011, 19:44 »

Well, I do see your interest in that option but on the other hand where is the need in fixing only a single set/issue?
(Actually I wonder why there is a need for a "ask before fixing" option )

2767

clrmame Discussion / Re: clrmamepro 3.137b

« on: 27 January 2011, 08:46 »

A MESS xml file is not a standard "MAME" one...so you need to load it with a different engine type...
If your engine.cfg doesn't hold one for a mess dat (it does for a direct mess import), you need to add one like:

engine (
   name MESS_DAT
   gamelist mess
   cachefile _messdat
   replace machine game
)

2768

clrmame Discussion / Re: possible slowdown due to utf-8?

« on: 27 January 2011, 08:42 »

...hmm...4MB...not that much...external HD...hmm...esata or usb?

2769

clrmame Discussion / Re: XML dats and UTF support

« on: 22 January 2011, 20:27 »

there is actually nothing with priority in cmpro.. I got very limited time and when I find some something gets added. cant tell you whats next... theres a huge list of all kind of requests and something is picked.... currently it's more the is-mechanical changes in mame or chd rebuild. nothing is forgotten.... but something may come later or even later...

2770

clrmame Discussion / Re: possible slowdown due to utf-8?

« on: 22 January 2011, 10:52 »

description isnt used for rebuilding... an easy test for you would be to simply mod the dat and replace such descriptions with something standard and rebuild again....

2771

clrmame Discussion / Re: possible slowdown due to utf-8?

« on: 20 January 2011, 15:06 »

It's very unlikely that it's based on the filename...I more think your virusscanner hangs on them for whatever reason.
...but of course you can send me the files you're rebuilding....

2772

clrmame Discussion / Re: XML dats and UTF support

« on: 20 January 2011, 08:33 »

ok I had a quick look at the source
...first of all utf-8 support is used when the encoding attribute lists "utf-8" (lowercase)...this will enable ut8 conversion for all texts but special characters should be set as multibyte chars. Encoding via &#x123; will only work correct for byte size not word size values.

guess one day I should rewrite cmpro with full unicode support...

2773

clrmame Discussion / Re: XML dats and UTF support

« on: 19 January 2011, 14:40 »

It's not shown correctly

It simply takes your code page and for YOU it looks correctly. When I load it (DE country page), it shows the superscript 3.

utf8 characters inside filenames inside a zip is a totally different story.....all I say for that: Good Luck

2774

clrmame Discussion / Re: XML dats and UTF support

« on: 19 January 2011, 14:06 »

Well, mainly cmpro is not a dat generator There are other tools which do a better job...however I will have a look at it...

2775

clrmame Discussion / Re: XML dats and UTF support

« on: 19 January 2011, 11:34 »

What's bad news? that you have to manually add the encoding attribute to the generated xml dat?

when not using xml dats you run into issues with non standard characters anyway since they differ from codepage to codepage and you have to toggle the oem/ansi conversion for archives...in other words....don't use non standard chars

With utf-8 encoded dats (and you need to specify the encoding) you should at least be able to have datfile xmls which can be read in the whole world without caring about different characters.

When I'm opening your datfile is see a superscripted 3 character and no 'sword' / 'cross' character as in your posts. So...before we can test something, we first have to define...what do you want to see

2776

clrmame Discussion / Re: XML dats and UTF support

« on: 19 January 2011, 09:56 »

Yes and that's intended. By default there is no utf-8 encoding.
What character are you actually trying to show? are we talking about the superscript 3 character? As in cubic meters...

2777

clrmame Discussion / Re: XML dats and UTF support

« on: 19 January 2011, 07:57 »

Be sure you're using an xml dat with

<?xml version="1.0" encoding="UTF-8"?>

at the beginning...then UTF8 is supported. If you still have issues with that one char, send me the dat.

2778

clrmame Discussion / Re: Problems with scanning and rebuilding

« on: 17 January 2011, 09:34 »

Win 7 64 here as well....and never ever experienced such an issue...yes please..send in the files, screenshots etc....I need as many info as possible...

2779

clrmame Discussion / Re: Problems with scanning and rebuilding

« on: 17 January 2011, 09:02 »

This sounds totally weird...send me your cmpro.ini, the used dat, the belonging .cmp file from cmpro's settings folder.
Some additional information is needed...like, are you using network paths as rompaths/rebuild source/destination, etc etc..

Of course keep in mind the difference of Scan and New Scan.
A new scan scans everything. A "Scan" only scans files which had an issue in a previous New Scan or Scan.

So if you did a rebuild in between with possible wrong folders, then of course a new scan gives a different result than a scan.

2780

clrmame Discussion / Re: How can I fixed missing but fixable roms?

« on: 16 January 2011, 20:03 »

It will move or delete (there are multiple options) all incomplete sets on request (popup menu)....so do it after fixing your set...