Print

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

[Roman]

well...as you might noticed, it's pretty silent around cmpro...why? well...holiday season is coming up...end of year real life stress....

But from time to time I add some tiny not really that important stuff...currently this...

misc:  32bit version still runs on SSE1 processors
misc:  updated to unrar lib/sdk 5.30 (final)and 7z lib/sdk to 15.12 (final)
misc:  select sets variables %h=1 (has chds) also supports =0 now (hasn't chds). Same for %p,%M,%B,%I.
added: added %r=1/0 variables (has roms)
added: dir2dat can export in softwarelist format (pretty preliminary but a start)
removed: cmpro.ini switch Adv_DatFormatXML
added: export format (in setinfo dialog) can now be switched via dir2dat format option

to do: some select sets variable to select chd-only, sample-only, roms-only sets (which isn't identical to %r=0...since there are sets which only consist of e.g. biosroms and chds...or only nodumps and chds...etc...have to think about that a bit)



haven't fully checked the softwarelist.dtd yet. (maybe a dataarea element can have all roms as childs and its size entry is the sum of all sizes)...but an export (from standard MAME sets) will look probably like this...

<?xml version="1.0" ?>
<!DOCTYPE softwarelist SYSTEM "softwarelist.dtd">
<softwarelist name="MAME" description="Current MAME">
   <software name="005">
      <description>005</description>
      <year>1981</year>
      <publisher>Sega</publisher>
      <part name="" interface="">
         <dataarea name="rom" size = "2048">
            <rom name="1346b.cpu-u25" size="2048" crc="8e68533e" sha1="a257c556d31691068ed5c991f1fb2b51da4826db"/>
         </dataarea>
         <dataarea name="rom" size = "2048">
            <rom name="5092.prom-u1" size="2048" crc="29e10a81" sha1="c4b4e6c75bcf276e53f39a456d8d633c83dcf485"/>
         </dataarea>
         <dataarea name="rom" size = "2048">
            <rom name="5093.prom-u2" size="2048" crc="e1edc3df" sha1="4f593546bbb0f50850dc6286cb514af6831c27a7"/>
         </dataarea>
etc..etc..

[Roman]

Part of softwarelist.dtd:

<!ELEMENT part (feature*, dataarea*, diskarea*, dipswitch*)>
         <!ATTLIST part name CDATA #REQUIRED>
         <!ATTLIST part interface CDATA #REQUIRED>
         <!-- feature is used to store things like pcb-type, mapper type, etc. Specific values depend on the system. -->
         <!ELEMENT feature EMPTY>
            <!ATTLIST feature name CDATA #REQUIRED>
            <!ATTLIST feature value CDATA #IMPLIED>
         <!ELEMENT dataarea (rom*)>
            <!ATTLIST dataarea name CDATA #REQUIRED>
            <!ATTLIST dataarea size CDATA #REQUIRED>
            <!ATTLIST dataarea databits (8|16|32|64) "8">
            <!ATTLIST dataarea endian (big|little) "little">
            <!ELEMENT rom EMPTY>
               <!ATTLIST rom name CDATA #IMPLIED>
               <!ATTLIST rom size CDATA #IMPLIED>
               <!ATTLIST rom crc CDATA #IMPLIED>
               <!ATTLIST rom sha1 CDATA #IMPLIED>
               <!ATTLIST rom offset CDATA #IMPLIED>
               <!ATTLIST rom value CDATA #IMPLIED>
               <!ATTLIST rom status (baddump|nodump|good) "good">
               <!ATTLIST rom loadflag (load16_byte|load16_word|load16_word_swap|load32_byte|load32_word|load32_word_swap|load32_dword|load64_word|load64_word_swap|reload|fill|continue) #IMPLIED>
         <!ELEMENT diskarea (disk*)>
            <!ATTLIST diskarea name CDATA #REQUIRED>
            <!ELEMENT disk EMPTY>
               <!ATTLIST disk name CDATA #REQUIRED>
               <!ATTLIST disk sha1 CDATA #IMPLIED>
               <!ATTLIST disk status (baddump|nodump|good) "good">
               <!ATTLIST disk writeable (yes|no) "no">


So...assuming dir2dat finds multiple roms connected to one set....what is the most common way to export them....each rom in a single part / dataarea / rom path or one part / dataarea path with all roms below it?

[Pernod]

So...assuming dir2dat finds multiple roms connected to one set....what is the most common way to export them....each rom in a single part / dataarea / rom path or one part / dataarea path with all roms below it?

How would dir2dat know that multiple roms/floppies/cassettes are associated with a single set?

I would expect this to simply export a directory with each file being a single part:

<software name="filename">
   <description>filename</description>
   <year>?</year>
   <publisher>&lt;unknown&gt;</publisher>
   <part name="flop1" interface="floppy_5_25">
      <dataarea name="flop" size="filelength">
         <rom name="filename" size="filelength" crc="filecrc" sha1="filesha1" offset="0" />
      </dataarea>
   </part>
</software>

The dataarea name 'flop' and interface 'floppy_5_25' could be manually entered and applied to all items in the list, as they can be unique per machine/list.

The export would substitute filename, filelength, filecrc, filesha1 for the values for that particular file.

After export, the softlist creator would then have to manually amend software name, description, publisher, year but would at least have a significant portion of the softlist pre-generated.

[Roman]

It "knows" that the same way as it currently does. A found folder or an archive forms a set...If it contains more than one file, it collects the files as roms for that set.

As I said...for MAME this is pretty common...for consoles or other retrosystems it may be 1 rom per set anyway (where the xml tree problem ain't a problem)....so I only wondered about multiple roms....then you can have various versions...
1 part element, 1 dataentry element, 1 rom element for each rom
...or 1 part, 1 dataentry, multiple rom elements
...or 1 part multiple dataentry elements with 1 rom element each
etc...etc...


...and actually the export routine is used by dir2dat and set-information's export functionality...so you can export anything loaded into software list format then....sets with no roms, one rom or multiple roms...

[Pernod]

It "knows" that the same way as it currently does. A found folder or an archive forms a set...If it contains more than one file, it collects the files as roms for that set.

Makes sense to keep that functionality, does it also treat zip files as folders?

I currently have a folder containing over 3000 floppy images waiting to be added to a softlist. This folder contains a folder for each Publisher. Could we have an option to handle this, to populate Publisher according to folder name?

[Roman]

as I said, "A found folder or an archive forms a set", so yes, files in an archive (zip/rar/7z) form one single set by default. However there is an option to handle archives as files, then they get added as single rom entries.

The folder name is used for the setname by default. Again, there is an option to generate Single-File-Sets...then I guess each found file generates a set and the setname is taken from the filename (have to double check that). Guess in that mode I may be able to add an option to have folder name as manufacturer/publisher or maybe freely mappable to something useful (however there is not that much left...maybe year....but nothing important I can think of at the moment)