Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Hell's Temple" compatibility issues (Oric-1/Atmos) #134

Closed
rzumer opened this issue Feb 20, 2019 · 6 comments
Closed

"Hell's Temple" compatibility issues (Oric-1/Atmos) #134

rzumer opened this issue Feb 20, 2019 · 6 comments

Comments

@rzumer
Copy link
Contributor

rzumer commented Feb 20, 2019

I noticed text corruption when running in Oric-1 mode in the title "Hell's Temple". With the serial modem enabled, just bumping into the wall at the start repeatedly will cause that to happen. Eventually the player's status is completely unreadable and I wouldn't be surprised if it caused crashes, but I have not gotten far enough to check.
image

It persists after being booted out by the game (following a game over).
image

After disabling the serial modem the display is fine, but the same issue occurs regardless of that setting when loading from a save file. Sample save tape below: enter the name "EUCLIDE" and insert on load. Note that this sample was generated on Atmos rather than Oric-1 and it is the only one I have, so I have no idea if it is caused by the difference in models used to write and read the tape.
euclide.zip

This title targets Oric-1, but when running on Atmos it seems to work correctly until trying to load from a save, which crashes to the debugger.

With Atmos (perhaps Oric-1 as well) I have heard secondhand that status text gets garbled under certain conditions as well, possibly involving combat. The same person who reported these issues to me also noted that after a certain amount of turns/time, the game crashes internally with a stack overflow (no crash to debugger as far as I know), and this has been reproduced on both models.

I have not yet compared these results with other emulators.

@rzumer rzumer changed the title Display corruption when enabling the serial modem with Oric-1 Display corruption with Oric-1 (under various conditions) Feb 20, 2019
@rzumer rzumer changed the title Display corruption with Oric-1 (under various conditions) "Hell's Temple" compatibility issues (Oric-1/Atmos) Feb 21, 2019
@assinie
Copy link
Collaborator

assinie commented Apr 9, 2019

I tried with Euphoric in Oric-1mode and have the same result, so it's not an issue with Oricutron but a bug in the software (or the Oric-1 ROM).

@rzumer
Copy link
Contributor Author

rzumer commented Apr 9, 2019

Thank you for checking. Have you considered the possibility of it being a shared bug between Euphoric and Oricutron?

@assinie
Copy link
Collaborator

assinie commented Apr 9, 2019

I think the probability of a bug common to Euphoric and Oricutron is very low because these 2 emulators have no source files in common (as far as I know).

@assinie
Copy link
Collaborator

assinie commented Apr 9, 2019

I looked at the program and it looks like it's for an Oric-1 and not for an Atmos because there are calls to ROM v1.0 routines for reading the backup file.
If started in Atmos mode, everything will work properly except reading the backup file (because of the calls to ROM v1.0 routines).

So I think it's something related to the initialization of the ROM v1.0 and the variables management.
When you start in Oric-1 mode, some memory pointers are "incorrect", HIMEM is set to $9F00.
If you do HIMEM #9800 before the CLOAD "", then you can WALK INTO A WALL without corrupting the character set 😃
(#9800 is the default value in Atmos mode).

@rzumer
Copy link
Contributor Author

rzumer commented Apr 9, 2019

Very nice, thanks for the information and the workaround.

@iss000 iss000 closed this as completed Feb 16, 2021
@iss000
Copy link
Collaborator

iss000 commented Feb 16, 2021

closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants