Thanks for the info. Yeah, seems redundant (also mistaken the C register) and should be safe to remove it. Anyway, congratulations for the game, it's impressive. Any plans on extending it? You could add lots of other data blocks (speech, videos etc) to the tap file
looking at that code, I don't see any use of the C register before calling the rom load routine (and you would also need a push/pop probably). C register on return from the rom load call is undefined (usually value 01, 0x21 and others) but it doesn't tell anything relevant (I think it's the last value sent to the port feh to draw the border stripes). So I think that's a bug in your code ;) Some emulators like Fuse return C=01, others like mine (ZEsarUX) didn't return anything on C register, so the game was failing and that's the reason I started debugging it, hehehe. Now I'm returning C=01 and yours is the only game that failed loading (of course this is the "fast load" tape method, if I do a "slow" load (realtime) it was working. I assume your game doesn't load on other emulators either
Please see the full screenshot. The first JR NC is not relevant (it was in red due to a breakpoint I put on my ZEsarUX emulator). See the LD A,C just some opcodes below that ;)
Bug report... on your loading routine, after checking the header of a tape block, you expect register C to be different than 0, why? The return of C register on the loading routine is not a documented behavior (can have different values 0x01, 0x21, 0xFE, 0xDE...)
Hi there! I'm the author of ZEsarUX emulator. I'm trying to run Actic Atac in ZEsarUX and I have some questions about the disk_filemap call the game is using. It now detects the card is not fragmented, reads some bytes from the card (up to offset 2227FH) and then it resets. Can I contact you by email ? My email is chernandezba at hotmail dot com. Thanks!
Hi. The Spectrum version (not Next version) says the game runs better at 7 Mhz turbo mode. Does the game use some i/o port to set 7 Mhz mode? I want to emulate that port in ZEsarUX. Thanks!
on your loading routine, after checking the header of a tape block, you expect register C to be different than 0, why? The return of C register on the loading routine is not a documented behavior (can have different values 0x01, 0x21, 0xFE, 0xDE...)