🚀 go-pugleaf

/***** unido:net.micro.at16 / druxu!rwb /  7:09 pm  Jun 18, 1986*/
[...]
To link: after you have generated two disks containing .bin files, you
are ready to link.  Create a file called hack.lnk containing the linker
directives.  It should be modelled after c.lnk, but expand the body to
include all the .bin files you compiled above (instead of taking the
command line).  Here the strategy is to copy the first disk of .bin
files (the one that is full) to the RAM disk and place the second disk
on the drive, writting the .ttp file to the drive; thus, each .bin file
on the second disk should be referenced in the .lnk file as b:name.bin.
Resize the RAM disk to 435K (this is the smallest I could make it and still
fit everything on it, leaving the rest of the RAM for the linker).  Copy
to the RAM disk the following:
	* the linker (link.ttp)
	* the libraries (clib.bin and startup.lib)
	* the all the .bin files from the first disk
	* the hack.lnk file
Run the linker with the following command line (leave off link if
invoked from the desktop):
	link -with hack -nolist -prog b:hack.ttp
After 15 minutes (if all has gone well), you should have an executable
file on drive b.
[...]
/* ---------- */

I found out that if you arrange the program output to go to the ram disk
and keep all other files  except the library on normal disk, you can link
hack within 6 minutes.

	Andreas Bormann
	University of Dortmund  [UniDo]
	West Germany

Uucp:   ab@unido.uucp
Path:   {USA}!seismo!{mcvax}!unido!ab
	{Europe}!{cernvax,diku,enea,ircam,mcvax,prlb2,tuvie,ukc}!unido!ab
Bitnet: ab@unido.bitnet (==  ab@ddoinf6.bitnet)
		      \
F-111 bombers:    -=>-->-*>     N 51 29' 05"    E 07 24' 42"
		      /