Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
09529 Documentation Trivial Always 26 days ago 1 day ago
Tester VasiliyFamiliya View Status Public Platform MAME (Official Binary)
Assigned To Kale Resolution Fixed OS Windows (x64)
Status [?] Resolved Driver
Version 0.289 Fixed in Version 0.290GIT Build x64
Fixed in Git Commit adafe47 Github Pull Request #
Summary 09529: pc8801mk2sr, pc8801ma [finalcri, finalcria]: Unclear QA notes
Description On MA, space key is able to make music to fade out on the disk B asking screen and crash the game after being held during music fading out at titlescreen, absolutely as on MkIISR and MC.
On MkIISR, I didn't found any syntax error bug.

In the case of parental set, I think sound stuck bug on MkIISR can be considered as verified.
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version
Affected Sets / Systems pc8801mk2sr, pc8801ma [finalcri, finalcria]
Attached Files
png file icon Debug phase 1.png (62,571 bytes) 1 day ago Uploaded by VasiliyFamiliya
VasiliyFamiliya
png file icon Debug phase 2.png (57,715 bytes) 1 day ago Uploaded by VasiliyFamiliya
VasiliyFamiliya
Relationships
There are no relationship linked to this issue.
Notes
4
User avatar
No.24656
Kale
Developer
13 days ago
Pretty irrelevant out of crashing regardless of the model, but I'll play along ...
User avatar
No.24657
Kale
Developer
13 days ago
Also, I need a real HW reference for (verify) type notes. Without it I won't take that word for good.
User avatar
No.24682
VasiliyFamiliya
Tester
1 day ago
Some info about the program crash occuring if to hold any key at the title screen until BGM fade out and first keyboard status check.

1. Screen garbaging happens because of RAM ($38~84fd) infinitive fill by same ($0039) value - see "Debug phase 1" screenshot.
2. This fill is caused by recoursive RST $38 call - see "Debug phase 2".
3. Just a little eloquent end of my trace log:

C601: xor a
C602: ld ($8A0F),a
C605: call $855A
855A: db $fd
855D: ld bc,$C5FC
8560: nop
8561: ld (bc),a
8562: inc l
8563: ld (bc),a
8564: jp $348D
348D: ret p
C608: ld a,($8A15)
C60B: or $01
C60D: ld ($8A15),a
C610: out ($E6),a
C612: call $C41C
C41C: ld h,b
C41D: call nz,$4FCB
4FCB~77FF: nop
7800: rst $38
0038: rst $38
0038: rst $38

Maybe, some data for $4fcb+ failed to be loaded from disk(s)?
User avatar
No.24683
VasiliyFamiliya
Tester
1 day ago
We have analogical RAM flood by $0039 also if we don't even touch a keys at titlescreen during the launch with disks A and B in according drives, or, in case of launch with disk A only, after disk B insert to drive 2 when game will ask for it and confirmation with space key.