🚀 go-pugleaf

/* Written 11:38 am  Feb  5, 1987 by bob@cald80.UUCP in uxc.cso.uiuc.edu:comp.sys.ibm.pc */
>In article <3281@hplabs.hplabs.UUCP> drichard@hplabs.UUCP (Dave Richards) writes:
>>
>>putc()ing characters to a stream that was successfully opened via
>>fopen() for "w" access to "COM1".  I check the returned pointer for NULL
>>and guaranteed fopen()s success.  However, after writing BUFSIZ
>>...much deleted for Pnews
>>	Dave Richards at Hewlett-Packard Labs (drichard@hplabs)
>
>I have found that fopen()ing a file causes the system to assume that
>you are going to send text to it.  It usually turns on ^Z mapping to
>end of file.  It also does \n to \r\n mapping.  Needless to say, you
>can't pump binary to it.

I'm not sure about aztec or desmet, but most of the C compilers I've
used (including MSC) give you the option of opening the file in
binary mode by appending a b to the mode (i.e. fopen("file","wb");).

>Try to use open() on COM1 and see if that has any better success.

With MSC, there are 5 predefined stream pointers...stdin, stdout,
stderr, stdaux (COM1:), and stdprn (LPT1:).  No opening is
necessary...just write to the appropriate stream.  This is all
documented completely in the manuals.

>					Bob Meyer
>					Calspan ATC

----
Dan Crimmins
University of Illinois at Urbana-Champaign
Computing Services Office - Micro Consulting Dept.

ARPA:	crimmins@uiucuxc.cso.uiuc.edu
BITNET:	crimmins@uiucuxc.bitnet
CSNET:	crimmins@uiucuxc.csnet
UUCP:	{ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!crimmins