Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ncar!gatech!bloom-beacon!eru!hagbard!sunic!news.funet.fi!tukki.jyu.fi!jyu.fi!otto From: otto@tukki.jyu.fi (Otto J. Makela) Newsgroups: comp.os.msdos.programmer Subject: Re: Can std-io be a *binary* file? Message-ID: Date: 1 Nov 90 12:25:29 GMT References: <22926@grebyn.com> <11280@hubcap.clemson.edu> Sender: news@tukki.jyu.fi (News articles) Organization: Turing Police, Criminal AI section Lines: 24 In-Reply-To: lsalomo@hubcap.clemson.edu's message of 31 Oct 90 17:17:55 GMT In article <11280@hubcap.clemson.edu> lsalomo@hubcap.clemson.edu (lsalomo) writes: From article <22926@grebyn.com>, by jmbj@grebyn.com (Jim Bittman): > A (unix) friend of mine is attempting to port an application, and is > getting frustrated, not that I can blame him. Most his complaints are > quite valid. One question (to which I had no answer) was: > "Why wasn't the 128 byte command line limit fixed between DOS > versions 1.0 and 1.1?" Because real people use DOS 3.x+ *grin* ;) All right, so now the question is: why wasn't it fixed between DOS versions 3.01 and 3.10 ? Or between versions 3.30 and 4.01 ? I hate MicroS*t for the fact that no significant improvements have gone into the command processor since version 2.11 ! Gee, for some reason I couldn't find the original article, but to answer the question posed in the Subject: yes, stdin and stdout can both be binary files -- you just have to ioctl them to binary mode ! -- /* * * Otto J. Makela * * * * * * * * * * * * * * * * * * */ /* Phone: +358 41 613 847, BBS: +358 41 211 562 (CCITT, Bell 24/12/300) */ /* Mail: Kauppakatu 1 B 18, SF-40100 Jyvaskyla, Finland, EUROPE */ /* * * Computers Rule 01001111 01001011 * * * * * * * * * * * * * * * * */