Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Help needed with xml extension

General
Marcel
2006-01-31
2013-04-03
  • Marcel
    Marcel
    2006-01-31

    Hello,

    Does anyone know how I can define an extension xml file consisting of different ROM/RAM parts? If I specify the specific slot it works fine, but as soon as I specify 'any' as slot openMSX just divides the ROMs in different slots/subslots.

    I'm trying the following:

    <msxconfig>
      <primary slot="any">
        <secondary slot="any">
            <ROM id="ROM1">
              <mem base="0x0000" size="0x2000"/>
              <rom>
                <filename>roms/rom1.rom</filename>
              </rom>
            </ROM>

            <RAM id="RAM">
              <mem base="0x2000" size="0x2000"/>
              <mem base="0xA000" size="0x2000"/>
              <size>0x2000</size>            
            </RAM>

            <ROM id="ROM2">
              <mem base="0x4000" size="0x4000"/>
              <rom>
                <filename>roms/rom2.rom</filename>
              </rom>
            </ROM>

            <ROM id="ROM1">
              <mem base="0x8000" size="0x2000"/>
              <rom>
                <filename>roms/rom1.rom</filename>
              </rom>
            </ROM>

            <ROM id="ROM2">
              <mem base="0xC000" size="0x4000"/>
              <rom>
                <filename>roms/rom2.rom</filename>
              </rom>
            </ROM>
           </secondary>
      </primary>
    </msxconfig>

    So if I fill in a specific empty slot for 'any' the roms are all put in that one slot. With the above config they split in 4 different slots/sub slots which I don't want.

    Can I somehow tell openMSX to use one slot but still just select any free slot available in that machine?

    Thanks for your help.
    Cheers, Marcel.

     
    • Sorry, it's a limitation (or call it bug) in current openMSX versions.
      The extensions mechanism is currently being reworked, for example to allow inserting and removing extensions in a running openMSX session. I'll try to make sure that this limitation you discovered also goes away.

      Thanks for reporting it.

      Wouter