Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

3241

clrmame Discussion / Re: CLRMAMEPRO 3.126a and MAME 0.131u1

« on: 09 May 2009, 06:47 »

It's a wrong sha1 definition in MAME's shootig master driver. cmpro only adds the file if you turn off (which is normally not recommended) the "check sha1/md5" additional checkmodes in scanner advanced (fixmissing)/rebuilder advanced (when rebuilding)

3242

clrmame Discussion / Re: Bug/Suggestion: Fix Unneeded

« on: 07 May 2009, 19:39 »

Argh, don't set the backupfolder as a rompath subfolder!!!!!

Cmpro supports decompressed sets. They follow the storing method: rompath\setname\file 1... file n

So your just created rompath subfolder is detected as an unneeded set and moved to backup...which is again the same folder.....and this creates a hole in the time-space continuum. Put your backupfolder somewhere else and I will add a check if someone got the weird idea to use the rompath or a rompath subfolder as backup....

3243

clrmame Discussion / Re: Bug/Suggestion: Fix Unneeded

« on: 07 May 2009, 17:42 »

The "Fix unneeded" operation moves the files to the cmpro backupfolder.
No idea what you mean with "unneeded folder".

3244

clrmame Discussion / Re: old mame exe issue

« on: 29 April 2009, 15:50 »

I downloaded mame034 from mamedev.com and put it in a new folder.
I try to create a new datfile with clrmame (selecting OLD_MAME in the create profile window), but at loading clrmame complains about a bad exe output.

BTW from a command prompt mame - listinfo > datfile.dat works perfectly and clrmame is able to load the output datfile.

There was one old version MAME exe which didn't allow an indirect call + redirect due to some djgpp compiler issues...maybe it was .34.

Try .35

3245

clrmame Discussion / #0017 - batcher

« on: 28 April 2009, 20:10 »

Hmm...real life takes a lot of my time at the moment...so just a quick one here...which you most likely already know....

You're bored to scan lots of dats as dat by dat? Well...then use the batcher.
Simply load more than one profile in the profiler (select multiple items) and the batcher window appears with three tabs.

Generally you can scan them in a row plus optionally a rebuild run before each scan (first 2 tabs). The third tab is mostly for naming rules when new datfiles are loaded. Pretty self explaining I hope.

The batcher simply loads the profiles in a row, so the individual n-th profile options are active during the n-th profile run. The options you select in the batcher window overwrite them temporarily. For example your profile removes rebuilt source files and you select in the batch to not remove them, the files won't be removed during a batchrun but they do get removed during a normal run.

3246

clrmame Discussion / Re: nightrai & psyvarrv oddities

« on: 27 April 2009, 16:57 »

Any ideas about this behavior?  Never had it occur before.  I am using the latest version of clrmamepro as well.

Sure I know what's causing this: You had wrong chds. Wrong checksums -> unneeded file -> fix unneeded removes them, after that you still miss the files.

The chds in question were replaced with factory reset versions in 0.130u2. Most likely you had the old ones.

3247

clrmame Discussion / Re: small request

« on: 27 April 2009, 08:51 »

hmmm...actually the profile name column sorts by profile name (btw...why do I don't see the sorting triangle in any of your listheader columns) The profile name however is either the name in the datfile header (description tag) or -if not filled- the datfile name. I will check if I can add something for new datfiles which don't have a profile yet....

3248

clrmame Discussion / Re: Skip confirmation only for certain fix options?

« on: 27 April 2009, 06:27 »

I understand your request...I put it on my list, however don't expect to see it anytime soon

3249

clrmame Discussion / Re: Some CHDs treated differently?

« on: 27 April 2009, 06:26 »

A missing set isn't a missing chd. clrmamepro is correct in showing you the missing set since you actually miss it
There are chd-only sets which consist only of a chd definition, no roms, no samples (and maybe biosroms which are usually separated). If you scan for missing 'sets' and don't have the chd, the 'set' is listed as missing. If you also enable the missing 'chd' check, you will additionally see 'missing chd' messages.
Since disabling the 'Sets' check is not recommended, you can fool cmpro by simply adding an empty rompath subfolder for the chd in question as you did for the other chds. Then the missing set message won't appear anymore (however a missing chd one will appear if 'chd' is enabled).

3250

clrmame Discussion / Re: Skip confirmation only for certain fix options?

« on: 26 April 2009, 12:56 »

Unless I'm missing something, it seems like the confirmation prompts issued by ClrMame when fixing a set are either all on or all off.

Each type of fix got its own confirmation. When a 'wrong name' prompt appears and you click "yes to all" this will only set 'yes' to all 'wrong name' messages. As soon as a different message appears (e.g. 'unneeded file'), a prompt for this is shown.

So you are asked for each group separately. The 'ask before fixing' option however is a general one which enables/disables the prompting.

3251

clrmame Discussion / Re: Some CHDs treated differently?

« on: 26 April 2009, 12:53 »

Hello

With CHDs scanning disabled (I have none), some CHDs sets are still detected as missing (fe. 700a04.chd or psyvaria.chd).
How to disable displaying them as missing?

TIA

Actually this shouldn't happen. Are you sure they are listed as "missing chd" and not by a different thing like "missing set"?

3252

clrmame Discussion / cmpro 3.126a released

« on: 23 April 2009, 20:01 »

3.126a

added: 3 state button bar file
misc:  scanner popupmenu move/copy to operations remember last used path
fixed: bios assignment can fail on rather identical sets (naomigd/naomi MAME .131 issue)

3253

clrmame Discussion / Re: Checksum analysis ignoring fix options

« on: 22 April 2009, 07:29 »

well...7z support is not priority as you might know. Solid archives are always a problem since there are a lot operations in cmpro which are file based (i.e. adding one file to an existing archive). For 7z this would mean that it has to recompress the full file over and over again each time a new file is added. It's a pain. Besides of that, as soon as you got one of the 'deeper' checksum checks (like full archive test, sha1, checksum analysis) enabled, it will decompress files into memory...and again....file by file...for solid archives this would mean it skips 99% of the time

3254

clrmame Discussion / Re: Checksum analysis ignoring fix options

« on: 21 April 2009, 11:28 »

I understand the options I just didn't understand the reasoning. I figured that if you weren't planning on fixing anything there would be no reason to perform checksum analysis, etc. I rebuilt the affected files so I cannot check the behavior. Did it show in the status window which files/sets were fixable? If that's the case, I understand... Because even if I didn't want to fix the problems, it would come in handy to know which were fixable if I did choose to fix them.

First, please differ between checksum analysis and the standard checkum checks.
A checksum check can be e.g. crc32 which can be rather quick for archived files since the checksum check will simply compare the stored information with the database. A checksum check can be more time-consuming when it has to decompress the file to check the sha1 for example.

This is all 'checking'. 'Checking' also includes (if enabled, default is disabled) the checksum analysis. This checks are run when a wrong checksum was found. Then it checks if byte order changes or fills with patterns can create a valid checksum.

Fixing can be enabled by the belonging standard fix options or -for checksum analysis- with the 'fix file (if possible)' option which corresponds to the standard fix operations.


So, by default all fix options are disabled. So actually you don't have to change anything to do what you wanted to do.

3255

clrmame Discussion / Re: Checksum analysis ignoring fix options

« on: 21 April 2009, 08:22 »

so the options are clear now?

3256

clrmame Discussion / Re: clrmamepro auto-minimizing problem

« on: 20 April 2009, 21:39 »

ah...I should read more carefully....XP....and cmpro is filled.

again: cmpro is being created if you run cmpro for the first time and quit cmpro. Actually it always writes cmpro.ini on closing the program. So if you run it for the first time, you won't see a cmpro until you close it.

The scan went fine...it used the default values during that one.

Now that cmpro.ini is filled, you will find your entry in there....but not at top....it used it during start, plus default values for the rest...and when you quit, it wrote your setting + the used defaults (not necessarily in that order).

so...looks fine now

3257

clrmame Discussion / Re: clrmamepro auto-minimizing problem

« on: 20 April 2009, 21:30 »

Are you running Microsoft Vista?

Then be sure that you DON'T use a folder for cmpro which is monitored by UAC.

If you install cmpro to a protected folder like C:\program files\, you have to set the compatibility properties of cmpro.exe to 'run this program as administrator' to work correctly or you have to disable UAC. In other folders it should work fine without setting this property and without the need of disabling UAC.

3258

clrmame Discussion / Re: clrmamepro auto-minimizing problem

« on: 20 April 2009, 20:19 »

Okay, I'm looking in the program folder for clrmamepro, and I don't see any cmpro.ini. The only .ini files are stats.ini, urls.ini, and version.ini. I also tried uninstalling and reinstalling the program, with no difference.

It's being created after you successful started cmpro, used it for the first time and quit.
So since you don't have a cmpro.ini, you can't have illegal sizes for the window....which is a bit weird that the profile isn't shown for you. If you start cmpro for the first time (no cmpro.ini) you should even see a welcome prompt telling you what to do next. Maybe that window is behind of any other window of your desktop.

what you can also try is: before the start, add a "cmpro.ini" file into the cmpro root folder. The file should hold the following two lines:

[CMPRO SETTINGS]
Adv_HideWindow = off

3259

clrmame Discussion / Re: clrmamepro auto-minimizing problem

« on: 20 April 2009, 20:05 »

Hi. I am trying to run the latest version of clrmamepro, but every time I run it, the window comes up for about 1 second, then immediately minimizes to the bottom of the screen, and I can't restore it. I can't right-click it, and if I left-click it, nothing happens. All I can do is bring up the task manager and end the program. I've also tried it with older versions, and the same thing happens. This is the first time I've tried it on my new computer, and I've ran this before on my old computer with no problems. I am running Windows XP SP3 32bit. Anybody have any ideas what is happening?

Also, once I managed to click "options" before it minimized, and I thought it was ok, but then a couple seconds after the options window opened, the whole thing minimized again.

The normal behaviour is that the 6-button main window is hidden when scanner/profiler/merger/etc is opened. In this case however you will see scanner/profiler/etc instead. If you don't see such a window, the saved window positions may be corrupted. You can find them in cmpro.ini...for example:

Win_ProfilerDlgTop = 105
Win_ProfilerDlgBottom = 634
Win_ProfilerDlgLeft = 248
Win_ProfilerDlgRight = 1262


If the profiler window (usually the first window you see after start) is hidden to the bottm left, you should be able to bring it back to normal by clicking the normal windows restore button beside the [X].
If you stop cmpro, remove the upper mentioned lines from cmpro.ini and restart cmpro, the default values will be used again.

When running cmpro under MacOS/CrossOver it's recommended to set: Adv_HideWindow = off  in cmpro.ini


In general it sounds like your profile window settings are corrupted somehow....since that's the window which a) hides the 6 buttons one and is shown right after start.

3260

clrmame Discussion / Re: Updating CHD files

« on: 20 April 2009, 18:30 »

Will ClrMamePro support automatically upgrading the CHD files in the future?

No since there is no need. chdman does the job just fine and it's no big deal to write a batch file which automatically converts all chd files.