Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07728 Crash/Freeze Critical (emulation) Always Aug 14, 2020, 17:17 Aug 19, 2020, 20:14
Tester rcoltrane View Status Public Platform MAME (Official Binary)
Assigned To Resolution No change required OS Windows 10 (64-bit)
Status [?] Closed Driver
Version 0.222 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary MESS-specific 07728: apple2p: Crash trying to run the game mounted as floppy disk
Description It seems that the Apple II Plus machine is not mounting the game in the floppy disk drive properly. It gives me an error saying: "Device 5.25" single density floppy drive load (-floppydisk1 sabotage) failed: file not found.
Steps To Reproduce Mount the game in floppy1 and try to run the game.
Additional Information It's a regression. It was working in MAME version 0.218 before my update to version 0.222.
Github Commit
Regression Version 0.218
Affected Sets / Systems apple2p
Attached Files
jpg file icon apple2perror.jpg (134,317 bytes) Aug 17, 2020, 14:13 Uploaded by rcoltrane
There are no relationship linked to this issue.
User avatar
Aug 14, 2020, 20:01
Can you make sure you don't have any apple2p.cfg or .ini files that might be causing your issues?
Are you positive that your software is located in the same place as your MAME 0.218 install and MAME 0.222 install knows this? If rompaths are not properly set you could have software not loading when requested. Does it happen with other software loaded by apple2p?
User avatar
Aug 15, 2020, 18:12
I cannot duplicate your issue with this software list title. I've tried loading from command-line and also via UI "File Manager" menus and both times upon reset they booted/played as expected.
User avatar
Aug 16, 2020, 15:32
Deleted both .ini and .cfg files and nothing changed. My settings are iddentical to the ones I was using in version 0.218 and I still cannot run the game, it gives the same error message reported here. Updated to MAME 0.223 with no luck. Here's my command line, see if I'm doing something wrong please:

-bgfx_backend opengl -bgfx_screen_chains -bgfx_shadow_mask -noreadconfig -nowriteconfig -nofilter -pause_brightness 1.00000000 -ui_active -nonvram_save -skip_gameinfo -noui_mouse -hashpath "C:\RCS\Games\UME\hash" -inipath "C:\RCS\Games\UME\ini" -rompath "C:\RCS\GAMES\UME\roms\APPLE2P" -samplepath "C:\RCS\Games\UME\samples" -record apple2p.inp -nosnapbilinear -nounevenstretch -video d3d -output console apple2p -flop1 sabotage.dsk

Here's my ROMpath: \roms\APPLE2P\sabotage.dsk
User avatar
Aug 17, 2020, 14:16
Did another test with a fresh mame 0.223 installation and putting all apple2p roms in the \roms default directory. It gave the very same error as before, so it's definitely a new bug of some kind. See at the new picture attached here that I'm not using any fancy command, just the very basic commandline to run the game.
User avatar
Aug 17, 2020, 16:03
Are you using a front-end?
Can you run MAME and use the TAB menu -> File Manager to mount that image and use it?
User avatar
Aug 17, 2020, 17:11
edited on: Aug 17, 2020, 17:15
FWIW it works fine here with: mame64 apple2p -flop1 sabotage
But I believe this could possibly cause the change in behaviour for your use case:

EDIT: if I use -norc to tell MAME not to use the ini file, I need the following for it to run without the problem you encounter: mame64 apple2p -flop1 sabotage -norc -rompath "d:\emu\mame\software;d:\emu\mame\roms"
User avatar
Aug 19, 2020, 19:52
edited on: Aug 19, 2020, 19:53
Thanks to OSSO I did a successful test running Sabotage. But I had to force the path to the game file via command line, like this:

C:\Temp\z>mame64 apple2p -flop1 roms\APPLE2P\sabotage.dsk

I don't know why they changed the way the system looks for a disk file, completely ignoring the roms path set in the .ini file. This makes systems less user friendly IMO.
User avatar
Aug 19, 2020, 20:14
Actually, rompath is only used for softlist setups. Your method of loading is very "picker style" in that you can load anything you want so long as the media and path to it is correctly entered. Softlists work like loading regular MAME roms, and expects those images in certain places (As defined by rompaths). Like normal loaded romsets, software images loaded via softlists should also be its own folder or compressed folder.

Let's take your sabotage example

c:\mame\roms - romsets
c:\mame\software - main folder for software from lists

rompath roms;software

Places it will look for softlist title and can be run simply typing: mame64 apple2p sabotage


This is a change that cannot be reversed so this isn't really a bug. CHD's used to just placed loose in a ROMS folder and work but in doing that it complicated many other things so this type of loose placing (which what your config was) is no longer supported.