|
Problem with MAME media types for systems with peripherals
#384476 - 11/29/19 11:17 PM
|
|
|
So I have what i believe is a bug in how systems are handled in MAME (possibly). My current focus is with the ZX Spectrum, however I have seen the same behavior with some other systems.
The problem comes about due to the media types (-listmedia) reported with the base system. In the case of the ZX Spectrum, these are as follows (These work just fine);
snapshot (dump)
quickload (quick)
cassette (cass)
Now, when I add a peripheral slot device that contains a floppy disk into the systems INI file (See below);
exp disciple
exp:disciple:fdc:1 35dd
exp:disciple:fdc:0 35dd
Then run the mame64 spectrum -listmedia, it reports the following;
SYSTEM MEDIA NAME (brief) IMAGE FILE EXTENSIONS SUPPORTED
---------------- --------------------------- -------------------------------
spectrum floppydisk1 (flop1) .mgt .dsk .d77 .d88 .1dd .dfi .hfe .imd .ipf .mfi .mfm .td0 .cqm .cqi
floppydisk2 (flop2) .mgt .dsk .d77 .d88 .1dd .dfi .hfe .imd .ipf .mfi .mfm .td0 .cqm .cqi
printout (prin) .prn
snapshot (dump) .ach .frz .plusd.prg .sem .sit .sna .snp .snx .sp .z80 .zx
quickload (quik) .raw .scr
cassette (cass) .wav .tzx .tap .blk
You can see that floppydisk1 (flop1) and floppydisk2 (flop2) have been added to the list of available media types. All makes sense so far. And if you run MAME and select a floppy disk image through MAMEs own interface, everything works as expected.
The problem arises however when you try to run the same flopp disk image using the MAME command line as follows;
C:\Temp\mame>mame64.exe spectrum -flop1 D:\Mameui64\roms\spectrum_cass\disciple.mgt
Error: unknown option: -flop1
You can see that even though the flop1 media type exists, MAME doesn't accept it. It seems as if when invoking the MAME command line like this, MAME is not taking into account the additional media types added via the settings in the spectrum.ini file. I know that INI file is correct as it works fine under the MAME gui itself.
Can anyone provide some knowledgeable advice on what's happening here and if indeed it is a bug?
Cheers.
|
|
|
|
Re: Problem with MAME media types for systems with peripherals
[Re: Gfinch]
#384478 - 11/30/19 12:32 AM
|
|
|
Sounds like INI parsing is taking effect after commandline parsing. I'm not sure if that's desired behavior.
If you used...
mame64 spectrum -exp disciple -exp:disciple:fdc:1 35dd -flop1 D:\Mameui64\roms\spectrum_cass\disciple.mgt
That probably would work. I don't have the necessary stuff to test it right now, though.
That said, I'll bring it up with MAMEdev and see what they have to say. Does Vas or anyone else want to comment here?
|
---
Try checking the MAME manual at http://docs.mamedev.org
|
|
|
Re: Problem with MAME media types for systems with peripherals
[Re: Firehawke]
#384482 - 11/30/19 02:01 AM
|
|
|
Yes you are correct, that does work. Not what I need though as I have a front end where I can set program specific INI file settings for different programs to take advantage if peripherals that they require.
I agree I believe its the INI parsing that's happening too late, however I've not been able to determine that 100% as the cause.
|
|
|
|
Re: Problem with MAME media types for systems with peripherals
[Re: Gfinch]
#384483 - 11/30/19 02:12 AM
|
|
|
|
|
|
Re: Problem with MAME media types for systems with peripherals
[Re: Robbbert]
#384485 - 11/30/19 02:31 AM
|
|
|
Yes that unfortunately doesn't help what I'm trying to do. The idea is to not have to invoke the MAME built in GUI to run the program.
It may be that its intended behavior, however if it is it seems odd given that it works fine with the base level media types. Just that the INI file isn't being parsed at the right point in time (I'm assuming).
|
|
|
Index 
Threaded 
Problem with MAME media types for systems with peripherals
Reply
[Re: 
