Date: Sun, 16 Sep 2001 15:03:54 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michael Allison <michael DOT allison2 AT sympatico DOT ca>
cc: djgpp-workers AT delorie DOT com, Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Subject: Re: Build problems
In-Reply-To: <014a01c13eab$37d6ac70$8a41d0d8@mnrpbapc0800>
Message-ID: <Pine.SUN.3.91.1010916150319.12964A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 16 Sep 2001, Michael Allison wrote:

> From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
> > Btw, I found out that if I open a DOS box on W2K and type
> > some innocent command, like "djtar -h", I get "Bad command
> > or file name", and right after that the expected results of the
> > program's run.
> 
> I've had Windows NT (not just W2K) do this same thing
> for a couple of years on the first djgpp built program that is run after
> a reboot.  I think you'll find it is not specific to invoking djtar either.

Sure, it's quite clear to me that djtar is not the reason.