Previous | Next
| From: TLC (all posts)
Date: 1998-06-11
Subject: Re: CLINK!
|
Hi!
> Levente? I think you misunderstood most of my letter, that is not
> an ASCII file, but binary! Contains the datas in the order I wrote.
> Implementing it in CLink wouldn't be a hard work, even you don't have
> to change _anything_ in the receivers, they will thing the parts of
> the n64 files are just some new files, or new data streams...
Well, I guess I should have been brighter. As I re-read my post, I thing my info was a bit incompleted. Sorry.
What I meant, there IS something similar like you mentioned (the n64 file)
already implemented into ComLink. It is the Intel Hex object file format.
Well, this is an ASCII file in its look, but it covers quite the same abilities as your n64 file does.
In other words, it may be fully possible to write a 100% n64 to Intel hex file converter ('cos the files are 100% equivalent in their information content).
Also, implementing its support into ComLink wouldn't be more than a few hours of coding and testing all in all (writing the appropriate loader and interface it to the stuff's core). Not a hot shot. I'm also planning to support the missing Motorola format object, it's quite the same easy to do because of the structure of the program.
Anyway, if you're interested in writing a quick hack-type n64 to Intel hex converter instead, the detailed description of the Intel Hex format is in the doc of TASM301.
> I didn't make the user port thing yet, but will do it soon, coz last
> time I coded a file to another file converter, and it was a pain in
> ass to test :)
Yikes :-) Whew, I seem to leave this 'pain in the ass' style for a while
'cos I finished my master's thesis (with typing some 60K of text :-( ) so now I concentrate more on the beach. ...Bitch. -es. Whoever knows eh...
%-) I got blind a bit by this pretty Windoze screen which I've been looking at last weeks.
Levente
|
| |
Copyright © Plus/4 World Team, 2001-2024. Support Plus/4 World on Patreon |
