Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
07053 Crash/Freeze Critical (emulation) Always Jul 25, 2018, 12:16 Jul 25, 2018, 20:11
Tester Robbbert View Status Public Platform MAME (Self-compiled)
Assigned To AJR Resolution Fixed OS Windows Vista/7/8 (64-bit)
Status [?] Resolved Driver
Version 0.200 Fixed in Version 0.201 Build 32-bit
Fixed in Git Commit Github Pull Request #
Summary MESS-specific 07053: osbexec: Stuck on PERFORMING SELF TEST
Description Machine will not go beyond self test
Steps To Reproduce
Additional Information Although machine is marked as not working, this is a regression.
Github Commit
Flags
Regression Version 0.192
Affected Sets / Systems osbexec
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.15291
Tafoid
Administrator
Jul 25, 2018, 13:07
Specifically, changes to the z80sio has caused this, but where other failing sets were resolved rather quickly (ccs300, jgz80, uts20), this one fell through the cracks and was not reported here when the next release happened.

https://github.com/mamedev/mame/commit/6407707ccc3445af120e5f7429392d4d344321e9
https://github.com/mamedev/mame/commit/711d7b490e48b4dd4bbaae46cbde6b8f87788be1
https://github.com/mamedev/mame/commit/3166f52c3fa865449879e08f8c62b832babb2ac0
User avatar
No.15292
AJR
Developer
Jul 25, 2018, 20:11
This was really my mistake for not having originally understood how MAME's RS232 emulation worked. I thought that inversions were necessary since the 1488/1489 line drivers and receivers are technically inverters, but MAME uses the logical levels rather than the signal levels.