Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!vsi1!octopus!stever
From: stever@Octopus.COM (Steve Resnick )
Newsgroups: comp.os.msdos.programmer
Subject: Re: Can std-io be a *binary* file?
Message-ID: <1990Nov1.162644.25372@Octopus.COM>
Date: 1 Nov 90 16:26:44 GMT
References: <22926@grebyn.com> <11280@hubcap.clemson.edu>
Reply-To: stever@octopus.UUCP (Steve Resnick )
Organization: Octopus Enterprises, Cupertino CA
Lines: 29

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*  ;)
>

And DOS 3.x fixes it? I think not. Real people use DOS 4.0! :) 

(Sorry - I couldn't resist)

The 128 byte command limit exists in DOS Version 1-4.01 (I haven't seen 4.03
or 5.0 yet) and in OS/2 1.0 - 1.21 (All of which I have run and yes there
are newer versions of OS/2). I guess Microsoft doesn't expect folks to
type much. :)

Cheers!
Steve


-- 
----------------------------------------------------------------------------
steve.resnick@f105.n143.z1.FIDONET.ORG - or - apple!camphq!105!steve.resnick
Flames, grammar errors, spelling errrors >/dev/nul
The Asylum OS/2 BBS - (408)263-8017 IFNA 1:143/105.0