Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: CLRMame Pro - Help me not destroy my romset!  (Read 1012 times)

0 Members and 1 Guest are viewing this topic.

Joystick Jerk

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 491
  • Last login:June 26, 2024, 05:10:33 pm
  • Slave to the stick.
CLRMame Pro - Help me not destroy my romset!
« on: July 14, 2007, 12:19:54 am »
I'm just doing my first audit of my romset with CLRMame Pro, and I had a question about the Scanner function.

So far everything looks good as far as completeness goes, but when I scan I'm getting ---steaming pile of meadow muffin--- tons of "wrong placed file" errors (and I'm using split sets). If I check the options so that CLRMame Pro will fix these issues, will it actually benefit me, or will my romset be trashed?

shock_

  • Wiki Contributor
  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 354
  • Last login:January 30, 2020, 06:23:29 pm
  • In Brisbane, it's GMT+10 all the time.
Re: CLRMame Pro - Help me not destroy my romset!
« Reply #1 on: July 14, 2007, 04:19:24 am »
First - make a complete backup of your set on another physical hard drive.  Then you can relax a lot.

You should be okay as long as you've not disabled backups in CMP.  It should move things it touches to the backup folder.  Every time you update, make sure you rebuild from that backup folder as well, just in case something old is required again, or something else gets borked.

Make sure you're starting from a dat that matches the build of MAME you intend to run with those ROMs too.