07001: specpls3: Can't load floppy images in specpls3

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07001	Media Support	Critical (emulation)	Always	Jun 4, 2018, 19:44	Jun 6, 2018, 18:48

Tester	StHiryu	View Status	Public	Platform	MAME (Unofficial Binary)
Assigned To		Resolution	Open	OS	Windows Vista/7/8 (64-bit)
Status [?]	Confirmed			Driver	sinclair/specpls3.cpp
Version	0.198	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07001: specpls3: Can't load floppy images in specpls3
Description	In this new mame release maybe some things have changed related to floppy emulation. Loading disk images in spectrum gives error, or the system doesn't recognize the image. This is a regression since the last 0.197 worked fine.
Steps To Reproduce	In Spectrum, just hit the loader option from the menu.
Additional Information
Github Commit

Flags
Regression Version	0.198
Affected Sets / Systems	specpls3

Attached Files

No.15092 Tafoid Administrator Jun 5, 2018, 02:03	I tried it and it worked for a game from the software list "gauntlet" Is there a specific software or configuration that you are not mentioning?
No.15097 B2K24 Senior Tester Jun 5, 2018, 17:18	This can be reproduced using Outrun - Side A.dsk and Outrun - Side B.dsk from worldofspectrum. Current release ignores that disks are inserted and instead asks for play to get pressed when a tape is inserted.
No.15099 StHiryu Tester Jun 5, 2018, 22:12	Other games that fails to load are (from WoS): Astro Marine Corps.dsk Comando Tracer.dsk Golden Axe (MCM) - Side 1.dsk
No.15104 StHiryu Tester Jun 6, 2018, 18:48	Strange Bug...I've been digging on it and really, the system can load a floppy image. For example the game Gauntlet, or one game from my list above (in summary, a disk that works). The problem is when you load a floppy like OutRun. That game fails to load and resets the machine, so at this point, if you try to load a different disk, is likely the system gets stuck and can't detect any floppy again. The only way I've found to exit from this situation, is to delete the .ini file at the ini folder.