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.

Sign up for GitHub

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

Jump to bottom

Feature Request: Allocate the null terminal \0 after "MOS" @ $40 for versioning. #111

Open
jackokring opened this issue Nov 5, 2023 · 1 comment
Open

Feature Request: Allocate the null terminal \0 after "MOS" @ $40 for versioning. #111

jackokring opened this issue Nov 5, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@jackokring
Copy link

The current screen mode number changes. What would happen to current development if the zero had to be a one to stop the MOS from issuing a vdu command to enable compatibility modes before exec16 or exec24 are called? It would allow older but not updated things to run. It wouldn't solve the using an older basic and do .bas files have the basic version number saved with in?
@jackokring
Copy link
Author

Of course just emitting the byte in VDU 23, 0, &C1, n might work, as it currently has a b>=0 test with b equal to n in the VDP source. Maybe aturning it into a generic compatibility versioning call.

@breakintoprogram breakintoprogram added the enhancement New feature or request label Nov 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
AGON Quark Firmware
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jackokring @breakintoprogram