Ullrich von Bassewitz wrote: > On Mon, Sep 21, 2009 at 05:14:42PM +0300, Karri Kaksonen wrote: > >> The cart-based code is more difficult as I want to set the RAM segment >> starting from the top of memory and growing downwards. Is there a way to >> do this? >> > I'm not sure what all that means. Is this config usable without any library > changes? What does "cart-base code" mean for a RAM only configuration? > I checked the current lynx.cfg and that is usable as it is. So forget about the cfg file I sent you. The cart build cfg-file contains building the directory. In order to make cart work I need to add a new SYMBOL __BLOCKSIZE__=1024 , 2048 or 512 depending on how the chip is soldered on the target board. I also need to discard the EXEHEADER as it is replaced by the CARTHDR segment. So instead of 8 bytes at startup I need to add a 64 byte description for emulators, a 410 byte encrypted loader, a filesystem built by the linker and macros. I also need a new segment for the mandatory title-sprite TITLE that can be linked in to the directory. I was hoping to leave the area between $0400 - $9800 for user programs that can be loaded and run from the cart. In the default cart template I might include a segment GAME for this to work. Or perhaps it is best to just forget about a "simple" cart config file. Such a thing does not exist. -- Karri ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Sep 24 18:45:46 2009
This archive was generated by hypermail 2.1.8 : 2009-09-24 18:45:49 CEST