21
clrmame Discussion / Re: Download folder - what's it do?
« on: 10 August 2010, 04:40 »The right one is the new name of course. The one without the _18524 extension. What filesizes are you talking about. i don't see any filesizes.The one I listed earlier with the DOS CLI screenshot. One file is 99,344 bytes and the other is 151,743. Obviously, one is very different than the other. Are you not seeing that screenshot?
Quote
two hours? oh please...unzip the cmpro package and if you don't have 1000 defined already, that's it. Maybe create a new MAME profile. If you got 1000 datfiles, you can copy cmpro's datfile folder and let the batchrun create profiles for you...ok..too much advanced stuff already.C'mon, Roman, don't get snarky. I honestly don't know how to use this program, what with its numerous, rather arcane-sounding options. Defining system paths in and of itself is VERY clunky and requires a LOT of mouse-scrolling and clicking. I just spent the last half-hour redefining those system paths after you (strongly) encouraged me to move the cmpro installation folder. If there was an easier way, such as saving a config file, I'd love to hear it. And I have NO idea what you mean by letting "batchrun create profiles for you" (though since I'm not using external datfiles, I assume that's not relevant). When I uninstalled cmpro via its own uninstallation utility, I did see where several files were left over, but I had no idea what to do with them in preparation for a new installation placement.
But generally unzipping the program, creating a MAME profile, setting up rompaths is a 2 minutes job.
Quote
Simply let me know which files are present in the4 drmn2mpu. If it's only one chd file which got a _randomnumber extension, then simply let cmpro rename it.Well, again, that's detailed in the DOS CLI screenshot. There're only the two CHD files, one with the _randomnumber extension. And the entire problem is that cmpro does NOT want to rename it (see log entry screenshot). What other information do you need to know?
Quote
The rebuilder rebuilds/adds anything valid from the source to the destination. There is an option which removes rebuilt files from the source. These includes zips and folder if they are empty after the rebuilt file was removed. So it cleans itself automatically...Usually you got text files or other garbarge...they won't be removed.Hmmm, I'll have to play around with that option. If you've enabled the option to remove rebuilt files from the download source, why would you want to save any leftover files for later?
So check what is still in the source after you've used the remove source file after rebuilt.....and save that for later.