Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#227 Fast!DiskROM

open
nobody
5
2011-07-15
2011-07-15
SD Snatcher
No

Please add the device Fast!DiskROM to openMSX. The configuration file is attached.

Discussion

  • SD Snatcher
    SD Snatcher
    2011-07-15

    Fast!DiskROM-CDX2.zip

     
    Attachments
  • Just one question: in the past you sent me a config like this:

    <msxconfig>
    <info>
    <name>FAST!DiskROM for DDX-3.0 disk interfaces</name>
    <manufacturer>A &amp; L Software</manufacturer>
    <code>FAST!DiskROM</code>
    <release_year>2006</release_year>
    <description>Double Sided Double Density port-based external floppy disk drive.</description>
    <type>external disk drive</type>
    </info>
    <devices>
    <primary slot="any">
    <secondary slot="any">
    <Microsol id="DDX_3.0">
    <io base="0xD0" num="5"/>
    <broken_fdc_read>false</broken_fdc_read>
    <drives>1</drives>
    <mem base="0x4000" size="0x4000"/>
    <rom>
    <filename>roms/fastdrom_ddx3.0.rom</filename>
    <sha1>f2da984b2076a00d7359df4803fccdc0552b0e5d</sha1>
    </rom>
    </Microsol>
    </secondary>
    </primary>
    </devices>
    </msxconfig>

    It has a different name and has a different sha1sum. Now, which one to add? And why is the sha1sum different anyway?

     
  • Another issue: in openMSX, when starting up with this extension, I see "0 drives" reported (both physical and logical). And when inserting a disk, it keeps saying "Disk offline". However, when starting up with a disk inserted, drives are detected and everything runs fine. Is this normal?

     
  • SD Snatcher
    SD Snatcher
    2011-07-16

    > It has a different name and has a different sha1sum. Now, which one to
    > add? And why is the sha1sum different anyway?

    Those are two versions, one for the CDX2 interface and other for the DDX-3.0 interface.

    The difference is that the DDX-3.0 is a more advanced interface, and supports both I/O through ports and memory. It's BIOS always uses the memory I/O, so more than one interface can be connected to the same MSX.

    I'm not sure if openMSX already supports the DDX-3.0 interface, this is why I sent the CDX2 Fast!DiskROM too. It's up to you to choose each one will be available. The CDX2 is certainly the easiest one.

    About the "0 drives" problem, it seems to be a bug on openMSX FDC emulation. On real hardware that doesn't happen and the drives are correctly detected regardless of a presence of a floppydisk inside.