Print

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

[Roman]

yes it will be part of the next release....regarding the old code...well...I guess originally for new datfiles it showed the pathname + datfile filename....and the sort was correct....and then I most likely changed the filename part to description but kept the path part before it and forgot to update the sorting, too...or something like this....

[D-an-W]

Hi Roman, just to let you know...I am still getting the "Can't receive version information!" even after replacing the update.dll you link to.

[shawnyadav]

cmnpro stops to respond and crash itself upon todays win 10 system update any solution?

[Roman]

solution: provide any useful information...like what did you do, what files were involved etc etc etc...

[NikNak]

I am using clrmamepro in WINE... when I press the Alt-Key while clrmamepro scans or rebuild it pauses completely. It starts working again when I click on the window.

Is this "normal"?

[Roman]

Hehe..cool ain't it ;-)

With the ALT key in windows programs you turn on the key shortcuts for options....when you press it (e.g. in the scanner window) you will see characters underlined...pressing the key belonging to the character will toggle the option...

so windows simply waits for another keystroke then.....

[NikNak]

I see... I noticed this when I press "Alt+Tab" to switch to another window. It pauses then for me. Maybe WINE handles this wrong...

[Roman]

it's nothing I can change....

[GameGirl3]

The latest build is crashing during rebuilding the roms. I'm on Windows 10 x64. Also, the main clrmamepro site's 403'd. Both needs to be fixed.

[Roman]

as you can read here in the forum, the downtime of the main page is intended....

and there is no crashing.....you are the first who reported this.....so you may want to give more details on your setup, the used files etc.....maybe you got somewhere a corrupt archive or faulty hardware etc etc tc....without detail, e.g. a rebuilder log, Incannot help you.

[D-an-W]

Hi Roman,

Any way to fix this error I get all the time (Currently using latest Nightly but happens with earlier versions too)...

[Roman]

No, actually I cannot fix it since it's not related to cmpro but to the https network connection......the server's response says rejected...for whatever reason.....

You can try to press the button multiple times but for some users it seems not to work and the network somehow blocks them....
Actually a lot of users tested it (myself from 3 different networks) and don't get the problem with 4.034 onwards at all....(Windows 10 pro, April 2018 release, 64bit)...

But don't worry...if there's a new version out, you will find it here (or at least the information for it) in the forum

[D-an-W]

Ok thanks, is there a way to stop it popping up all the time?

[Roman]

what do you mean with all the time?? It only happens when you check for an update....which happens when you either clicked "Check Now" in the about update -> dialog...or you've set the selection to check it daily/weekly/monthly......so go there and switch to "never"

[D-an-W]

If I have the update check to weekly, every time I open "Settings" (Or any other window) I get the above prompt.

[Roman]

most likely because it does not save the last time since the connection failed....so simply put it on "NONE"....there is no new version planned anytime soon....

[GameGirl3]

Well Roman, clrmamepro is working, but only in Safe mode on Windows 10. I can't give you an error report if the application keeps crashing in Normal mode when rebuilding ROMs or scanning for ROMs. Hopefully, the next build can correct the problem.

[Roman]

The rebuilder is the module which is used so often by so many people in their daily work and noone reported a problem yet.....so I guess it is really your problem...so we need to find out what is wrong. As mentioned, it can be anything.....a bad archive file which is processed by 7z/rar/zip dlls.....even cpu overheating or bad ram can be the issue....or bas usb drivers when working with external drives......also virusscanners are known to interfear...and if you are saying it only works in Win10 safe mode it only hardens the idea that something is wrong with your system....

so...the only thing you can do at the moment is, use the latest nighly build, try to minimize the files you are rebuilding...turn on rebuilder logging to see which files are processed or at which point it fails. try to have a minimum set of files where you can repeat thej problem, archive them together with your cmpor installation and let me look at them.