So, in principle, SAVEOBJ4 can save any code file, of any start, any length and any page?
As I understood you should write something like this:
If I have a source file and want to assmble a "file 1" it into page 7, I do assmble, and then want to save the "file 1" machine code on the disk. Could you write me, what steps should I follow?
so, you can call saveMyCode after compilation. ( Note: The code above is a "pseudo" code, it demonstrates only idea ). As we saw main idea of that proc - easiest way to save multiple compiled files. The data in the structer is just to create file on file system.
; saving code here --------------
; the code ----------------------
code_start equ 0xc000
code_page equ 7
org code_start, code_page
; some code
ld a, a
; end of code
code_len equ $ - code_start
; table -------------------------
db "file 1 " ; 9 bytes
db 0 ; end of table
I'm not sure if it neccesary, it seems that it can be compiled from disk.
Do I have to keep the source code of "file 1" in the memory all the time? Do I have to keep a source code of "SAVEOBJ4" in the memory all the time?
There's a command in main.. hmmm... menu ( when cursor 'A' ) ( 'P' - key ) it types PAGE so you can enter page number. After that the page becomes 'current'. If it empty new file will be created.
Maybe a stupid question, but how can I load more sources into alasm? If I load them, they keep loading in page 6, and they are overwritten. How to solve it?