Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!decwrl!ucbvax!rti-sel.UUCP!rcb
From: rcb@RTI-SEL.UUCP (Random)
Newsgroups: mod.computers.vax
Subject: Re: VMS output
Message-ID: <8603101411.AA00255@rti-sel>
Date: Mon, 10-Mar-86 09:11:25 EST
Article-I.D.: rti-sel.8603101411.AA00255
Posted: Mon Mar 10 09:11:25 1986
Date-Received: Tue, 11-Mar-86 08:48:46 EST
References: <510520825.rick@siemens>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Research Triangle Institute, RTP, NC
Lines: 25
Approved: info-vax@sri-kl.arpa

In article <510520825.rick@siemens> you write:
>
>	 I've been having a problem with output on VMS C.  I am in the
>	 process of porting a graphics program from UNIX to VMS.  My
>	 problem concerns the driver for a Raster Technologies' Model
>	 One/10 terminal.  
>
>	 On VMS, I send lots and lots of ASCII characters to the
>	 terminal but the computer decides that no one would really
>	 want to output so many characters without a newline now and
>	 again so every 256th character is a newline.

Deja Vu!!!! I think I've been here before!!! As it turns out, the VMS
C stdio stuff is not very good for pure binary output to terminals as
it does not have an ioctl to set a raw mode. You will need to use
QIO to set ther terminal line to pasthru. This may be enough to allow the
use of C io calls. I personally use QIO's for all the io to graphics devices
so that I know exactly what is going on. All you need is one routine
to write a character and one to flush the buffer in the first routine.
I would definately suggest doing some buffering if you use qio's. The overhead
is just too much for one character at a time. 

					Random (Randy Buckland)
					Research Triangle Institute
					...!mcnc!rti-sel!rcb