Цитата Сообщение от Antipod Посмотреть сообщение
It seems that you are going to port alasm to your favorite OS ...
Ok, about subj, though I'm not alasm user... It seems that function 'nenado' saves all compiled code to tr-dos disk. The code should be described in array of structures and the array should be located at global label 'ObjTab'. Fields of the structure is commented in source ( as we can see it contains: filename ( 9 bytes ) , start adr at memory, length and file lenght[which can be used as last 2 letters of file name extension ] ).
So, you can use that function to save all your code, all you need as to fill the table and make call to 'nenado'.
There's also some strange hardcoded call to 8026...
Another words, you can write your own function that can do same thing
Good luck

...yees, exactly, we shall see how I succeed this time, the structure of alasm is for me "a university" in coding)

Yes, I saw that table in the begining of SAVEOBJ4 code.

So, in principle, SAVEOBJ4 can save any code file, of any start, any length and any page?

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? 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?


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?

Thanks


Hood