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.

3041

clrmame Discussion / Re: Generate HTML Report Current Folder including Sub-folders possible?

« on: 13 February 2010, 09:09 »

maybe a better (and less time taking) idea would be to export the profile data as xml so you can code the html pages yourself

3042

clrmame Discussion / Re: Generate HTML Report Current Folder including Sub-folders possible?

« on: 13 February 2010, 08:57 »

well...theoretically...of course....practically...I put it on my list...don't expect to see it anytime soon since currently I got nearly zero time for bigger changes.

3043

clrmame Discussion / Re: Drag & Drop?

« on: 02 February 2010, 08:30 »

Welcome to the beautiful world of Vista and Windows7.

You can't drag'n drop files from a source to a destination where the user access rights differ.

So...either your source folder got different user rights than the cmpro application or viceversa.

You can fiddle around with running the application as administrator but usually it's enough to store cmpro in a not-UAC protected folder.

My setup: Windows 7 64bit ultimate, logged in as an administrator user

cmpro installed in d:\cmpro\cmpro.exe (so I avoid anything like c:\programs...) and the things I want to scan/rebuild are somewhere in h:\mame\roms for example.

3044

clrmame Discussion / Re: creating mess dats

« on: 29 January 2010, 18:03 »

Profiler->Create->Emulator = MESS

3045

clrmame Discussion / Re: how to add CHD using clrmamepro?

« on: 27 January 2010, 21:00 »

Regarding the stats, well, cmpro counts nodumps (no matter if chd or full set or rom) as 'available' depending on the nodump-mode (required/optional/etc). So even if you scan an empty rompath, you automatically have some roms...the nodumps

3046

clrmame Discussion / Re: how to add CHD using clrmamepro?

« on: 27 January 2010, 14:42 »

ignore the stats (they are calculated differently, without caring for merge modes etc...)

look at the scan results tree output..that's the only important thing to care about. Everything listed there is an issue and it gives you detailed information about what is wrong.

3047

clrmame Discussion / Re: how to add CHD using clrmamepro?

« on: 26 January 2010, 21:09 »

the semi-official method is the one which follows the standard storing method for MAME:
rompath\setname\file 1 ... file n

this means, for example you got your roms in d:\temp\mame\roms and go the cap-jjk-160.chd  file, you put it in

d:\temp\mame\roms\jojo\cap-jjk-160.chd

since jojo is the belonging setname.

So the semi-official method is to use rompath subfolders named after the set...similar to decompressed sets.

Since CHD files are containers (Compressed Hunks of Data), putting them in a zip is obsolete and would cause endless and very memory intensive decompress operations.

Since MAME .130 you can allow store chds in a rompath root...which is the 'weird mode' since you don't reallly see which set the chdfile belongs to (usually they are not so easily named like area51.chd for area51).

That chd-on-rompath-root level is supported by cmpro but you need to enabled it (scanner->advanced).

3048

clrmame Discussion / Re: how to add CHD using clrmamepro?

« on: 26 January 2010, 08:19 »

You can't.
Rebuilder is (currently) roms only.
However the scanner can not only warn you about all kind of chd issues, it can also move wrong placed and wrong named chds to their correct place. So you can simply move a chd with any name to a rompath root (assuming you don't use that weird storing mode) and chd + name + unneeded check/fix will tell you they are wrong placed and moves them to their correct setsubfolder.

3049

clrmame Discussion / clrmamepro 3.132b released

« on: 18 January 2010, 21:55 »

3.132b

added: support for utf-8 encoding in xml datfiles
misc:  agent name for http/ftp is now set to "cmpro"
fixed: www profiler can't load from php generated urls with ?
fixed: archive comments warning is still broken for rar files
fixed: wrong illegal download folder message on clean install
fixed: explore menu option opens an explorer path for not game specific warnings
fixed: www open popmenu option shows romname in url only in the 2nd try onwards

3050

News & Communication / clrmamepro 3.132b released

« on: 18 January 2010, 21:55 »

3.132b

added: support for utf-8 encoding in xml datfiles
misc:  agent name for http/ftp is now set to "cmpro"
fixed: www profiler can't load from php generated urls with ?
fixed: archive comments warning is still broken for rar files
fixed: wrong illegal download folder message on clean install
fixed: explore menu option opens an explorer path for not game specific warnings
fixed: www open popmenu option shows romname in url only in the 2nd try onwards

3051

clrmame Discussion / Re: CMP Sub-Directory Handling

« on: 18 January 2010, 13:13 »

Good to hear it's 'fixed' for you.

As mentioned, you can have folder entries besides file entries in zipfiles like:

"subfolder\"
"subfolder\rom1.bin"

Since filenames are always fully qualified, you don't actually need the dummy folder entries and they become unneeded....the fully qualified filename is more than enough to create subfolders.

3052

clrmame Discussion / Re: CMP Sub-Directory Handling

« on: 17 January 2010, 20:48 »

Works fine here....

maybe you're talking about useless zip folder structures which can get optionally detected and removed (Settings->compressor->General->Mark useless folder structs as unneeded)

Zip can store an extra folder entry in the zipfile...which is not needed for subfolders and can be removed.

So maybe you should send me a file in question and some screenshots.

3053

clrmame Discussion / Re: CMP Sub-Directory Handling

« on: 16 January 2010, 19:29 »

Since you say that no folder is empty it shouldn't be a problem to scan them correctly.

Send me a datfile.

It should contain roms like this (old syntax, xml is similar, romnames hold fullfolder)

game ( name sub description subsub
rom ( name "bla\blablabl\blalbalbla\1.bin" size 1024 crc 12345678 )
)

3054

clrmame Discussion / Re: incompatable with some filenames

« on: 15 January 2010, 08:39 »

Well....they get skipped since they cannot be opened with the normal open functions of the win32 api....normally you don't even see a message prompt.
So I guess a prompt here and there (no idea which call produced yours) is not that hard...

Guess it's some unicode thingie....and it already depends which zip program you're using to unpack the file. With one I get a filename without the pipe (and so working on the file works fine), with a different one I get an not printable character in the filename which gets converted to a pipe as soon as you query the name.

3055

clrmame Discussion / Re: incompatable with some filenames

« on: 14 January 2010, 20:02 »

Ehe...looks like various windows programs have issues to open it...funnily enough notepad opens it....hmmm...interesting case.


edit: ok...simply putting quotes around it or using a short name conversion doesn't help to open the file. Unfortunalety "DragQueryFile" which is used e.g. when drag'n dropping a file returns the pipe symbol...wonder what else can be used to open it.

Anyway....guess it's a pretty weird filename and I wonder how it was created anyway.....maybe some unicode weirdness....nothing really to care about, isn't it

3056

clrmame Discussion / Re: incompatable with some filenames

« on: 14 January 2010, 19:44 »

ah ok....opening the file fails.....well...I will check what the System calls return in that case.

3057

clrmame Discussion / Re: incompatable with some filenames

« on: 14 January 2010, 19:42 »

wait a second..you unpacked it....I used the full archive....lemme test it...

3058

clrmame Discussion / Re: incompatable with some filenames

« on: 14 January 2010, 19:25 »

Well the pipe symbol "¦" is definetly an illegal filename character since it's used for well..piping. But I don't see that character here at all. Which codepage is your Windows using?

Here it's shown as: "iLogicAll_Espa+Ôûîol.tzx" (now I hope this messageboard does no character translation,too ...guess I have to make a screenshot then.

3059

clrmame Discussion / Re: incompatable with some filenames

« on: 14 January 2010, 18:45 »

Works fine here.
I've create a dummy dat

game ( name "test" description "blubb" rom ( name "1" size 74133 crc 1837600b ) )

and it rebuilds fine. Maybe some oem2ansi conversion issue with the dat you've used....so...please send it.

3060

clrmame Discussion / Re: Help!

« on: 12 January 2010, 19:12 »

> Both were set to the opposite, so have changed them back. This was an update over an old CMPro - must have been changed back in the mists of time.

Not really. They were never exchanged or pointed by default to a different value. Anyway, you found it, you changed it, perfect.

> Just one last item, the Fixed-Wrong-Name shows CHDs as 0/5, instead of 0/0 like ROMs and sets. Is this fixable?

If chd + name + fixname is enabled they should have been fixed and if nothing is in the scan tree, perfect, you're fine.
Which ones are still listed as wrong named after a new scan?
Maybe the 'new name' already exists as a file and that's why the rename operation fails. In this case you can manually remove the 2nd instance.

> A "Just-fix-it!" button, if you will!

Well, 1st of all, clrmamepro grew to a monster over the last 13 years (it's 'PRO' due to the input from several in-deep-collector groups, devs etc who got some weird requests which the common user doesn't have to care about.
For the common user it's actually set to some good defaults already and he/she only has to:
1) load a dat in the profiler
2) setup a rompath in settings
3) go to the scanner and hit scan.....This lists everything which is wrong...and if you enable the fix options, it will fix them....

Maybe the rewrite in 2026 will bring you a one-touch only functionality.

>Should I be parsing merge tags on the ROMs, too?

If you like...you will gain a little bit of diskspace...but in days of multi-terabyte hds...who cares