NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/sys/transput/1433

Internet Message Format | 1993-01-28 | 1.6 KB

Path: sparky!uunet!seismo!darwin.sura.net!gatech!rpi!batcomputer!munnari.oz.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!news.adelaide.edu.au!jeremy
From: [e-mail] (Jeremy Webber)
Newsgroups: comp.sys.transputer
Subject: Re: Format of .btl files
Message-ID: <[e-mail]>
Date: 27 Jan 93 14:24:43 GMT
References: <[e-mail]>
    <[e-mail]>
Organization: Digital Arts Film and Television
Lines: 22
NNTP-Posting-Host: chook.cs.adelaide.edu.au
In-reply-to: [e-mail]'s message of 26 Jan 93 03:49:07 GMT

In article <[e-mail]> [e-mail] (Don Goodeve) writes:

   The bootable file has encoded into it all the configuration and
   booting info as well as the executable text. The btl file is an
   unstructured binary file from the point of view of iserver. The
   iserver just sends the file down the link. The file is structured
   into packets (as I understand it) by bootstrap code as it passes
   into the network and is fanned out. All control lies with the
   code in the bootable. The iserver does not have a clue.

Further, there is a very good reason for doing it this way.  Many
(most?) transputers run in an embedded environment where there is no
Iserver.  Having all the bootstrap code in the .btl file means that the
same .btl file can be loaded into ROM to start such a system.

    -jeremy
--
--
Jeremy Webber               Internet: [e-mail]
Digital Arts Film and Television,         [e-mail]
1 Ledger Rd, Beverley, SA 5009,       Phone: [phone]
Australia                    FAX: [phone]