From: ams AT ludd DOT luth DOT se (Martin Str|mberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: REDIR - Bad command or file name
Date: 3 Apr 1999 17:16:48 GMT
Organization: University of Lulea, Sweden
Lines: 36
Message-ID: <7e5ie0$jln$1@news.luth.se>
References: <370519a3 DOT 4299122 AT news DOT enter DOT net> <7e373s$j9t$1 AT news DOT luth DOT se> <37064729 DOT 8201713 AT news DOT enter DOT net>
NNTP-Posting-Host: queeg.ludd.luth.se
Cc: djgpp-workers AT delorie DOT com
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Tim Updegrove (tdu AT enter DOT net) wrote:
: Yes, I read readme.1st.  go32-v reported DPMI memory=19580 kb and DPMI
: swap space=9956kb.  Right clicking on the title of the DOS box and
: selecting properties/memory shows all the settings (Convential, ems,
: xms, and dpmi) are set to "auto".
: 
: I'm able to compile (gcc) and run a "hello world" program so some/many
: things are working.  Just entering REDIR by itself does return the
: redir help screen.  Any other suggestions why the below REDIR command
: gets "bad command or file name"?

[Klippa, klapp, kluppit.]

: >: A simple REDIR command like "redir -o gcc.log gcc -v -o hello.exe
: >: hello.c" puts "bad command or file name" in gcc.log.  A user on

[Klippa, klapp, kluppit.]

First "redir -o gcc.log gcc -v -o hello.exe hello.c" doesn't put "bad
command or file name" in gcc.log for me; it puts it on the screen.

Anyway, yes indeed. I can recreate your problem.

From experimenting it seems it's the ".log" in "gcc.log" that somehow
makes it fail. If I use "redir -o xxxxgcc gcc -v -o hello.exe hello.c"
it seems to be doing what it should. Or if I first "SET LFN=n", it
works too (but a little differently).

Hope this helps you work-around the problem.

I've sent this message to djgpp-workers too.


Arnold, Symphony No. 3,

							MartinS