Previous | Next
| From: TLC (all posts)
Date: 1998-06-10
Subject: Re: CLINK!
|
Hi!
> This is to LEVENTE, but may concern some more...
Yep? Who is that LEV....
> Levenete: I would like to see .N64 support in the CLINK program.
Whew, your 'e' key contains a built in rapper inside :-/
About .n64, well, I might be persuaded. As you may have known, I'm planning to release the new version of that stuff this summer. BTW, have you succeed the modification of the serial receiver routine to the userport?
> Unfortuately I am pascal beginner to be able to improve your code.
> N64 is a file generated by the Taboo xassembler, it is for multi
> parted code. (I had to reedit a lotsa code coz the missing n64
> support last weekend :(
O.K.
On 'multi parting', I suppose you mean that it assembles the code into more continuous blocks and stores this whole bunch into a single file.
Using TASM301 and hexadecimal object file does also mean that your compiled code is organized into blocks instead of one continuous dump.
This is true, and in theory it may be equal with the .n64 as long as .n64
doesn't support wider address space (like support of extended memory). Well,
I must check their page or the location you mentioned.
> The format is something like:
> (word)legth of the next block
> (word)start addy
> (bytes)data
> (word)length of the next block
> (word)start addy
> (bytes)data
> Exactly described in ftp://c64.rulez.org/pub/c64/Tools/MSDOS/xasm.zip.
> Please note that this is NOT the latest version, I will update that
> as soon as I can reach the Taboo page.
Well, using object formats is easier, since they are ASCII and not binary files. But O.K., this format also should take place in the next version of ComLink.
(Or, you can write a n64 2 Intel obj format converter routine :-). It seems (at least, from your description of the file) that it's possible anyway, without any loss of the information covered by the file.)
Levente
|
| |
Copyright © Plus/4 World Team, 2001-2024 |
