Opry99er Posted October 31, 2010 Share Posted October 31, 2010 (edited) So, I know we've talked about this at one point, but I can't seem to find the thread. How much space is available for machine code when in the XB environment? If I remember correctly, it's something like 8k. Much of the low memory available on the /4a gets devoured by the XB architecture--- This is what Matthew went through while building his sound player--- I have re-read his journal entry about the development and have some questions... So Matthew, if you're reading, here's my idea, perhaps you can help. I want to load 4 704 byte maps into low memory at a time along with the sound player and a soundlist. Each screen map is 704 bytes, since two full rows are used for stats and will not be re-drawn. The goal: take a SPRITE across the screen, when the SPRITE reaches the edge, call an assembly routine to draw the "next" screen. I will not need to have 4 in memory for every circumstance, but 4 is the most I will need at any time. I'll diagram my requirements later... In the meantime, I'll continue doing research and if you guys can give me an idea about space limitations beyond what Matthew cited in his XB sound player notes, I'd be appreciative!! Edited November 29, 2010 by Opry99er Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.