The new forum is online, hope you enjoy it!
Well, basically your setup should not include rompaths in rompaths...that's all you have to care about.I keep hearing this, but don't understand what it means. So, what should my directory structure look like? Surely I've got to at least have a root roms\ directory with every system path beneath it...? Anything else would seem like complete chaos.
Take one of the multiple instances and move (copy+delete) it to a new folder (not a rompath folder). Then use the rebuilder to readd it to the correct place in your collection.Well, I'll do you one better. I'll MOVE everything out of the standard\ directory (even the subdirectories) into my usenet download directory. Then let rebuilder take it from there. HOPEFULLY, that will resolve this mess I've gotten myself into. I just don't have the patience to do this one-at-a-time.
Cmpro moves replaced and "unneeded" files into its backup folder.Well, there's almost nothing in the backup folder (14 files), so I can't imagine it helping much.
So if you're missing something simply rebuild from that folder to your collection.
You can't add additional ones but you can assign a folder to a bios by double-clicking the "assigned sysdefpath" column.Oh, believe me, I know. That's what I was doing before using that Auto button (boy, was that a mistake....).
You could e.g. move all your sets to your G:\M.A.M.E.\MameUI64\roms\standard folder and then click on move to get them sorted to the others...(well, of course only the ones are moved which don't belong to 'Standard').Well, I think I may've utterly FUBAR'd my a great chunk of my whole setup tonite. I don't know what happened, but here's what I did:
For you and your setup (iirc, you had unsorted ones in G:\M.A.M.E.\MameUI64\roms and want them moved to G:\M.A.M.E.\MameUI64\roms\standard), you need G:\M.A.M.E.\MameUI64\roms setup as one sysdefpaths, otherwise the MOVE operation won't work for you....But how do you "add" a definition/directory to SysDefPaths? It looks like all the slots are hardcoded. I did add "G:\M.A.M.E.\MameUI64\roms\" to the ROM-Paths section of cmpro, but that didn't seem to do anything, so I'm presuming it's all tied into the SysDefPaths screen.
Not really....Scanner shows "you prefer". If you scan a fully merged collection as split merged....well, cmpro will split merge it for you during fixing..of course this takes longerOh, well, errr, okay. I take it this means it really shouldn't ever be used? Is that section of the program going to be eliminated in a future release?
Merger is obsolete...since years.
When you care about perfectly compressed sets...If you're sure that all of your zips are already compressed with a fine zip compression setting, you don't need to enable it.Well, I wasn't sure they were already compressed, with a fine zip compression setting or a coarse one, hence why I used this option.
Or you recompress them later on as a batch (or with Zipmax).
Ah...ooook...I will have a look at that functionality. Can you send me your cmpro.ini file plus the .cmp file belonging to your profile (in cmpro's settings folder). Currently I assume you got a rompath "G:\M.A.M.E.\MameUI64\roms" and defined the "standard" sysdeffolder as G:\M.A.M.E.\MameUI64\roms\standard"....That's correct. It seemed the most logical way to do things in order to fully separate rom files from their respective systems. Is this not the usual way it's done?
by the way, having capsuled rompaths ain't a good thing to use...Uh oh. I'm almost afraid to ask what this means. You mean it isn't a good idea to use the whole "Systems" feature and split out the roms accordingly?
Either look at the datfile (if you used an exe to import the data you can export the datfile in set-information window) or check the set-information window and click on the names....you find the "rom-of" information at the top of the screen.Ah, okay. I'll definitely give that a whirl.
Well, yes. The program and documentation makes it very clear that cmpro MUST know what sort of files its dealing with when doing its various operations, so I figured I'd go ahead and make sure I had the sets in the right "format" (split-sets). The Merger seemed like the only way to ensure this, so I hit the button and just let her rip.QuoteOkay, I'll try that and will get back to you. Right now, I'm running a merging operation that's going to take awhile, as I've got about 200 gigs of files for cmpro to process.Don't tell me you're using the Merger for this....Scanner and rebuilder are way faster and more reliable. The Merger is an old time left over...
Rebuilding a whole night? Either you got a very very slow CPU/HD or you didn't use the "no recompress" option.No, it's a pretty fast system (Core 2 Quad 9550 [non-OC'd]) with four gigs of PC2-8000 running Win7 Ultimate x64. And you're right, I had the "Recompress Files" option checked (I don't remember checking it, though). I take it this is an unnecessary option to enable? Since it is an option, when is it necessary?
What is the manual button? What "move set" operation? If you want to rebuild to systemdefaultpaths, you need to tell the rebuilder to do so.What I referred to the "manual button" is (in reality) the Move Sets button under systems. Sorry, it was late and I wasn't being clear.
at least I found the reason for the "version" prompt issue....fixed for next releaseThat's good news. At least all my I'm sure tedious questions haven't been entirely unproductive.
Ah there...well...what you can do is, simply rename both chds to something random. clrmamepro will detect them as being wrong placed/named and will move/rename them to their correct place/name.Okay, I'll try that and will get back to you. Right now, I'm running a merging operation that's going to take awhile, as I've got about 200 gigs of files for cmpro to process.
Actually not. First of all, system default paths is already something the more experienced users use and secondly, Hit the "auto detect sysdefpaths" button and it will assign them for you.Well, I thought that was probably an "advanced feature", but figured it was better to bite the bullet now rather than tackle it later. Also, from what I recall, the ADS button didn't assign the subdirectories properly, as I did try the option. However, when this merging operation is finished, I'll try it again and see what happens.
Because you might need them? Becuase they may be files which get added to MAME later on? Because you collect .txt files in zipsHey, that's why I was asking. And I meant in regards to successfully rebuilt files, not unsuccessful ones. I'm a big fan of keeping a "pruned" system, so if a file has been processed and isn't needed anymore, I'd like it deleted. What sort of .txt files would one collect in a zip file? What sort of files should one definitely keep around for "just in case" purposes? Both of those are honest questions (IOW, I'm not trying to be sarcastic).
