Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!mahendo!wlbr!hacgate!gryphon!pnet02!rickf From: rickf@pnet02.gryphon.com (Rick Flower) Newsgroups: comp.sys.amiga.tech Subject: Help Needed Connecting "stdout" to a Process in Lattice 5.02.. Message-ID: <22855@gryphon.COM> Date: 29 Nov 89 05:20:21 GMT Sender: root@gryphon.COM Organization: People-Net [pnet02], Redondo Beach, CA. Lines: 23 I've just finished writing a small routine that will enable me to create a process that is part of (and linked into) my main program.. Anyway, since it doesn't have the normal (or any for that matter) startup code, I don't get ANY "stdout/stdin" file-type pointers, so regular "printf" functions go into the bit-bucket (or somewhere?!?) Anyway, I tried passing the "pr_CLI" and the "pr_COS" and the "pr_CIS" and the "pr_ConsoleTask" fields from the parent to the child in my Message structure that I passed. I had the child assign the parental values of these fields to the child and attempt a "printf".. But, to no avail.. I looked at the Lattice startup code in "c.a" and also in "cback.a" and noticed that it seems their "stdout/stdin" pointers are an offset from their base pointer that resides in A4.. I don't really want to patch into the code in that manner if I can do it easier, but if not, perhaps I'll have to do that.. If ANYONE knows about this particular field with Lattice, I would be happy to hear any and all responses! Thanks.. +-----------------------------------------------------------------------------+ | Caution, 68k Assembly Language Programmer at Play! | | Support S.A.N.E. (Snails Against Nuclear Energy) | +-----------------------------------------------------------------------------+ | UUCP: {ames!elroy, }!gryphon!pnet02!rickf | | InterNet: rickf@pnet02.gryphon.com | +=============================================================================+