Hi all
As people seem to think you can only have your code run at address &8000(32768)
here how the loader works (I hope people can understand it!). Questions I have
had have mainly about the loader
How the loader works
When using the default saving of Object file, Jam Assembler only saves what it
needs to i.e. does not save big DEFS space or space the DUMP command has made.
This is so you can have code and MDATA's in many different pages stored on one
file and not super big file.
The format is:
Header
Address of code (2 bytes)
Length in byte (2 bytes)
Page of code (1 byte (0-31))
Code
the code data of the above length
After the code there will be another header then code etc. etc. until the end
of the file.
Sam's loader
On the SAM Coupe's side when the disk image is booted auto file runs from line
10 (not line 1). the loader program is loaded at 32527 and uses the rest of
that page so you can't use 32527-32767 for your own code or extra basic code.
It only loads the file as it needs it so loads the header first then the data
and puts it in the right pages. So the object file on the disk says it starts
at 32768 but it's never loaded there.
After it booted you can run the basic which just calls 32768 or just type CALL
??????
I will upload a new version soon which will include an input call address
statement on the SAM side of things.
Hope this helps people. If not just ask!!!
All the best
David
P.S. The name has come from merging SAM and Java (well sort of!)
On 1 Feb 2012, at 09:05, Andrew Gillen wrote:
> Hi David,
>
> I have used JAM and found it to be an excellent environment. Much of the
> original code I wrote for Dave was developed using it but I found the
> default build to address $8000 a limitation, so I ended up with a
> context/pasmo setup where I could do what I wanted and build to any address.
>
> Cheers
> Andrew
>
>
>
> On 1 Feb 2012, at 07:59, david brant <davidcbr...@yahoo.com> wrote:
>
>> People do use it then, not had much in the way of feedback.
>>
>> Jam Assembler does not doing anything special with the font or anything like
>> that. It would be using Windows API for fonts and messages etc. i.e.
>> anything standard windows stuff.
>>
>> Jam Assembler not been tested on anything newer than XP though.
>>
>> What version of Java is your computer using? Have you tried re loading Jam
>> Assembler? I have a newer version on my computer which sorts out some
>> project view issues and does method inheritance I'll upload it tonight with
>> a bit of luck.
>>
>> Otherwise can you send me a screen shot please.
>>
>> On 1 Feb 2012, at 01:19, Balor Price wrote:
>>
>>>
>>>
>>> So, hmmm... while I'm fired up...
>>>
>>> Anyone having problems with the GUI in Jam Assembler? It's been a while
>>> since I tinkered, but now I'm getting gobbledygook instead of English in
>>> the dropdown menus and dialogue boxes... At a guess I'd say the font
>>> lookups had gone askew, it's a JAR file that's executed so it's not relying
>>> on Windows API calls or anything. David?
>>>
>>> Howard
>>
