Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is similar to the VIC44 mode but takes it much further. The VIC44 mode simply doubles the pixel output rate, and modifies the ROM code so that BASIC has a 44 column text window. The VIC44K mode extends on that to move the base address of various components around to create a continuous 44K of RAM available to BASIC. The end result is that it boots up into BASIC saying that it has 45055 bytes free, i.e. 44K.
This is very much not compatible with the original VIC 20, but a home brew project might adapt a VIC 20 motherboard to work in this way, using the same custom ROM code that this new mode uses.