🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.ibm.pc
Article #43512

MSC, Devices, and 0x1a

#43512
From: George Woodside
Date: Mon, 05 Mar 1990 15:33
21 lines
1364 bytes

When a binary file is opened under MSC (5.1), and the file name is a
device (AUX, CON, PRN, NUL), the binary mode is not completely
transparent. It does stop altering line feeds to carriage return/line
feeds, but it still stops and (apparently) closes the device when the
data stream contains the EOF character 0x1a. The fwrite calls write,
where the library reference manual states "When writing to a device,
write treats a CTRL+Z character in the buffer as an output terminator."

In reality, when a binary data stream (a graphic image) to a printer
contains an 0x1a character, the output is truncated, and eventually the
subsequent write calls will return a file write error. 

Is there any method, save byte-at-a-time INT output, to write a binary data
stream transparently to a device?

-- 
* George R. Woodside - Citicorp/TTI - Santa Monica, CA *
* Path:       woodside@ttidca                          *
*   or:       ..!{philabs|csun|psivax}!ttidca!woodside *
Technical Details
Message-ID: <10521@ttidca.TTI.COM>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!srhqla!quad1!ttidca!woodside

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!srhqla!quad1!ttidca!woodside
From: woodside@ttidca.TTI.COM (George Woodside)
Newsgroups: comp.sys.ibm.pc
Subject: MSC, Devices, and 0x1a
Message-ID: <10521@ttidca.TTI.COM>
Date: 5 Mar 90 15:33:37 GMT
Reply-To: woodside@ttidca.tti.com (George Woodside)
Organization: Citicorp/TTI, Santa Monica
Lines: 21