Path: utzoo!attcan!uunet!husc6!rutgers!ucsd!ucsbcsl!amadeus!grosen From: grosen@amadeus.ucsb.edu (Mark D. Grosen) Newsgroups: comp.sys.ibm.pc Subject: Re: Microsoft C Bug or Feature ????? Message-ID: <754@hub.ucsb.edu> Date: 6 Aug 88 18:10:04 GMT References: <8808021504.AA05128@wilson.csri.toronto.edu> <11074@cgl.ucsf.EDU> Sender: news@hub.ucsb.edu Reply-To: grosen@amadeus.UUCP (Mark D. Grosen) Organization: University of California, Santa Barbara Lines: 24 > Problems printing binary files . . . . I went through the same problems with trying to print binary files with MSC. Somebody mentioned earlier about using setmode(file, O_BINARY). Another method is to set the global variable _fmode to binary so that all files are opened in binary mode. If you have a disk file (binary, contains 0x1a) that you want to print, generic MSDOS print won't work. Using a plain copy command won't work UNLESS you use the binary option, as in C:> copy /b print.fil lpt1: (I hope that option is right; see your DOS manual.) I guess DOS checks the destination and if it's a device (printer) interprets the file differently. Mark Mark D. Grosen ARPA: grosen@amadeus.ucsb.edu Signal Processing Lab / Communications Research Lab ECE Dept. University of California Santa Barbara, CA 93106