EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

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] 7 8 9 10 11 ... 158
101
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 05 June 2022, 19:09 »
Thanks, due to weekend/holiday I will have a look at it later this coming week

102
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 05 June 2022, 19:08 »
Nothing needs to be unpacked.


Are you using a full softwarelists import? Since such files which are listed as misplaced are not part of MAME (without softwarelists). In other words:  For a non-softwarelist MAME, they can be removed. For a software list import MAME profile, they simply don't belong to your Mame_ROMs folder. You can manually move them away.

103
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 05 June 2022, 19:03 »
No set behaviour at all is hardcoded.
You said you're using a datfile without disks. Can you send me that one please.

104
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 04 June 2022, 06:37 »
You're right, dinokich and others should also appear then. Why it doesn't do it for you...well....hard to say without knowning all your settings but most likely you have an empty dinokich folder in one of your rompaths which fools the set check. If the set check finds a folder or an archive with the name, the set check will be ok....an enabled chd check will of course tell you that the chd itself is missing though.

105
clrmame Discussion / Re: loveber3cn Missing Set ARXMAX
« on: 03 June 2022, 20:25 »
You need to differ between the meanings of the check options "sets" and  "chds", "samples","roms".

The set check checks if the set is available or not. The chd check would only moan about wrong named or missing chds inside the set. A set is a collection of roms and/or samples and/or chds. The rom check would tell you if a rom inside a set is wrong named, wrong checksum etc....

The mentioned set only cosist of shared parent roms but it uses an unique chd. So actually you'd need a rompath subfolder named after your set with the chd in it.
Since you're missing that chd, the set is missing and so the output is right.

106
clrmame Discussion / clrmamepro 4.044d released
« on: 01 June 2022, 19:02 »
while working on *something else* I found two little things in the old thingie....

4.044d (2022-06-01)
fixed: wrong bios set assignments for clones which don't use the bios roms themselves (pwrshovla, v4frfact*)
fixed: not showing files as unneeded which became empty sets over time (e.g. microvsn, mach64, msm6222b, o2_voice)

107
The rebuilder is the solution.

Let the rebuilder source point to your "messy collection" and rebuilder destination to a new folder. Use a datfile (or MAME binary import) for the data basis you want to create your target sets for.
The rebuilder matches anything valid (hash compare) in the source, no matter how it is named and creates all instances of the matches in the destination. Of course this doesn't mean it will create complete sets, just anything valid which can be found.
The rebuilder also supports drag'n drop and/or multiple source folders (via add paths).

108
clrmame Discussion / Re: Creating custom rom sets
« on: 14 April 2022, 12:20 »
the rebuilder only rebuilds roms

109
clrmame Discussion / Re: Creating custom rom sets
« on: 14 April 2022, 08:35 »
I only took a quick look at the page and I guess it selects sets and then does a rebuild. And I'd have proposed the same.

Assuming your collection is ok and on your cabinet you're using the same MAME binary as you're using to scan the collection in cmpro it's like this:

Scanner -> Scan Results -> Set Information, use "select sets" or "from file" or manual ticking the sets which you want (maybe also ticking incl. devices/bios/clone/parent checkboxes)

and then doing a rebuild in the rebuilder where the destination points to a new path (and not removing rebuilt files of course).

110
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 17:53 »
No...I only wanted to point out that it follows a general storing schema (and MAME follows it too).

Either you have your sets in archives (.zip or .7z) OR you keep them decompressed.

Of course 99.99999999999% use archives.

111
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 17:42 »
You can convert your sets by using the rebuilder by the way......

(in case your sets are compressed as zip, you can disable "recompress" in the rebuilder options, so it should run rather fast (depending on your system))

The rebuilder takes everything from the source which matches entries in the loaded dat (match by hash) and creates all instances of that match in the destination. There it uses the correct name etc....

112
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 17:23 »
Unmerged is not "stand alone"...simply due to the device references.
Modern Frontends should all handle split or full merged sets (this is nothing new...)
So there is really no real need to use unmerged (unless I add a real stand alone mode).
I'd say the most common is split....and of course there are some hd-space-gurus who have everything fully merged in solid 7z archives (hey wake up....it's 2022 and TB of HD space is cheap... ;-))

You can turn off Scanner->Advanced -> separate bios sets...in case each of your sets really contains the bios files for their own....(yikes)....

but really....believe me: noone (should) use unmerged sets :-)

113
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 17:14 »
"I have a non-merged set for 0.241"

Then you're the only person on the planet who does that :) and actually I highly doubt that...it does not make sense to keep MAME roms unmerged since they are NOT stand alone. You still have device and bios relations (ok, the latter can be handle with turning off separate bios roms option, but you won't have luck with the device relation.

So....check again...sure that you're using unmerged sets...it's really really really uncommon. Use split instead ;)

114
clrmame Discussion / Re: ClrMame Tutorial
« on: 12 April 2022, 16:59 »
What you normally do:

1 ) Run clrmamepro, go to profiler, add one exe-based profile for *the current* MAME: Profiler -> create... -> filename: browser for your mame binary, description: MAME, Emulator MAME, hit create profile

2)  double click the profile, it will prompt that it runs mame etc....after confirming, it will import data. If a prompt asks you about importing Software lists, answer NO. Other prompts while importing can be answered with OK to all and yes to all.

3) after the main window appears, go to settings, top left drop down box should show ROM-Paths. Now you can add your rompaths here (either drag'n drop or use the Add... button). Same can be done (if needed) for sample paths (if you switch the drop down box accordingly)

4) Go to scanner, select your prefered merge mode (most likely it's split or merged sets) and that's basically it (maybe disable samples if you don't use them). If you now hit "new scan" your rompaths are scanned. Nothing is touched since you didn't enable the check options yet.
Everything which now appears in the scan results window is bad.

Now what does BAD mean:
You can examine the output (expand/collapse) to see what is wrong with the mentioned set.
If you think that can't be right, then maybe your setup is not ok.
For example: You're checking a collection which does not belong to the loaded database or your rompath setup is bad. If you have your roms in e.g. e:\temp\test\neogeo_roms\mslug.zip and f:\other\pacman.zip, then e:\temp\test and f:\other should be setup as rompaths. Or your chosen merge mode does not match the one of your collection.

Enabling the fix options and running another scan will actually FIX the problems (if possible).


This is one standard scan (+ fix)....after that the scan result should either be empty (no problems) or you might miss files (e.g. when a new MAME is out and new stuff was added). There are various ways of adding missing files, one is the rebuilder (rebuilder destination should point to your rompath).


When a new MAME is out, you don't have to repeat all of the above. You simply replace your MAME binary and when you load your old profile, cmpro sees and asks you to update its database. And of course you don't have to resetup your rompaths again or your scanner options.



So basically it's:
- load profiler, run a full scan with all fix options, use the rebuilder to add missing stuff (there are some nice scanner context menu options for drag'n drop which automatically run another scan after a rebuild etc....)


"Tons of errors" is not normal. As mentioned, you either use a wrong database, didn't setup the rompaths correctly or used a different merge mode.


Maybe some additions:

You should store sets like this (and setup your rompaths accordingly)
rompath\setname.zip (.7z/.rar) for compressed set
rompath\setname\file 1... file n for decompressed sets

so e.g. c:\temp\test\puckman.zip (with puckman.zip holding the puckman roms and c:\temp\test is your rompath)
or c:\temp\test\puckman\pm1_chg1.5e (and so on) (with c:\temp\test is your rompath, puckman is the setname which is a folder then and the single files like pm1_chg1.5e inside that folder


The merge modes:
- full merged (sometime also simply called "merged"): Only parent sets exist but the sets include the clone set files, too
- split merged (simetimes simply called "split"): Each set exists but the clone sets only hold the files which are unique and aren't shared with the parent set
- unmerged (not merged): forget that mode...it's not really used, each set exist and even clone sets have the shared parent files in them...a waste of diskspace and not even a real standalone since today a set has other dependencies as well (bios / devices).

115
clrmame Discussion / Re: Different dat with the same name
« on: 09 April 2022, 08:11 »
The detection mechanism works by looking at the name element inside the dat file. So filenames don't play a role. If you're not the author of the dats, you will run into the same problem with the next update....so I guess you either convince the authors of changing the name somehow or be aware when loading the dat that you select a different option and not click on update ;-)

It's not really planned to add work in cmpro to change this behaviour at this point in time.

116
You don't need to copy it back since in 242 it doesn't exist anymore. As I said...it doesn't have any roms on its own but only device references now.

117
Don't worry about the resize. That's the normal behaviour when it sees that the file is there (identical name) but size is not correct.

Resize tries different things, not only cut down but also fill up with 0x00 / 0xff or double the rom to match the checksum.

So...ignore the message, the real problem was that when it adds the found missing rom, the existing one wasn't copied to backup.

118
in 242, pcmx2 does not have any roms. It only consists of device references....
in 241, it contained some roms which are now devices.

So it's ok that it was removed for 242....however it shouldn't be listed as missing. Most likely another full scan fixes that.

119
I was able to reproduce it with your files. Will check what is different

120
clrmame Discussion / clrmamepro 4.044c released
« on: 30 March 2022, 18:25 »
4.044c
fixed: Scanner fix missing, backup fails when replacing a file in an archive and file is replaced silently


Pages: 1 2 3 4 5 [6] 7 8 9 10 11 ... 158

Page created in 0.128 seconds with 20 queries.

anything