Please login or register.

Login with username, password and session length
Advanced search  


The new forum is online, hope you enjoy it!

Show Posts

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.

Messages - Roman

Pages: [1] 2 3 4 5 6 ... 116
clrmame Discussion / Re: Of .zip and .7z
« on: 06 December 2017, 15:38 »
The scanner, when fixing files or adding files via fix-missing, checks a) does the set exist, if yes, take its archive mode, b) if the set does not exist, take the prefered one (which is determined on startup by a simple count of all available files)..if no files are available it's zip.

When rebuilding YOU define the archive mode and newly created files use that one. Actually I have to double check what happens when only a file is added to an existing archive....but the case with new files can already mix archive types since no, currently there is no rebuilder routine which only keeps one archive type alive.

clrmame Discussion / Re: ClearMAME Prp and software lists
« on: 04 December 2017, 13:06 »
You're welcome

clrmame Discussion / Re: ClearMAME Prp and software lists
« on: 04 December 2017, 08:46 »
The problem is that your setup is most ikely wrong. I guess (well, pure guessing since you don't give setup details) that you setup one but wrong rompath (where other folders for the software lists are inside it). I've told you before how the official storing method needs to look like and folders in folders is not the way to go for rompaths.

The so called easy mode is to NOT import software lists from the MAME binary (you are prompted at the end of an import) but to use software list definitions (MAME's hash folder files) to build up single profiles for each (Profiler->drag'n drop such files). So one profile for Apple II, one for C64 and so on. If you're familar with that, you can start using the batcher (load multiple dats at once).

The automatic assignement button works perfectly fine, you simply did not understand its purpose and what it does. Calling it "useless" and "a nonsese" shows me that you should first get in touch with some basic setup operations and check out tutorials....or simply stick to MAME's internal audit functionality.

clrmame Discussion / Re: ClearMAME Prp and software lists
« on: 03 December 2017, 20:21 »
Well, ok, as said before, if you use the complex mode, you need:

a) rompaths...for each system one unique one....simply drag'n drop them in the rompath window in settings
b) assigned system default paths...since cmpro needs an indicator which rompath belongs to which system.

both a and b only have to be done only once (unless new systems are added).

The auto-assign button can help you to do b). And b) is done simply to NOT check where to put or fix a file during scan/rebuild every single time.
The action behind it looks in each rompath, checks the files and counts how many of them belongs to which software list. The winner is assigned. If no winner is found (e.g. if you don't have any files at all), the 1st rompath is assigned. In the end you need to ensure that each software lists is assigned to one distinct rompath. So you can't have let's say C64 files together with let's say Apple II files in one path. They need to be separated....which is pretty obvious, isn't it.

Most likely the basic mode with one profile per software list is easier for you to use....there you don't have to care about system default paths at all....and the batcher can actually auto create the rompaths for you, too.

clrmame Discussion / Re: ClearMAME Prp and software lists
« on: 03 December 2017, 18:07 »
For auditing software lists you got 2 options: One full mode, where you have all data loaded in one profile and one split mode, where you use one profile per system.

Mode 1: You need to store sets separated in rompaths per software list. These rompaths needs to get assigned as system-default-paths, which is just a one-click procedure when you got sets already stored in the separated paths.

Mode 2: The easy one...nothing really hard. Simply pick a rompath.

There is nothing you need to do "by hand"....as mentioned before you can easily use the batcher and let it auto create rompaths etc for you.

I don't get it what your actual problem is....it sounds a bit like you simply used a wrong folder as one rompath (where you actually have subfolders for the software lists as subfolders). That's of course a wrong start.....
Keep in mind, there are 2 official storing methods which you need to follow:
rompath\setname\file 1 .. file n (for decompressed sets)
rompath\setname.zip (.rar\.7z) where the archive holds the single set files (for compressed sets).

Comparing MAME for whatever reason here makes no sense.... MAME looks in each rompath and looks as long as it finds matching checksums to see if a set is available or not...it doesn't even care about names.

So maybe it would help if you describe your problem a bit more detailed....with examples...with your setup details

Generally you got a maximum path name limit given by Windows, which is defined as something around 260 characters. However you can switch to UNC style path which the windows api supports, too and then you can have up to 32k characters....this can be achieved by using a "\\?\" prefix in the pathname.

clrmame Discussion / Re: ClearMAME Prp and software lists
« on: 03 December 2017, 09:52 »
what do you mean with refueses to mix?
Of course you need separated distinct rompaths for each imported software lists and the rest of MAME. A software list may contain a set named e.g. dkong which may be used in software lists, too....and you cannot have multiple identical named files in a folder.

Auto assign only makes sense when you already have a setup where sets are split and spread over various paths. Then a simple most-matching-count procedure will assign the paths to the winning software list.

If you want auto rompath creation etc, you should switch to the normal mode where you keep software lists in separate profiles....and you can update them in the batcher in one go

clrmame Discussion / Re: Shared network folders
« on: 12 November 2017, 16:58 »
"my documents" is also protected ;-)

Actually I just tried a "run as admin" installation in an uac folder and adding an UNC path worked fine. A mapped driver letter was not visible though and was not accepted when added manually. So it's clearly connected to the run type...

So for now you can go with UNC paths......and when I find a little time I will check why mapped letters are not shown (they don't appear in the folder dialog either when running in a protected folder as admin)

clrmame Discussion / Re: Shared network folders
« on: 12 November 2017, 16:52 »
I've just tried it with a mapped drive letter, works fine, too..

So....since cmpro simply uses basic runtime file routines it's more a question of access rights. Since you put the cmpro installation into a UAC protected folder you might run into issues...

So...try to move cmpro into a non uac folder....like E:\cmpro, c:\work\cmpro whatever...but not program files....
and run it normally....no prompt, no issues ;-)

clrmame Discussion / Re: Shared network folders
« on: 12 November 2017, 13:48 »
hmm...no problems here.....however I used an UNC path (\\fileserverX\shareY\folderZ)...and haven't assigned a network letter for it....I will do later today...

can you give me some more details...like what is cmpro complaining about, where did you put cmpro, how do you start it (as admin, with additional "run as admin" etc)...

clrmame Discussion / Re: INI/CFG import file format?
« on: 11 November 2017, 13:40 »
Your're talking about the "import" button in the settings window?
It's for importing rompath and samplepath information (and nothing more) from an existing mame.ini file (which is generated by MAME....e.g. via mame.exe -cc)

Users often simply use drag'n drop or the add button to add the rom and samplepaths manually.....so you can of course use this, too

the mame.ini format is a plain textfile with a keyword and the beloning value...rom-, sample paths are semicolon-separated, for example:

rompath                  f:\MAME\ROMs\3DO;f:\MAME\ROMs\AcclaimPSX;
samplepath              f:\mame\samples

clrmame Discussion / Re: weird missing set not listed
« on: 02 November 2017, 20:12 »

<rom name="taito_type_x_bios.bin" size="65536" status="nodump" region="maincpu" offset="0"/>
<disk name="raiden4_v1_00j" sha1="f5ad509f57067089e0217df6d05036484b06a41a" region="ide:0:hdd:image" index="0" writable="yes"/>

So raiden4 consists of a chd and a not-yet-dumped (nodump) rom. Cmpro won't moan about nodump roms but it does if you don't have the chd.

MAME seems to have a problem when it doesn't find at least one rom to load (even if it's a nodump one)....on the other side...hey...you can't start it anyway...the rom is missing ;-)
In other words, cmpro's report is correct...ignore MAME

clrmame Discussion / Re: weird missing set not listed
« on: 31 October 2017, 23:42 »
That's the N-Sub Oscillator 97271-P set....which doesn't hold any roms (only devicerefs and parent samples (actually a clone of nsub samples)....

Since it only references the nsub sample set, you don't miss anything

I will update the miss-list routine to handle it correctly...

clrmame Discussion / Re: Rebuilder/Scanner renaming pattern
« on: 31 October 2017, 19:03 »
Not fullly since the the offical storing method is <rompath>\<setname>\<rom name 1 ... rom name n> for decompressed sets and <rompath>\<setname>.zip/.rar/.7z (where the archive holds the belonging rom files for compressed sets.
Cmpro will always follow this....

Cmpro's rebuilder advance options "Dest prestring" allows defining some pattern during rebuild which is put in front of this general rule. The box allows several variables to be used like %d for description....
I'm not sure if this helps you in your task...but it might be a start

if the set doesnt have any roms on its own you dont need a zip for it and you dont find one anywhere in the net.
I dont have access to my machine till mid next week so currently it‘s just pure guessing and too much typing on a mobile phone :-)
I will check it rhen and come back to you.

check if you:
a) use cmpro with the same versiin which you used for playing
b) enabled all sets/systems and don‘t only work on a subset
c) enabled all check options (sets/roms/chds and all the missing/name/etc)
and you may want to check ithe raiden files manually by comparing mame‘s -listxml output with your files. if they do exist mame might have an issue.

I can doublecheck it mid of next week.

clrmame Discussion / Re: weird missing set not listed
« on: 28 October 2017, 21:14 »
have/miss list is just a quick lookup by setname while a real scan is much more accurate. I‘d trust an empty scan tree output. However I will doublecheck the list generator mid of next week.

"On 23 February 2017, Google announced the SHAttered attack, in which they generated two different PDF files with the same SHA-1 hash in roughly 263.1 SHA-1 evaluations. This attack is about 100,000 times faster than brute forcing a SHA-1 collision with a birthday attack, which was estimated to take 280 SHA-1 evaluations. The attack required "the equivalent processing power as 6,500 years of single-CPU computations and 110 years of single-GPU computations"

This...and the fact that we use crc32 + size + sha1 will make it very unlikely that someone will fake a file for whatever reason to match all 3 attributes

and don't forget, we're mainly talking about rom files which are usually provided by the dumpers themselves which of course want a good dump. Besides of this, modification of files will end in either broken graphics/sound roms or code roms which don't run then....

To sum it up...in the MAME world, there is no need to switch to SHA512 etc....  ...and as long as MAME doesn't include a new hash you won't see it in cmpro

clrmame Discussion / Re: Request for new option in batch mode.
« on: 16 October 2017, 06:41 »
"invert" is an action which is applied once (when you click the button).
If you want to get it applied after profile load, you need to check "initial invert".

"Logical not" is different to "invert". It applies a logical not on each of you "select sets" selection. Invert works on the final selection only.

So if you apply a logical not on "a*;b*" you get something you might have not expected...you get not(a) or not(b)...where not(b) of course enables some of the 'a' again ;-)

Pages: [1] 2 3 4 5 6 ... 116

Page created in 0.103 seconds with 20 queries.