1
clrmame Discussion / cmpro no longer viable for me
« on: 09 June 2019, 03:27 »
Used 4.034 up until MAME 2.09.
Then tonight decided to update to 4.035, then saw there was a "nightly build" version available, so I downloaded and installed that (05152019).
Then updated my MAME executable to 2.10 using the "arcade" flavor (mamearcadeui64).
Loaded up the profile with the 100% 2.09 scan, and proceeded to start a scan with 2.10.
At least 15 MINUTES later, and it is STILL "Receiving data". It NEVER took this long before! I don't know exactly how long it did take as I walked away from my PC for a time.
Then, while in the middle of the scan, my paid Malwarebytes dutifully reported that it blocked cmpro64.exe as "ransomware". What?? It then decided to "block" the program from running, or even be able to be deleted.
So, I created an exception, made a copy of the cmpro folder, renamed the old folder to "cmpro old", and renamed the new folder back to "cmpro", and re-started a scan.
Again, it was 15 minutes before it started any activity.
But, my main concern was that Malwarebytes saw it as ransomware. I've been using this program for years without an issue before today, so I thought I'd report it here in case anyone else has run into the same issue.
Then tonight decided to update to 4.035, then saw there was a "nightly build" version available, so I downloaded and installed that (05152019).
Then updated my MAME executable to 2.10 using the "arcade" flavor (mamearcadeui64).
Loaded up the profile with the 100% 2.09 scan, and proceeded to start a scan with 2.10.
At least 15 MINUTES later, and it is STILL "Receiving data". It NEVER took this long before! I don't know exactly how long it did take as I walked away from my PC for a time.
Then, while in the middle of the scan, my paid Malwarebytes dutifully reported that it blocked cmpro64.exe as "ransomware". What?? It then decided to "block" the program from running, or even be able to be deleted.
So, I created an exception, made a copy of the cmpro folder, renamed the old folder to "cmpro old", and renamed the new folder back to "cmpro", and re-started a scan.
Again, it was 15 minutes before it started any activity.
But, my main concern was that Malwarebytes saw it as ransomware. I've been using this program for years without an issue before today, so I thought I'd report it here in case anyone else has run into the same issue.