CriticalCid
-
Posts
1,461 -
Joined
-
Last visited
-
Days Won
19
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by CriticalCid
-
-
I know that the wall-of-text and all the screenshots could be a little intimidating but when you done it 2-3 times the whole process won't take you any longer than 10 minutes. @SentaiBrad it seems I couldn' edit my placeholder post and it just created a new post. Maybe you can delete the placeholder then. Also if you want further information's for your video tutorial I would be very happy to help.
-
Step 2: Setting up the profile and paths 5. Open the “cmpro64.exe” and you will be greeted with a messagebox. Click okay and you will automatically be in the profiler menu. 6. Here you have different options to include a database for Clrmamepro to work with. The easiest and in my opinion the best way is to use the database which comes directly with MAME itself. So click on the create button and a new window will open. As filename search for the .exe file of your MAME version. As description I recommend you name it after the MAME branch and version you are using. In my case I name it MAMEUIFX64 0.171. Keep MAME as the emulator. Click on “Create Profile” and a new window opens in which can organize your profiles. For now just click on OK.
7. Now your newly created profile should show up in the profilelist. Double-click on your new profile.
8. Now Clrmamepro wants to extract the database from your MAME .exe file. Click on OK. After a short scan it may ask you if you want to import SoftwareLists. If you don’t use MESS within MAME you won’t need that.
I don’t use MESS or want to update a MESS romset so I say “NO” to the SoftwareLists.
Now some error messages are popping up. That’s totally normal. Just confirm every message with “OK TO ALL”.
9. Now you’re in the main menu of CLRmamepro. At first we have to set up our rom paths. Click on "Settings" for that.
10. In the left upper corner you can select for what kind of files you want to set up the paths. We want to add our ROM-Paths so we select “ROM-Paths”.
You can either click on “Add” to add your paths or just drag-and-drop them into the window. So add the path to your current romset you want to update. (NOT the paths which are containing your updates!)
11. Every file CLRmamepro finds within the ROM- and Sample-Paths which don’t fit to the current MAME version will automatically be moved into the Backup folder. The standard setting for this is a folder called “backup” within CLRmamepro folder.
If your CLRmamepro installation is on the same drive as your MAME romset than you can leave it as it is. If CLRmamepro and your ROMset are on different drives I highly recommend changing the backup folder path into an empty folder which sits on the same drive as your ROMs. It will highly increase the speed. Leave the rest as it is.
12. Change the path type to “Add-Paths”. Here you need to add every path you want the program to look for updates or new ROMs you want to add.
IMPORTANT: You have to add the backup path too!
In my case I want to update from 0.170 to 0.171 and add the extra games for MAMEUIFX.
13. Optional: If you want to scan/fix/update your Sample files too, choose “Sample-Paths” and add the folder for it as well.
A small explanation what sample files are (thanks Google): Samples go in a folder called 'samples' in your main Mame directory. They are used in conjunction with games that either doesn't have emulated sound or used external sound samples via another device (like a Tape). Mame will automatically use the correct ones with the game if they are present in the samples folder.
14. Close the window. All settings are being saved automatically.
Step 3: The Scanner
15. After we have set up all paths we want that CLRmamepro scans our current romset and fix/remove every outdated ROM, CHD and Sample file. For that we click on "Scanner".
16. The “You want to scan” section is self-explanatory. In the “You prefer” section you have to choose how you want your romset to be constructed. For the best compatibility with LaunchBox I highly recommend a split or non-merged set!
Here are the differences between the different set options:
Non-Merged: Each set has ALL files it needs. This is normally a waste of disk space because even clone sets have the parentsets included.
Split: Parent sets only have the parent files and a clone sets consists of the clone files only.
Merged Sets: Full merged sets are parentsets only, which also include all clone files. So you will have every version of the game in just on file.
I don’t want to waste disc space so I go with a split set in this tutorial.
17. “Prompts” you can leave it as it is.
18. In the check/fix section we want to check and fix everything. Click on “All” and every checkbox should be checked now.
19. Ignore the “Advanced” and “LogFile” button and click on “Systems”. A new window opens up. Here click first on “All” and then on “Auto-Assign”. It will automatically set the paths for all systems into the ROM-Path you chose earlier. At the end of this tutorial I will say something more to this but for now just close the window.
20. Click on the “Hash & CHD” button. In the new window check both options at the bottom “Run Analysis” and “Fix file (If Possible)". These options will decrease the scanning speed but if you have corrupted ROM files it will try to repair them automatically. Leave the rest at is and close the window.
21. Ignore “Statistics”. Now we have configured the scanner and it should hopefully look like this:
22. Click on “New Scan” and wait. The scanner will tell you if it finds something which needs to be fixed. Confirm every message with “Yes To All”.
In the “Scan Results” window you can see exactly what is currently wrong with your romset. You don’t have to worry about that.
23. When the scan is finished a window pops up that’s giving you information about the current status of your ROMset. Click on “OK” and close the scanner.
Step 4: The Rebuilder
24. Our ROMset is cleaned and fixed now. At next we have to update it to the new version. For that click in “Rebuilder”.
25. Check the box “Use Add-Paths” and CLRmamepro will use all the paths for the updates that we already set up.
26. At "destination" you have to check the box “Use System Default Paths”.
27. The Merge option should be the same as you chose on the scanner.
28. At “Compress Files” you have to choose which file format you want for your ROMS. I prefer .7z because it saves more space on the hard drive as .zip.
IMPORTANT #1: If you change the file format to a different format as your ROMs are already zipped it will take very long to rebuild your ROMset, because all your ROMs will be extracted and compressed again.
So if you have all your ROMs in .zip files and you want it to change to .7z prepare for a long waiting time until everything is done.
IMPORTANT #2: If you want to use .7z you will have to need 7-Zip installed on your PC.
If you want to use .rar you will have to need WinRAR installed on your PC.
29. Check “Recompress Files”, “Show Statistics” and “Remove Matched Sourcefiles”.
30. Ignore “Systems” and “Advanced” and click on “Rebuild”.
31. Optional: If you get an error relating to a .7z file it helps to copy the “7z.exe” and “7z.dll” from your 7-Zip folder into your “CLRmamepro” folder.
32. Now the rebuilding starts. Depending on your ROMset and your options it could take quite a while. When the rebuilding is finished you get a status report.
33. Click on ok and close the rebuilder. Now we are almost finished.
34. If you want to update your CHDs you can now move the CHD folders from your Update folders into your ROM folder. If Windows asks you if you want to integrate the files in the already existing folders confirm that with "Yes".
35. Do the same with your Sample files if you want to add or update them. Just keep in my mind to move them in your samples and not into your ROM folder.
36. Go back to the “Scanner” and click on “New Scan”.
37. If everything worked the new scan result screen should look like this:
I only miss a sample file for one game which I couldn’t track down yet. Everything else is complete and now up to date.
38. Now you can delete all your update folders.
Bonus Step: Split your ROMset in different systems
If you don’t want every ROM in one big single folder and instead separate folders for separate arcade systems you can split them with CLRmamepro too.
For example I like to have my NeoGeo ROMs separated because I want them as a separate platform within LaunchBox.
Go back to the “Scanner” and click on “Systems”. Choose the System you want to be separated from your other ROMs and make a double-click on the path.
Choose or create an empty folder in which you want to move the ROMs for that system and click “OK”.
Now click on “Move Sets” and the program will automatically move all ROMs into the folders you chose.
NOTE: If you want to scan your ROMs again a message will show up saying that the new paths for your systems aren’t ROM-paths. Click on yes to add them automatically to your ROM-Paths.
The end.
I hope this tutorial was understandable and useful for some of you. If you have questions feel free to ask.
-
Tutorial: How to update your MAME ROMset to a newer version with CLRmamepro Note: This tutorial assumes that you already have a complete ROMset from a previous MAME version. If you don’t have a complete ROMset than I would suggest to just grab a complete set for the current MAME version and return to this tutorial if you want to update it in the future. Why update the ROMs?: MAME is very sensitive about its ROM versions. You can get an older version of a ROMset to work with a newer MAME version but you should be aware that you can run in many errors and missing files. In the best case your ROMset version matches exactly the MAME version you are using. The MAME developers are updating MAME every last Wednesday in the month, so if you download a complete ROMset today it won’t work perfectly fine with the newest MAME version by the end of next month. If all the games you want to play are all there and working perfectly fine you probably won’t care about new updates, but if you want to get all the new emulation improvements and new added ROMs you should keep track of them. Now is a complete ROMset with all CHDs roughly 400GB in size, so you probably don’t want to download that amount of data every month. It’s faster to just download all new added ROMs, CHDs and Samples and just to update the ROMset you already have. And with the program CLRmamero you can do this. If you want more information why MAME is so sensitive about the ROM versions and mandatory file names I highly recommend this Reddit thread: https://www.reddit.com/r/MAME/comments/3gh78n/probably_a_silly_question_but_why_are_ROM_packs/ Step 1: Groundwork 1. First of all you should know what ROMset version you have. I don’t know if there’s a comfortable way to find out what version you have. Normally your ROMset version should be the same as the MAME version you are currently using but I can’t guarantee that this is the case for you. So if you have absolutely no idea what ROM version you have I would suggest what I wrote at the beginning of this tutorial. Download a complete set of the current version and write down what version that is, so you can update that set in the future. 2. Download all ROM update packs beginning from the version you have until to the current version. With all I mean all. For example if your ROMset is on version 0.168 and you want to update to version 0.171 you will need the update packs: 0.168 to 0.169, 0.169 to .170 and 0.170 to 0.171! 3. Download CLRmamepro at http://mamedev.emulab.it/clrmamepro/ and install/extract it. You will also need to install/update to a version of MAME which matches the version you want to update your ROMset to. In this tutorial I show you how I update my 0.170 ROMset to version 0.171. I use for that MAMEUIFX64 0.171. 4. Optional: If you use a branch of MAME which supports some extra games (like MAMEUIFX) you would probably want these games too. Normally they are not included in an official complete MAME ROMset so you have to download them separately. Use Google to find out if your MAME version supports additional games and then download them. If you use MAMEUIFX like myself you can legally get the additional games in their forum: http://mame32fx.altervista.org/forum/viewtopic.php?t=4 Just download all ROMs and Samples and keep in mind to create separate folders for ROMs and Samples.
-
I wouldn’t just replace the CHDs. MAME sometimes keeps older versions of the games and just renames them. They would be missing if you just replace them. Also I would strictly disadvice to manually repacking the .zip files. You can break more than it would help you. If you want I can document my process when I update my own romset later this day and write I little tutorial. As I said it’s not very intuitive but when you done it 2-3 times it’s very easy.
-
There's also a third program. InputMapper https://inputmapper.com/ I use InputMapper myself and everything works completely fine.
-
I just looked at the PS1 xml and it appears that it doesn’t include normal CRC values at all (what would be impossible anyway since most CD games are a .cue + .bin file(s) combination) Instead it looks like this: SCUS94601, 3D_LEMMINGS Am I right that the parser would crash as well because the values don't have 8 digits? If that’s the case I would find it very great if you could include the option to just skip the first line. It wouldn’t break the parser because if a game hasn’t a CRC value listed then the line is still there, but only blank.
-
I thought that the CRC could be the problem because it caused already trouble in a synopsis file. But I honestly don’t know where the problem exactly is because all I get is this unclear error message:
I tried it with a SNES, NES, N64, PS1 and Genesis synopsis file. The only file that was working was Genesis. At all the others I get the same error. I also uploaded the SNES one so you can test it yourself.
-
Or skip the CRC lines completely. Some systems like the N64 have almost no CRC values in it but I would still like to import all the other information’s from the synopsis file.
-
I love this tool of yours. With the feature to scrap from synopsis files I have finally an easy way to get the numbers of local players in LaunchBox. Now I really would love to see an updated version with better error handling. I have many synopsis files which just give me an ‘invalid synopsis file’ error and I really don’t know in which line I could fix the errors.
-
Oh sorry, I kinda missed that your games are zipped. I’m using RocketLauncher to launch all my games. It extracts all of my games before the game starts so that was never a problem for me. Sorry for the confusion.
-
1
-
-
I'm using NeoRaine for NeoGeo CD games and I don't had to struggle with TXT files or such. Some games have, besides the better music quality, additional features like the Combat School in Metal Slug 1 & 2 in their CD version. On the other hand some games are missing frames and animations compared to their cart version. Here's a list which features some games and their differences of the various versions: http://www.gamefaqs.com/neogeocd/916662-neo-geo-cd/faqs/51773
-
What about an extra section in Retro Style Spotlight? I mean emulation news would fit perfectly fine with the other retro news, especially if it’s on a channel for a product like LaunchBox which is designed for using emulators. But I also would say there’s no need to cover it weekly, just throw it in when a huge release did come out.
-
I’m sorry you feel that way. I LOVE the early 3D era of gaming. The look and feel of many of these games is such unique and has its own interesting experimental style, graphical and gameplay wise. Maybe I’m too nostalgic about it because I grew up with it and the N64 was my first console ever. But nonetheless the PS1 is still my favorite console of all time and I love to play games for it still today.
-
My method to do this is with the tool 'Rom Folder Cleaner' and the current HyperSpin MAME database. But it requires having RocketLauncher installed and MAME already set up in it. If you don’t use RocketLauncher could this method be a little bit too much work for such a minor task but if you want I could write a tutorial how to do it. The much easier method would be to just import your whole MAMEset in LaunchBox, then using the genre filter, go to the genres you don’t want and then delete all the games in this genre.
-
There are programs like ROMlister which can filter your MAME romset. I don't use it myself but it should be worth to check it out.
-
Haha, I have to admit that for two or three seconds I was really confused to see here a German word.
-
It’s exactly the same. Typically you update your ROMs and CHD together in the whole process. But if you want to only update your CHDs it’s absolutely no problem, it’s just a checkbox to uncheck.
-
Guess we have to wait for Mobygames then. But what about Giantbomb and Arcade-History? The first one already has an API and the second one is a database file designed to get scraped from. It would be nice to have some info on what is worked on at the moment. Sorry if I sound too pushy but with Arcade-History integrated I could finally start to set up my LaunchBox and import all of my arcade systems.
-
Oh ok. I only looked in their wiki and there was nothing about this topic.
-
Most trackers don’t like proxys but I couldn’t find any rules against it on their site.
-
If you want the most recent MAME set it is indeed the best option to go. The MAME sets are even 'free' so you don't need to build up any ratio to download them. Just register there and grab it. But again, if you don't want to download the 300 to 400GB CHD set each time it is easier to learn how Clrmamepro works and just update the set you already have. And I also think that Jason don't want to see here any links to ROM sites even if they are private trackers with strict rules that don't allow any current systems.
-
I'm using Microsoft Security Essentials and never got any warnings. And Clrmamepro is one of the most common programs in the MAME community so it should be definitely clean.
-
You can update from 161 to 170 in one step but you will still need all update packs from 161to162 till 169to170 to do that.
-
For starters I would recommend the offical Clrmamepro tutorial: http://www.mameworld.info/easyemu/clrmameguide/clrmame-guide.html If you need help just ask. I used that program so many times I could rebuild and update a romset while I’m sleeping.
7. Now your newly created profile should show up in the profilelist. Double-click on your new profile.
8. Now Clrmamepro wants to extract the database from your MAME .exe file. Click on OK. After a short scan it may ask you if you want to import SoftwareLists. If you don’t use MESS within MAME you won’t need that.
I don’t use MESS or want to update a MESS romset so I say “NO” to the SoftwareLists.
Now some error messages are popping up. That’s totally normal. Just confirm every message with “OK TO ALL”.
9. Now you’re in the main menu of CLRmamepro. At first we have to set up our rom paths. Click on "Settings" for that.
10. In the left upper corner you can select for what kind of files you want to set up the paths. We want to add our ROM-Paths so we select “ROM-Paths”.
You can either click on “Add” to add your paths or just drag-and-drop them into the window. So add the path to your current romset you want to update. (NOT the paths which are containing your updates!)
11. Every file CLRmamepro finds within the ROM- and Sample-Paths which don’t fit to the current MAME version will automatically be moved into the Backup folder. The standard setting for this is a folder called “backup” within CLRmamepro folder.
If your CLRmamepro installation is on the same drive as your MAME romset than you can leave it as it is. If CLRmamepro and your ROMset are on different drives I highly recommend changing the backup folder path into an empty folder which sits on the same drive as your ROMs. It will highly increase the speed. Leave the rest as it is.
12. Change the path type to “Add-Paths”. Here you need to add every path you want the program to look for updates or new ROMs you want to add.
IMPORTANT: You have to add the backup path too!
In my case I want to update from 0.170 to 0.171 and add the extra games for MAMEUIFX.
13. Optional: If you want to scan/fix/update your Sample files too, choose “Sample-Paths” and add the folder for it as well.
A small explanation what sample files are (thanks Google): Samples go in a folder called 'samples' in your main Mame directory. They are used in conjunction with games that either doesn't have emulated sound or used external sound samples via another device (like a Tape). Mame will automatically use the correct ones with the game if they are present in the samples folder.
14. Close the window. All settings are being saved automatically.
Step 3: The Scanner
15. After we have set up all paths we want that CLRmamepro scans our current romset and fix/remove every outdated ROM, CHD and Sample file. For that we click on "Scanner".
16. The “You want to scan” section is self-explanatory. In the “You prefer” section you have to choose how you want your romset to be constructed. For the best compatibility with LaunchBox I highly recommend a split or non-merged set!
Here are the differences between the different set options:
Non-Merged: Each set has ALL files it needs. This is normally a waste of disk space because even clone sets have the parentsets included.
Split: Parent sets only have the parent files and a clone sets consists of the clone files only.
Merged Sets: Full merged sets are parentsets only, which also include all clone files. So you will have every version of the game in just on file.
I don’t want to waste disc space so I go with a split set in this tutorial.
17. “Prompts” you can leave it as it is.
18. In the check/fix section we want to check and fix everything. Click on “All” and every checkbox should be checked now.
19. Ignore the “Advanced” and “LogFile” button and click on “Systems”. A new window opens up. Here click first on “All” and then on “Auto-Assign”. It will automatically set the paths for all systems into the ROM-Path you chose earlier. At the end of this tutorial I will say something more to this but for now just close the window.
20. Click on the “Hash & CHD” button. In the new window check both options at the bottom “Run Analysis” and “Fix file (If Possible)". These options will decrease the scanning speed but if you have corrupted ROM files it will try to repair them automatically. Leave the rest at is and close the window.
21. Ignore “Statistics”. Now we have configured the scanner and it should hopefully look like this:
22. Click on “New Scan” and wait. The scanner will tell you if it finds something which needs to be fixed. Confirm every message with “Yes To All”.
In the “Scan Results” window you can see exactly what is currently wrong with your romset. You don’t have to worry about that.
23. When the scan is finished a window pops up that’s giving you information about the current status of your ROMset. Click on “OK” and close the scanner.
Step 4: The Rebuilder
24. Our ROMset is cleaned and fixed now. At next we have to update it to the new version. For that click in “Rebuilder”.
25. Check the box “Use Add-Paths” and CLRmamepro will use all the paths for the updates that we already set up.
26. At "destination" you have to check the box “Use System Default Paths”.
27. The Merge option should be the same as you chose on the scanner.
28. At “Compress Files” you have to choose which file format you want for your ROMS. I prefer .7z because it saves more space on the hard drive as .zip.
IMPORTANT #1: If you change the file format to a different format as your ROMs are already zipped it will take very long to rebuild your ROMset, because all your ROMs will be extracted and compressed again.
So if you have all your ROMs in .zip files and you want it to change to .7z prepare for a long waiting time until everything is done.
IMPORTANT #2: If you want to use .7z you will have to need 7-Zip installed on your PC.
If you want to use .rar you will have to need WinRAR installed on your PC.
29. Check “Recompress Files”, “Show Statistics” and “Remove Matched Sourcefiles”.
30. Ignore “Systems” and “Advanced” and click on “Rebuild”.
31. Optional: If you get an error relating to a .7z file it helps to copy the “7z.exe” and “7z.dll” from your 7-Zip folder into your “CLRmamepro” folder.
32. Now the rebuilding starts. Depending on your ROMset and your options it could take quite a while. When the rebuilding is finished you get a status report.
33. Click on ok and close the rebuilder. Now we are almost finished.
34. If you want to update your CHDs you can now move the CHD folders from your Update folders into your ROM folder. If Windows asks you if you want to integrate the files in the already existing folders confirm that with "Yes".
35. Do the same with your Sample files if you want to add or update them. Just keep in my mind to move them in your samples and not into your ROM folder.
36. Go back to the “Scanner” and click on “New Scan”.
37. If everything worked the new scan result screen should look like this:
I only miss a sample file for one game which I couldn’t track down yet. Everything else is complete and now up to date.
38. Now you can delete all your update folders.
Bonus Step: Split your ROMset in different systems
If you don’t want every ROM in one big single folder and instead separate folders for separate arcade systems you can split them with CLRmamepro too.
For example I like to have my NeoGeo ROMs separated because I want them as a separate platform within LaunchBox.
Go back to the “Scanner” and click on “Systems”. Choose the System you want to be separated from your other ROMs and make a double-click on the path.
Choose or create an empty folder in which you want to move the ROMs for that system and click “OK”.
Now click on “Move Sets” and the program will automatically move all ROMs into the folders you chose.
NOTE: If you want to scan your ROMs again a message will show up saying that the new paths for your systems aren’t ROM-paths. Click on yes to add them automatically to your ROM-Paths.
The end.
I hope this tutorial was understandable and useful for some of you. If you have questions feel free to ask.
I tried it with a SNES, NES, N64, PS1 and Genesis synopsis file. The only file that was working was Genesis. At all the others I get the same error. I also uploaded the SNES one so you can test it yourself.
Best Practice for keeping MAME ROMs up to date
in Emulation
Posted