Do you need to, run test.tsk as opposed to, run test ? What if you “run foo” and foo is nowhere to be found, does it complain or just silently return to the prompt?
I haven’t been on RSX since about 1981 so be gentle HA HA cje -- Chris Elmquist > On Sep 2, 2026, at 9:25 PM, Peter Ekstrom via cctalk <[email protected]> > wrote: > > Hi Mike, > > I added that and rebuilt the task but still no output on the terminal. > > - Peter > >> On Wed, Sep 2, 2026 at 10:16 PM Mike Katz via cctalk <[email protected]> >> wrote: >> >> try fflush( stdout ); >> >>> On 9/2/2026 9:02 PM, Peter Ekstrom via cctalk wrote: >>> Hi Fred, >>> >>> I should have mentioned I tried printf as well. And I had the /n in that >>> output but nothing was printed on the terminal. >>> I have had the same thought about buffering. I think I ran into that on >> my >>> Amiga back in the day with something. >>> >>> Thank you though! >>> >>> - Peter >>> >>> On Wed, Sep 2, 2026 at 9:57 PM Fred Cisin via cctalk< >> [email protected]> >>> wrote: >>> >>>> No idea whether this is applicable to you, . . . >>>> There are multiple variations of puts() (with/without \n, etc.) >>>> Surprisingly, printf() is more standardized. >>>> Try printf, instead of puts, and see if it makers a difference. >>>> >>>> and/or add a \n to the end of your string literal, in case it is doing >>>> some cockamamy buffering, and not making the outpur until it is given an >>>> end of line marker. That would be absurd, but there are weirder things >> in >>>> some C libraaries. >>>> >>>> -- >>>> Grumpy Ol' [email protected] >>>> >>>> >>>> On Wed, 2 Sep 2026, Peter Ekstrom via cctalk wrote: >>>> >>>>> Hello again, >>>>> Yes, this time I am trying to figure out what I'm doing wrong while >>>>> creating a C program. >>>>> It is still in RSX11M+ on my 11/23+ and PDP-11 C 1.1. >>>>> >>>>> I have a really simple test program like this: >>>>> >>>>> +>type test.c >>>>> #include <stdio.h> >>>>> >>>>> main() { >>>>> puts("Hello, world!"); >>>>> } >>>>> >>>>> The following is what I do to compile and task build: >>>>> >>>>> +>type tstbld.cmd >>>>> .IFNINS MAC INS $MAC >>>>> .IFNINS TKB INS $TKB >>>>> >>>>> PIP TEST.C/PU,TSTBLD.CMD/PU,TSTTKB.CMD/PU >>>>> CCC TEST.C >>>>> TKB @TSTTKB.CMD >>>>> PIP TEST.OBJ;*/DE >>>>> PIP TEST.TSK/PU >>>>> >>>>> +>type tsttkb.cmd >>>>> TEST/-FP=TEST,LB:[1,1]CFPURSX.OLB/LB >>>>> / >>>>> UNITS=1 >>>>> ASG=TI:1 >>>>> TASK=...TST >>>>> LIBR=FCSFSL:RO >>>>> / >>>>> >>>>> The code compiles fine and TKB has no issues. I get my test.tsk: >>>>> >>>>> +>dir test.tsk >>>>> >>>>> Directory DU0:[200,2] >>>>> 2-SEP-2026 21:36 >>>>> >>>>> TEST.TSK;2 22. C 02-SEP-2026 21:30 >>>>> >>>>> Total of 22./22. blocks in 1. file >>>>> >>>>> I run it as '+>run test' and I just get the prompt back. I expect it to >>>>> print to the terminal. >>>>> What am I missing? Nothing stands out to me in the manual. I'm sure >> it's >>>>> something stupid. >>>>> >>>>> Any pointers would be greatly appreciated. >>>>> >>>>> - Peter >>>>> >>
