Xref: news-dnh.mv.net comp.os.msdos.djgpp:2847
Path: news-dnh.mv.net!mv!news.sprintlink.net!newsfeed.internetmci.com!news.msfc.nasa.gov!elroy.jpl.nasa.gov!news.aero.org!kasper
From: kasper AT aero DOT org (Brian P. Kasper)
Newsgroups: comp.os.msdos.djgpp
Subject: Redirecting stderr to a file -- oops
Date: 25 Oct 1995 19:08:36 GMT
Organization: The Aerospace Corporation
Lines: 29
Distribution: world
Nntp-Posting-Host: aerospace.aero.org
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

As it says in the subject line, oops.

In my previous post discussing the redirection of stderr to a
file, I most carefully included information about what version
of DJGPP I was running when I successfully redirected stderr
by including an ampersand ('&') character immediately after the
redirection ('>') char.

Unfortunately, about half an hour after I posted that message,
I realized that the _shell_ I'm using is *much* more important
than the version of DJGPP.

Redirection of stderr works just fine as I outlined in my
previous posting under 4DOS for Windows NT.  When I try the
same technique under the DOS 5.0 which ships with NT, no dice.

I retract my previous statement that this technique works,
except to say that it might work, depending upon the DOS you
are using.

I have not tried the technique of adding '2r1' (or whatever the
exact string is) to my GO32 environment variable, as suggested
by an astute poster.

Sorry for the blunder.

-Brian Kasper
 The Aerospace Corporation
 kasper AT aero DOT org