home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!doc.ic.ac.uk!uknet!yorkohm!don
- From: don@ohm.york.ac.uk (Don Goodeve)
- Newsgroups: comp.sys.transputer
- Subject: Re: Format of .btl files
- Message-ID: <1993Jan26.034907.9697@ohm.york.ac.uk>
- Date: 26 Jan 93 03:49:07 GMT
- References: <1993Jan22.114632.24686@dcs.warwick.ac.uk>
- Organization: Electronics Department, University of York, UK
- Lines: 32
-
- In <1993Jan22.114632.24686@dcs.warwick.ac.uk> markhill@dcs.warwick.ac.uk (M Hill) writes:
-
- >I'm doing a project with transputers, and would like to know the answer
- >to the following question.
-
- >When the iserver boots a transputer network with a .btl file, is the
- >iserver just sequentially picking up bytes from the file and throwing
- >them at the C011? This would imply that the .btl file had all the necessary
- >bootstrap code for the whole network inside it, in addition to the
- >program code that will eventually run on each processor on the network.
-
- Yup! thats it!
-
- 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.
-
- I hope that answers it. If you have any further queries, email me
- and I will do my best...
-
- Cheers
- Don
-
- --
- Don Goodeve|Adaptive Systems|Electronics Dept|University of York
- email: don@ohm.york.ac.uk|-------->I speak from my own angle...
- --Disclaimer:--------------------------------------------------
- |In the beginning was the word. Man attempted to speak the word |
-