At 8:40 PM +1200 on 4/9/00, Robert Purves wrote:

>Somewhat trimmed, and with comments added, your dump shows
>
>[SNIP]



>This is unlinked assembler code. It shows a stackframe being set up, and a
>call to InitOpenTransportCommon with parameter = 3. Information about the
>location and nature of the actual library function is given in a (to me)
>incomprehensible MPW format, presumably meant for the linker.
>
>In MPW and in Code Warrior, linking is a separate phase that follows
>compilation. Addresses are resolved at link time, and cross-TOC calls (i.e.
>calls to a different code fragment) handled by overwriting the nop with an
>instruction that restores the TOC register.

Most of what is done at low-level programming is beyond me, I never 
kept up with it.  I did some 6809 assembly on a Commodore SuperPet 
back in '82.  It had a very advanced (for the time) development 
environment.  One thing I do remember is being able to create 
relocateable code with the assembler, everything was written with 
relative addressing.  I've forgotten the particulars but we had a 
separate assembler and linker for that as well, so I do understand 
some of the process.  Thanks for taking a look.


>Unfortunately none of the above seems to help in constructing a call to
>InitOpenTransport from FB^3.


Too bad, I just hoped that if the file could be read it might help.