The stack on the 8085 grows down from high memory, towards your files. I think it can fill all unreserved RAM, and then some (if you're not careful). Given that it is critical for interrupt handling it is very well protected by the ROM.
So, safe as houses (while your .CO is running). Basically, you would save SP, subtract 2K from SP and store the new value in a variable (I could be off by one byte... does it point to the next byte to write or the byte already written?). I'd say throwing your data on the stack should be the default way for a dynamic allocation that doesn't need to outlast your program. Now, if you want it to be protected after your program exits, or you want the speed of a fixed block of RAM instead of indirect access through a pointer, then you have to look to other solutions. If you want fixed space (like config), you could just access memory built into the space you CLEAR for your .CO program to run. -- John.
