06351: sol20, mz700 (and probably others): Crashes after mounting a file

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
06351	Crash/Freeze	Critical (emulation)	Always	Aug 19, 2016, 13:39	Aug 21, 2016, 18:36

Tester	demotester	View Status	Public	Platform	MESS (Unofficial Binary)
Assigned To		Resolution	Suspended	OS	Windows XP
Status [?]	Closed			Driver
Version	0.176	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	06351: sol20, mz700 (and probably others): Crashes after mounting a file
Description	The last "unofficial" MESSUI from 2016-08-15 crashes just after mounting a file on my WinXPSP3 ! Does that announcing that WinXP will not be anymore supported in MAME/MESS ?
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	sol20, mz700 (and probably others)

Attached Files

No.13057 Tafoid Administrator Aug 19, 2016, 15:44	This is a tracker, at least at this time, for Integer releases of MAME ONLY Bleeding edge binaries, Daily builds or anything else are not valid for reporting here. That said, this is not your fault and isn't some anti-XP trickery. There are regressions with file loading and softlists which are being handled as soon as possible and covering most systems. Just keep an eye out via GIT about issues and regressions being resolved before release (which is scheduled for August 31). I highly suggest you keep to 0.176 until 0.177 released. If you encounter issues with bleeding edge/non supported binaries, post to one of many forums (mameworld.info, bannister.org, mamedev.org, etc) and I'm sure a developer will see it. I've suspended this one until 0.177 and will delete if the issue has been taken care of at that time.
No.13062 Tafoid Administrator Aug 21, 2016, 18:36	This has been fixed in local GIT and should not appear in 0.177 release. Upon 0.177, this will be deleted.

No.13057

Tafoid

Administrator

Aug 19, 2016, 15:44

This is a tracker, at least at this time, for Integer releases of MAME ONLY Bleeding edge binaries, Daily builds or anything else are not valid for reporting here.
That said, this is not your fault and isn't some anti-XP trickery. There are regressions with file loading and softlists which are being handled as soon as possible and covering most systems. Just keep an eye out via GIT about issues and regressions being resolved before release (which is scheduled for August 31). I highly suggest you keep to 0.176 until 0.177 released.

If you encounter issues with bleeding edge/non supported binaries, post to one of many forums (mameworld.info, bannister.org, mamedev.org, etc) and I'm sure a developer will see it.
I've suspended this one until 0.177 and will delete if the issue has been taken care of at that time.

No.13062

Tafoid

Administrator

Aug 21, 2016, 18:36

This has been fixed in local GIT and should not appear in 0.177 release.
Upon 0.177, this will be deleted.