EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: Roman on 03 September 2017, 19:03
-
What a special day today....20 years ago...yes twenty years...the very first version of clrmame was released. Back then it was a win32 commandline tool. 1999 cmwin, a first windows ui version was released and finally in 2000 clrmamepro came out. In 1997 MAME had no zip support, no merging and actually not even crc32 was used for hashing...good old times ;-) And today...look at that beauty of emulator. What a success, what a huge amount of emulated sets. Times are changing, I've tried to update cmpro as good as possible to keep track of the changes made in MAME. I'd like to thank all the users who supported me over the years...some of them from the beginning till today. Without you, I would have stopped cmpro a long time ago. So....keep me busy. Thanks again. And yeah...here's the latest version 4.033.
Since the homepage is now https, you need to download this update manually. The updater will work again once you have 4.033 installed
4.033
fixed: xml parser to handle > character within an xml attribute correctly
fixed: wrong "missing but fixable" message (mainly chd) when set check is disabled which covers the actual message
fixed: dir2dat archives with folders produce wrong output
fixed: stats count of missing roms for clone sets which only consist of parent roms (and chds)
fixed: stats count of missing chds in case set check is disabled
fixed: fixmissing skips the set with the missing file itself for checking for a possible match and might miss a possible fix
(pretty rare that a set holds identical files, but e.g. MAME's 188 "pippin" does)
misc: use MoveFile instead of CopyFile also for disabled remove-rebuilt-source when possible
misc: drag'n drop operations now work when you use "run as admininistrator" to run cmpro in an UAC protected folder
misc: changed softwarelist import to always import all and filter specific afterwards. Solves problem where MAME does not print out data for some.
misc: remove possible empty setfolder when a chdfile is moved
misc: cmpro.ini setting Adv_AvoidPCSleep=on can be used to avoid PC switching to hibernate/sleep mode during scan/merge/rebuild/dir2dat operations (default = on, i.e. it won't switch)
misc: updated to rar 5.50
misc: make updater https aware
-
Thank you Roman for 20 years of updates and support.
CMP merged followed by T7Z (https://imgur.com/IP5dfNK) is the best combination ever
39.5 GB 11673 Archives and everything neatly organized.
Thanks for everything :)
-
Does not work on xp
The procedure entry point ChangeWindowMessageFilter could not be located in the dynamic link library USER32.dll
-
what does not work on xp?
the 32bit version of cmpro should still work on it....(latest patch level which was SP3 or something)
besides of this...windows xp is dead...update
maybe you're talking about the update.dll....you might want to exchange it with the (unrar'ed) attached one
-
cmpro.exe 32bit does not work on xp sp3+ and that is the error it produces
i tried it on another xp machine and also in a virtual machine and still does not work
-
It worked fine and nothing has changed regarding the compile options, the only possible thing is the update.dll which you might want to replace (see previous post). I will double check it later on a virtual machine.
-
Replacing the update.dll did not fix it. v4.032 works fine
-
I have found some information which might possibly be the culprit
https://stackoverflow.com/questions/827525/building-a-screensaver-for-xp-using-vc-2008
"Microsoft botched the scrnsave.lib library included in VS 2008 to call a Vista-specific function, which fails on XP because the function does not exist."
Googling the error found the same or similar information
This one of from the JKDefrag changelog
Changes:
- Reverted back to an old Microsoft Screensaver library. The 2008 compiler has a library that is incompatible with Windows XP ("The procedure entry point ChangeWindowMessageFilter could not be located in the dynamic link library USER32.dll").
-
All I know currently (until I found my XP virtual machines) is that cmpro needed to be compiled with some special VS2015 flags to be runnable on XP. This was done ages ago and it did run and I did not change the compile options, especially not from last to the current version.
What did change was the update.dll (which needed the same compile options to be set...which I forgot, that's why I posted the new one)....
So...currently I don't know any reason why it should not run....but I will check it later today.
-
Ah....I know why ;-)
misc: drag'n drop operations now work when you use "run as admininistrator" to run cmpro in an UAC protected folder
this isn't compatible with WindowsXP anymore, no matter how it is compiled.
I will try to update the code...
-
Fingers crossed
-
ok...first try...a simple if windows version >= 6 around the function calls in question:
https://mamedev.emulab.it/clrmamepro/binaries/cmproXP.rar
-
ok...first try...a simple if windows version >= 6 around the function calls in question:
https://mamedev.emulab.it/clrmamepro/binaries/cmproXP.rar
Same error
-
well then all functions are checked for availability on startup....tough luck...then you need an exra compile where they are completely removed.....I may build one for you once....really....there is no real need too use xp these days :-)
-
My motherboard may be old but it still works without any problem. It doesn't have drivers for 7/8/10. I have no idea when my next system upgrade will be
Is it possible to have an xp legacy release version without the feature which is incompatible ?
-
That's what I said...I will build it once for you........and currently I don't know if I'll do it for possible future versions, too...time will tell
-
Second try...completely removed the functions...
https://mamedev.emulab.it/clrmamepro/binaries/cmproXPNew.rar
-
Second try works :)
Is that going to be the official release of it ?
-
yes...it's official ;-) keep it....nothing else is different to the other packages......currently you seem to be the only XP user out there ;-)
I don't know if I will move the code into a dll which only gets loaded and called on a > Vista/7/10 system...time will tell....
-
Nice tool used several times in the past. Decided to revisit my Mame install/collection and see if I can tidy it up. Scan shows many games with odd missing file. However your download url's no longer work they lead to missing .404 pages. Have you any plans to update/replace these with working ones ?
I use Emuparadise for mine but it would be nice if after scanning it auto downloads the missing.
-
They do work fine here...
Double check if it shows https instead of http for you when hovering over the links, otherwise you got bad cached data.
If the scanner says you're missing files, you're missing files ;-) A few more details would be helpful
-
well, ROMs are subject to copyright; so a tool to download them automatically would be a MASSIVE breach of copyright's law and an invitation for the big powers to sue Roman.
I think it's best if you find the ROMs you are missing by yourself, they are all widely available from multiple places.
-
well...actually there is an option in the scanner's context menu to open specific sets at specific urls....you only need to configure it correctly ;-)
-
you seem to be the only XP user out there
There's two of us :)
I've kept my old XP desktop as a download box, and it's where my MAME files are kept, maybe it's time for me to finally upgrade?
-
by the way...... xp users need to download
https://mamedev.emulab.it/clrmamepro/binaries/cmproXPNew.rar
if they want to run cmpro...