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 ... 109
1
clrmame Discussion / Re: MAME's Software List ROMs
« on: 09 January 2017, 07:34 »
cmpro's supported software list files are the XML files.

2
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.

3
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).

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

5
clrmame Discussion / Re: Feature Request
« on: 04 January 2017, 09:47 »
it's not that easy to have multiple colors within one tree entry lines....different lines, different color are ok...


6
Sorry, but there won't be a minimal fixdat.

What is a fixdat, well, it's simply a printout of the loaded datfile but limited to the missing files.
So basically it uses the loaded data and hides some entries (the existing ones).

7
fixdats do look like this and this is intended. fixdats are for rebuilding purposes only and the user decides which merge mode is used when using the fixdat,so you need this format.
if you look at a standard mame -listxml output you will see that similar parent clone relationships are listed in a similar manner.

8
clrmame Discussion / Re: Wrong names for CHDs folders
« on: 03 January 2017, 10:22 »
I've updated the post in between...so please reread ;-)

9
clrmame Discussion / Re: Wrong names for CHDs folders
« on: 03 January 2017, 10:10 »
Thanks for the files....I was able to create an environment where I can repeat the problem.

The basic problem is indeed the usage of system default paths.

You can't really use system default paths *AND* a split of CHDs. Both the chd and the roms belong to the "Standard" system.

When cmpro finds area51 (roms) the assigned sysdefpath everything is fine. However if it then sees the area51 folder (chds), the assigned system default path doesn't match anymore and cmpro complains (yes, the message which is prompted is misleading...and that indeed changed a while ago when a problem for softwarelists was fixed).


So...you need to turn off the use of system default paths if you want to keep chds in one folder and roms in a different one.

10
Well of course they are not matching different versions, different data...MAMEUI is not an official MAME build
comparing their -listxml output quickly shows the differences.

see: http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=362166&page=0&view=expanded&sb=5&o=&fpart=1&vc=1

....but which "issues people are finding" are you refering to? Everything here on the board is definetly NOT related.

11
Well....yes...the double naming is not wanted. Should get fixed for the next version... Until then, you can select in batch mode / misc tab: "for default naming use: DatFile Folder" (the line above "for rompath naming use") which will solve the double naming for you already.

12
clrmame Discussion / Re: CLRMamePro + TOSEC Rompaths
« on: 01 January 2017, 20:32 »
let's keep this thread untouched.....I will reply in your other post

13
clrmame Discussion / Re: CRC issue with newest ClrMAME?
« on: 01 January 2017, 20:24 »
The file perfectly rebuilds to:
avalnc13, avalns13, avalonc, avalons

"The Key of Avalon 1.2" is NOT part of this list but this set is a clone of avalnc13 and shares the file in question with it.

14
clrmame Discussion / Re: ClrMAME and ROMs in directories.
« on: 01 January 2017, 19:48 »
cmpro replaces illegal characters in setnames ( like ><*? / \ etc) with - ....and it does this since years....so if you think it was working last year, your datfile was structured differently.
So again, setnames cannot hold \ / for specifying subfolders. You can move the name to each romname though:

rom name="[BIOS] PC-6001 (60) [ROM]\BASICROM.60" ...

15
clrmame Discussion / Re: Wrong names for CHDs folders
« on: 01 January 2017, 19:44 »
hmm...I can't repeat your described problem. So your cmpro.ini and settings/datfiles would be helpful.

Did you enable all sets?
On which system do you run cmpro (linux/mac/windows)?
For the sets in question, can you check the rompaths if folders/archives exist multiple times or describe (e.g. for firefox) what file is stored where?

16
clrmame Discussion / Re: ClrMAME and ROMs in directories.
« on: 28 December 2016, 13:15 »
combining dats can be done but not by using folders on setname level.
for quick scanning multiple dats cmpro's batcher is the prefered method. when Im back from holiday I can go into details

17
clrmame Discussion / Re: Wrong names for CHDs folders
« on: 28 December 2016, 09:38 »
I will be back on Jan 1st. so I can't look into this now.

In the meantime you can send me cmpro.ini and the to the profile belonging files from cmpros settings and datfile folder

18
clrmame Discussion / Re: CRC issue with newest ClrMAME?
« on: 28 December 2016, 07:05 »
I will check it in 2017...now back to my holiday :-)

19
I will tell you in 2017....now back to my holidays :-)

20
clrmame Discussion / Re: ClrMAME and ROMs in directories.
« on: 27 December 2016, 20:18 »
what is superdat?

and again, nothing regarding subfolder usage or storing method has been changed. rompath/setname/rom1..N where rom1..N can be stored within an archive or a folder and can have subfolders.

double think about the definition of a set in this context. a set is a collection of roms not a collection of games. pacman is a set in eg Mame and it contains some roms, the ic dumps from the pacman arcade board.

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

Page created in 0.093 seconds with 20 queries.

anything