Tested against the ZetaWing II d64 image. After going through it with the logic analyzer I could see that when loading the M1 file the Commodore was aborting after byte 619 and causing the EOI ack failure at byte 620. The game seems to know how many bytes it wants for some files and just quits after getting them all instead of waiting for EOI to be signalled.
Checked image against ninepin and worked fine there. Looked at the actual file length of M1 on the d64 image and it really is only 619 bytes. Looked at how ninepin calculates file length and it was nearly identical except for the - 1. Added - 1 and now zetawing plays fine with disk image on the SD card.
Tested against the ZetaWing II d64 image. After going through it with the logic analyzer I could see that when loading the M1 file the Commodore was aborting after byte 619 and causing the EOI ack failure at byte 620. The game seems to know how many bytes it wants for some files and just quits after getting them all instead of waiting for EOI to be signalled.
Checked image against ninepin and worked fine there. Looked at the actual file length of M1 on the d64 image and it really is only 619 bytes. Looked at how ninepin calculates file length and it was nearly identical except for the
- 1. Added- 1and now zetawing plays fine with disk image on the SD card.