Date:	Tue, 19 Oct 1999 13:24:55 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Rodeo Red <rodeored AT netstep DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: Read Me Third: A Short FAQ List
In-Reply-To:	<BB7C4C9BDA989697.89844A29E55B6BD8.EE56B5FB36DEB4DD@lp.airnews.net>
Message-ID:	<Pine.SUN.3.91.991019131856.13375B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 18 Oct 1999, Rodeo Red wrote:
> It appears to unzip ok with the comand :
> unzip32 djdev202
> but there's warnings or error messages or something I can't read because it
> goes by so fast.

Try pressing Ctrl-S.

> So I tried to redirect the message to error.log:
> 
> C:\djgpp>redir -oe -e error.log unzip32 djdev202
> Bad command or file name
> 
> Why doesn't this redirect work ?

I don't know.  I tried the exact command above, and it worked for me.
Are you sure this was the *exact* command you typed?

Btw, if by "-oe -e error.log" you meant to redirect both stdout and 
stderr to error.log, then you were wrong.  The handles are redirected in 
the order you mention them on the command line, so the above redirects 
stdout to the console, because that's where stderr is initially, then 
redirects stderr to a file.  You need to do it the other way around:

	redir -e error.log -oe unzip32 djdev202

This is explained in the redir docs.

- Raw text -