Path: utzoo!attcan!uunet!mcvax!cernvax!davidj
From: davidj@cernvax.UUCP (davidj)
Newsgroups: comp.sys.transputer
Subject: Re: Problems loading transputer networks .....
Message-ID: <812@cernvax.UUCP>
Date: 6 Sep 88 06:58:10 GMT
References: <8808170650.AA23442@uk.ac.ox.prg>
Reply-To: davidj@cernvax.UUCP ()
Organization: CERN European Laboratory for Particle Physics, CH-1211 Geneva, Switzerland
Lines: 20

To: MALENT%finabo.earn@NSS.CS.UCL.AC.UK
Subject: Re: Problems loading transputer networks .....
Newsgroups: comp.sys.transputer
In-Reply-To: <8808170650.AA23442@uk.ac.ox.prg>
Organization: CERN European Laboratory for Particle Physics, CH-1211 Geneva, Switzerland
Cc: 
Bcc: 
If you mean 'the first processor has a higher entry point than the others...'
then is this the processor that TDS is running on ? If it is then this
explains why the entry pointis higher. TDS runs on the 'root' processor
and in rev-c of TDS occupies the low end of memory (i.e.) on chip memory
and upwards. So that your program will be loaded above this. Other processors
in the network don't have to worry about tds, so the program can start low
down in mem. In rev-d of TDS, the TDS code occupies the high end of the
transputer memory i.e. on a 2-mbyte card it sits up near 200000. I don't
really know why padding your program with a byte array mafe it work, but
perhaps you were overwriting some of the code in the unpadded version, and
all you did was hit the byte array in the the padded one ??????

	Dave Jeffery