Date: Wed, 20 Oct 1999 14:04:27 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Rodeo Red cc: djgpp AT delorie DOT com Subject: Re: Read Me Third: A Short FAQ List In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 19 Oct 1999, Rodeo Red wrote: > C:\djgpp>unzip32 djdev202 > Warning: TZ environment variable not found, cannot use UTC times!! > Archive: djdev202.zip > inflating: bin/bin2h.exe > inflating: bin/coff2exe.exe > > etc. etc. etc. > All the files appear unzipped, but what does this warning mean. ? It means unzip32 cannot restore the correct time stamp of the files it unzips, because you don't have the TZ environment variable set up. See section 22.19 of the FAQ for more about this. Bottom line: you shouldn't worry about it too much, especially when unzipping djdevNNN.zip for the first time. > I think I can get to use unzip32 without solving this particalar dilemma > right now, but I would still like to find out why the redirect doesn't work. Me too. Let's try to find out. For starters, does the "Bad command" message happen for *any* program you invoke via REDIR? > > Btw, if by "-oe -e error.log" you meant to redirect both stdout and > > stderr to error.log, then you were wrong. > > I have no idea what you're talking about. Last week I asked > > >How do I copy > > the entire contents of the dos box into the clipboard ? > > the answer I got from "Johan Venter" > "Redirect it too a file with redir: > redir -oe -e error.log That advice was in error, too. (There's no warranty on correctness of free help, you know. As a matter of fact, there's no warranty on help you pay for, either; just read the fine print in all those licenses you get with commercial software.) > I got it to work when I compiled a file It will work as long as the program prints messages to stderr. stdout will still go to the screen. > but I have no idea what stdout and stderr are. Never heard of > em. What are they ? Each program gets 3 I/O channels when it starts. These are: the standard input, stdin, the standard output, stdout, and the standard error, stderr. They are all connected to the console by default, but REDIR can redirect them to files. Library functions such as fprintf use these streams to print messages. See section 6.14 of the FAQ for more about this. > > The handles > > Handles ? Whats a handle ? That's a way to reference an I/O channel. When you open a file, the library functions like `open' return you a handle that you can then use to call functions such as `read' or `write'. > > redir -e error.log -oe unzip32 djdev202 > > Neither works That's because you have some additional problem. Once that one is solved, the above is the correct way you should use to redirect both stdout and stderr to a file.