Date: Sun, 16 Feb 1997 19:58:21 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: "'OpenDOS newsgroup'" <opendos AT mail DOT tacoma DOT net>
Subject: Re: [opendos] BAD Filesystems
In-Reply-To: <5t1LUIA1E6BzEwYq@darkblak.demon.co.uk>
Message-ID: <Pine.GSO.3.95.970216195702.3217D-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Mon, 17 Feb 1997, Ian 'DrDebug' Day wrote:
> "Colin W. Glenn" <cwg01 AT gnofn DOT org> writes
> >> I've been using 4DOS with DOS apps for years it allows command lines of
> >> upto 256 characters.  It simply only gives 126 to the application.  It's

> >Well, programmers have been bouncing off that wall for years, which is why
> >many fine well written programs allow the use of @include files.

> Did I miss something there?
> What have #include files got to do with command line length?

Not #include, @include, as in:

pkzip oldjunk @filelist -m

  <! PrePared HTML!  Just export as a HTML file and Click!>
A Christian Web Site!  The Light 
  <a href="http://www.thelight.org/">.</a><br>
A neat place to visit. HotSpot 
  <a href="http://www.hspro.com/hotspot/">.</a><br>
Caldera, Inc. / Makers of OpenDOS
  <a href="http://www.caldera.com/">.</a><br>
Caldera's OpenDOS page
  <a href="http://www.caldera.com/dos/dos.htm">.</a><br>