Topic: cmnpro 4.034 released (Read 13465 times)

Roman · « **on:** 20 February 2018, 20:03 »

4.034
fixed: due to a cache flag error, in non-merged mode, cmpro took merge attribute information for names into account which is wrong
fixed: setinfo, falsely hide empty parent set and its clones in tree when parent is empty but clones got content
fixed: scanner, falsely list empty parents set in full merged mode as wrong named when parent is empty
fixed: scanner, falsely list empty parent set in full merged, multi-software list mode as missing when set exists in various software lists
fixed: miss list generator falsely lists sampleonly sets when they only reference parent samples
fixed: scanner, falsely show wrong case set messages when missing option is turned off
misc: allow romclones to be sampleparents
misc: switched to visual studio 2017 (also for updater)
misc: updated zipArchive lib to 4.6.5, 7z sdk to 18.01

if you have problems with the update process in 4.033, you can download an updated update.dll here: https://mamedev.emulab.it/clrmamepro/binaries/update.rar

coccola · « **Reply #1 on:** 20 February 2018, 21:56 »

I tried using the update.dll you linked but it didn't work.

So, I updated downloading the zip and extracting on top of the installed files.

Now, after it's updated and working, if I check if there are new versions available within clrmamepro itself, I get "Can't receive version information!".

Using 64-bit on Windows 7.

Roman · « **Reply #2 on:** 21 February 2018, 08:47 »

Hmm...no issues here with the new dll from 3 different machines in 3 different networks....The old dll does cause issues though.

coccola · « **Reply #3 on:** 22 February 2018, 02:33 »

How can I help you check this problem? Perhaps sending you somehow all files of clrmamepro's folder?

zitz · « **Reply #4 on:** 22 February 2018, 03:23 »

No xp support ?

https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2017-compatibility-vs

Windows XP Yes
Managed development requires using Visual Studio .NET multi-targeting. Remote debugging and profiling tools are not available.

Roman · « **Reply #5 on:** 22 February 2018, 08:07 »

coccola: you actually can't help. The server seems to send a HTTP error code 400 from time to time (bad request) which seems to be caused server sided (since the cmpro request does not change). Since it's not my server I cannot do anything (however I informed the server owners, but no reply). Lately I was able to 'fix' this behaviour by changing some http headers here and there and as mentioned, it works flawlessly on any machine/network I've tested so far (while the old code still fails). So it is somehow network/server related...my DNS cache...maybe just a random thing on the server....

zitz: No xp support ? NO, no XP support. XP is dead. Microsoft's end of support was 2014. Upgrade!
To be honest, I usually compile a limited version which still runs on XP from time to time. So...you might see one download link sooner or later.

Update: XP Users please test this.... https://mamedev.emulab.it/clrmamepro/binaries/cmproXP..rar

zitz · « **Reply #6 on:** 23 February 2018, 01:52 »

Failed to load 7Zip Library: 7z_32.dll

Roman · « **Reply #7 on:** 23 February 2018, 05:33 »

you've extracted the file into your installed cmpro folder( and replaced the existing exe) haven't you?

coccola · « **Reply #8 on:** 23 February 2018, 07:55 »

@Roman

OK, thank you for your reply. It looks like I'll have to update manually from now on.

zitz · « **Reply #9 on:** 23 February 2018, 09:32 »

Quote from: Roman on 23 February 2018, 05:33

you've extracted the file into your installed cmpro folder( and replaced the existing exe) haven't you?

Were you referring to me ? no, it was run standalone in its own folder

Roman · « **Reply #10 on:** 23 February 2018, 13:38 »

zitz: yes...of course the rar archive only holds the exe which (should) run under XP. you need a 4.034 installation first, then replace the exe.

I just saw that the executable in the rar file is not named cmpro.exe but ClrMamePro.exe, so after unpacking it, you need to run that one (in your cmpro folder with all the other files from the normal installation)

pacman56 · « **Reply #11 on:** 28 February 2018, 20:52 »

Good afternoon,

I just upgraded to 4.034 this morning and noticed that after I dragged all the xml files from the MAME 0.195 hash folder then attempted to sort the resulting list by clicking on the Profile column, the software lists names were not ordered alphabetically as in previous versions. The Profile column displays the description attribute of the softwarelist element but the new sorting behavior appears to be using the name attribute or filename as its sort field. From what I can see, version 4.033 sorting was based on the description attribute which is what's visible to the user. Is this the intended behavior?

Thank you for your help

Roman · « **Reply #12 on:** 01 March 2018, 06:44 »

erm...nothing has changed regarding profiler sort or profile naming of software lists for ages....
I've just dropped all of MAME's hash files into the profiler and created profiles for them and they appear as usual, listed by description...and sorting works fine...see attached picture..

so.....all I can say....It works fine here....

pacman56 · « **Reply #13 on:** 01 March 2018, 17:39 »

Good afternoon Roman,

Thank you for your reply. I think I know what's happening here.
Your screenshot shows loaded and scanned profiles which is a step passed what I was observing or reporting. Sorry for the confusion!
Right after you drag and drop the xml files from the hash folder then click on the "[NEW DATAFILES]" folder in cmpro, the list of profiles will initially be sorted on the filename or "name" attribute of the "softwarelist" elements of those hash file.
This is where I was trying to sort the profile list so that I could remove the "VTech V.Reader - Storio cartridges" profile from before performing a scan in batch mode.
I just repeated this steps this morning to confirm that the problem was still present.
Once the profiles have been scanned, sorting on the Profile column will work as expected.

I'm attaching a screenshot which should depict the problem.

Again, thank you so much for this awesome tool!

Roman · « **Reply #14 on:** 01 March 2018, 19:28 »

Yes, when they are in "new datfiles", cmpro additionally shows the path...but still the name is the description (e.g. 3do_m2.xml versus 3DO M2 CD-ROMs).

pacman56 · « **Reply #15 on:** 01 March 2018, 19:52 »

I understand and agree with your response but in my screenshot "path\Sega 32x cartriges" comes before "path\3DO M2 CD-ROMs".
Shouldn't it be the other way around?
You'll also see other profile names in that screenshot that are out of order.

Roman · « **Reply #16 on:** 01 March 2018, 20:45 »

ehehe...good point ;-) Yes you're right and I actually found the belonging source code for it. It uses the description BUT NOT if it's a new profile...there it uses the filename as sort criteria... ;-)

I have no idea why though...pretty damn old code part.....but by looking at the code I can say...back then....it was made intentionally

pacman56 · « **Reply #17 on:** 01 March 2018, 20:56 »

yes...I was definitely mistaken when I said earlier that this was working in previous version.

In any case, I'm happy to see we're both on the same page.

Roman · « **Reply #18 on:** 02 March 2018, 18:22 »

you might want to give this a try....
https://mamedev.emulab.it/clrmamepro/binaries/cmpro20180302.rar

pacman56 · « **Reply #19 on:** 03 March 2018, 20:08 »

yesss...Looking perfect!

I also re-scanned all software lists in batch mode to make sure everything was still green.

Did you find out or remember why the old code was intentionally using the filename as sort criteria? Just curious.
I'm guessing this new code will be merged into the main branch for the next official release.

Thanks a million Roman. This is very appreciated!

News:

Author Topic: cmnpro 4.034 released (Read 13465 times)