Date: Tue, 28 Jan 1997 13:11:34 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
cc: Gurunandan R Bhat <grbhat AT unigoa DOT ernet DOT in>, djgpp AT delorie DOT com
Subject: Re: tar for DJGPP
In-Reply-To: <Pine.GSO.3.95.970127233427.10377D-100000@sparkie.gnofn.org>
Message-ID: <Pine.SUN.3.91.970128130859.11362B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 27 Jan 1997, Colin W. Glenn wrote:

> I, myself, noticed that, but didn't use it because I had need of TAR
> multiple times in a real mode session, ie I was calling it up to 160 time
> at one sitting to extact a _single_ file for working with.  Even loading
> cwsdpmi as resident wouldn't help because I'd have to do it before
> launching my command shell, and I didn't want it in my autoexec because I
> might not need it.  Is this making sense?

Not to me, it doesn't.  Why do you need to load cwsdpmi resident, when 
every DJGPP program loads it on startup automagically?  Why do you need 
to invoke TAR for each file instead of extracting those which you need?  
What does ``real mode session'' mean?