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 ... 110
1
Sharing rompaths for different emulators will always cause problems when auditing. Simply because normally there are too many differences, not necessarily in the sets themselves but in e.g. parent/clone relationships. Every files which is inside a rompath and does not belong to the currently loaded data is marked as unneeded (if the unneeded option is selected)...

Well, of course there is a way....Each profile got the "common roms folder as rompath" plus the specific ones for the current emulator.
The problem is ...what belongs to the "common roms". clrmame can't know since it only looks at the current data. You may need a different tool which compares n datfiles and tells you which sets go in there. Too much manual work if you ask me.

Now maybe with the mentioned MAME versions it can be a bit easier...as long as parent/clone relationships are identical and they only differ by having more sets (like Aracde64 as basis, MAME64 includes arcade64 + mechanical ones and finally fx includes mame64 + some extra ones). Then you simply have 3 profiles, Arcade64 one with one rompath, MAME64 with 2 and fx one with 3).
But even then fixing might be critical since cmpro does not know where to put new sets (fix missing). Normally it looks for the best place (parent/clone relationship,existing files, or first rompath)....and then you might mix up sets again.


So....actually you should rethink the idea of having multiple MAME installations ;-)

2
clrmame Discussion / Re: Custom Parent-Clone Dat Question
« on: 13 February 2017, 19:09 »
1) not really a difference....mame switched to machine a while ago, cmpro will parse both
2) the set name is usually a short name which is used for the file/archive (Mame still uses 8.3 naming in 99.9%). Description is a full descriptive name....which is not used for filenames though...it's more for frontends/cmpros output

3
clrmame Discussion / Re: Custom Parent-Clone Dat Question
« on: 13 February 2017, 17:21 »
You can simply add a release tag to the parent set like <release name="Knuckles' Chaotix" region="EUR"/>.
In case of full-merged sets it will use that name then.

  <machine name="Knuckles' Chaotix (Europe)"> 
    <description>Knuckles' Chaotix (Europe)</description>
    <release name="Knuckles' Chaotix" region="EUR"/>
    <rom name="Knuckles' Chaotix (Europe).32x" size="3145728" crc="41D63572" md5="4CE9E6B6E8883D8A678D90AABCE022D0" sha1="5C1A2E327A656217604D4BAE7E141764A7E59922"/>
  </machine>
  <machine name="Chaotix ~ Knuckles' Chaotix (Japan, USA)" cloneof="Knuckles' Chaotix (Europe)">
    <description>Chaotix ~ Knuckles' Chaotix (Japan, USA)</description>
    <rom name="Chaotix ~ Knuckles' Chaotix (Japan, USA).32x" size="3145728" crc="D0B0B842" md5="47B1095E68B053125CD2CD5B1AC4EB50" sha1="0C2FFF7BC79ED26507C08AC47464C3AF19F7CED7"/>
  </machine>

4
clrmame Discussion / Re: Wrong Name Issue
« on: 09 February 2017, 07:38 »
Most likely a difference in profiler->options->parse rom 'merge' tags. One installation got it enabled, one disabled.

If you want to enable/disable it is your personal choice/taste. If enabled, you don't care about byte-identical roms in clones (compared to the parent) with a different name in the clone. You will gain some free space.
If you like accuracy and want to keep the original clone naming you disable the option (but that means you have some byte identical files in the parent/clone relationship).

5
clrmame Discussion / Re: Error with sysdefault paths
« on: 05 February 2017, 08:00 »
link works fine here....

6
clrmame Discussion / Re: Error with sysdefault paths
« on: 03 February 2017, 21:01 »
ok yeah....a bug is hiding the real problem:

---------------------------
Bad System-Default-Paths
---------------------------
You're using SysDefPath options and at least one software list path is not unique!
Softwarelist paths have to be unique and cannot be shared with others.

The paths for the following systems are affected:


- [SOFT] Sord M5 cartridges -> G:\_MAME-0.182-Softwarelists\MAME 0.182 Software List ROMs (merged)\mo5_cart\
- [SOFT] Sord M5 cassettes -> G:\_MAME-0.182-Softwarelists\MAME 0.182 Software List ROMs (merged)\mo5_cass\
- [SOFT] Sord m5 diskettes -> G:\_MAME-0.182-Softwarelists\MAME 0.182 Software List ROMs (merged)\mo5_flop\
- [SOFT] Thomson MO5 cartridges -> G:\_MAME-0.182-Softwarelists\MAME 0.182 Software List ROMs (merged)\mo5_cart\
- [SOFT] Thomson MO5 cassettes -> G:\_MAME-0.182-Softwarelists\MAME 0.182 Software List ROMs (merged)\mo5_cass\
- [SOFT] Thomson MO5 floppy disks -> G:\_MAME-0.182-Softwarelists\MAME 0.182 Software List ROMs (merged)\mo5_flop\



ah yeah and the fixed version is here:

http://mamedev.emulab.it/clrmamepro/binaries/cmpro20170203.rar

7
clrmame Discussion / Re: Error with sysdefault paths
« on: 02 February 2017, 13:46 »
thanks, I will have a look at it

8
clrmame Discussion / Re: Error with sysdefault paths
« on: 01 February 2017, 08:15 »
Send me the belonging cmpro's settings folder *.cmp file (for your profile)

From the screenshot it looks like there is one empty one? (There is an empty line above the ....)
....or enable BIOS/MECHANICAL and set them to some folder(s)

Maybe a better way to use software lists is to not use the mixed mode (Software lists/standard mame) but standalone profiles for each list

9
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 31 January 2017, 18:35 »
no issues either....works fine again

10
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 31 January 2017, 17:18 »
So I did more tests...and still no luck.....I can't repeat any issues with that set.
I've tested existing, partly existing, not existing files (source/destination). A direct compare of 181 / 182..., scanner fixmissing and rebuilder....
always the same, it works as expected.

I can only image that your archives were somehow locked by the system (or other tasks......like virusscanners etc) when cmpro tried a write operation at it and failed....

11
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 31 January 2017, 07:32 »
Thanks for the report.

For the rebuilder: Try to rebuild to a new archive (I on my side will test with an existing set in the destination). I will also double check the scanner fix missing (when the set already partly exists with one of both files in it).

12
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 30 January 2017, 06:45 »
I can't repeat that here. It just rebuilds fine. There is nothing uncommon in the dat.  Double checksums where the name differs is a pretty normal thing. The rebuilds finds the source file and creates all instances of the file in the destination.
In this case it creates two files.

Question is now what is different on your system. I've tested it with an import from an official mame .182 64 bit on a windows 10 machine with zip and latest 7zip (not t7z!). Split and full merged mode.


13
clrmame Discussion / Re: 0.182 'missing' ROM
« on: 29 January 2017, 19:58 »
I don't see a problem. The set rebuilds fine (even if you only got one of the files), also the scanner handles it fine.

14
clrmame Discussion / Re: WWW Mode
« on: 28 January 2017, 18:31 »
Websites which want to support cmpro's www mode need to put a special xml file at their page. See
http://mamedev.emulab.it/clrmamepro/docs/wwwprofiler.txt
(section II - What a datfile provider has to know)


15
clrmame Discussion / Re: Occasionally losing 'ROMs'
« on: 28 January 2017, 18:28 »
The rebuilder is a pure "adder". It adds files (which match the checksum) from a source to the destination. If a different file already exists at that place (and doesn't match the checksum), this file is moved to backup first.
So yes, it's pretty common that files which might belong to a different place (due to renames, reorganizations) gets overwritten by the rebuilder....but they are not lost, they are in the backup folder (unless you untick the belonging make-backups option.
The standard way to update sets is running the scanner first with all check/fix options, THEN use the rebuilder to add the missing stuff.
So you only need to rebuild your cmpro backup folder and you get your files back.

16
clrmame Discussion / Re: Feature Request
« on: 25 January 2017, 06:44 »
by the way...if you don't care about the sha1 values at all, you can hide them.

Scanner tree window context menu -> View -> For listed missing roms additionally show -> sha1 (turn that off)

17
clrmame Discussion / Re: MAME's Software List ROMs
« on: 09 January 2017, 07:34 »
cmpro's supported software list files are the XML files.

18
clrmame Discussion / Re: MAME's Software List ROMs
« on: 08 January 2017, 16:40 »
MAME's software list data files are stored in MAME's hash folder and have a XML file extension.

19
The main problem in not directly doing it in cmpro is that MAME uses 1 set per game while progetto Marquees dats and files are using 1 set for all game pngs. So you can't simply export a missing list in one and load it in the other profile to disable the sets (and there would be an option to mark disabled sets as unneeded)....

So you can only use the exported set list for some batch deleting

1) Load the MAME profile, do a full scan/fix orgy until you're happy with the scan result
2) right click any entry in the scan results tree, in the context menu select "Export Set List->To File->" and now either "all set issues" or "completely missing sets only". For completeness you might want to check the menu entry "Export format" which should point to "sets". In any way, let cmpro create the file for you.
3) now you need to do some texteditor magic on the listfile...you can for example add a delete statement and full path to each line + png extension like "del e:\temp\marquees\005.png", save the file as .bat/.cmd and run it


Another idea:

1) Load the MAME profile, go to the scanner, hit "have list.." to save a file which holds a list of your existing sets
2) After its creation, open it with a texteditor, remove the header lines (first 2 lines)
3) add a dummy header before the setlist

<?xml version="1.0" encoding="UTF-8"?>
<datafile>
  <machine name="marquees">

4) add a dummy footer after the setlist

  </machine>
</datafile>

5) add the following to each line of the set list before the setname <rom name="
6) add the following to each line of the set list after the setname .png" status="nodump"/>

So you have something like:

<?xml version="1.0" encoding="UTF-8"?>
<datafile>
  <machine name="marquees">
    <rom name="005.png" status="nodump"/>
    <rom ....
    <rom ...
    ....
  </machine>
</datafile>


Now you got a dummy datfile which can be loaded as a new profile, rompath should point to your marquees rompath and when you run a scan with fix-unneeded you will get rid of anything in the rompath which is not part of the dat (i.e. your existing sets).

20
(oh oh...2017 and no answer yet.....) Looks like I've overseen this post after coming back....will answer shortly

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

Page created in 0.105 seconds with 20 queries.