From:	strags11 AT yahoo DOT com (Nick)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Simple (?) problem with djgpp/gcc/make
Date:	7 Jun 2003 18:34:38 -0700
Organization:	http://groups.google.com/
Lines:	34
Message-ID:	<1ba37fef.0306071734.14b12b96@posting.google.com>
References:	<1ba37fef DOT 0306010650 DOT 10517f99 AT posting DOT google DOT com> <6137-Sun01Jun2003200228+0300-eliz AT elta DOT co DOT il> <1ba37fef DOT 0306011651 DOT 4dfb06ed AT posting DOT google DOT com> <3995-Mon02Jun2003065843+0300-eliz AT elta DOT co DOT il> <1ba37fef DOT 0306021906 DOT 52b96029 AT posting DOT google DOT com> <bbhte5$n1e$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <1ba37fef DOT 0306031706 DOT 1eeb3d5e AT posting DOT google DOT com> <bbkcot$8dd$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host:	151.204.82.197
X-Trace:	posting.google.com 1055036079 15500 127.0.0.1 (8 Jun 2003 01:34:39 GMT)
X-Complaints-To:	groups-abuse AT google DOT com
NNTP-Posting-Date:	8 Jun 2003 01:34:39 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

This solved the problem, thanks.  The trouble was the autoexec.nt
file, and as you surmised it was the XP upgrade that caused the
trouble.  At least Microsoft's engineers were nice enough to comment
this file to state that they were copying the settings from my old
OS's autoexec.bat file.  :-)

The only mystery still remaining is why djgpp's "make" crashes when I
issue an ECHO command in all uppercase letters.  That still happens.

Nick


Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> wrote in message news:<bbkcot$8dd$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>...
> Nick <strags11 AT yahoo DOT com> wrote:
> > Thanks, but still no luck.  I renamed autoexec.bat to something else
> > entirely, but the problem remains.  (This isn't that big a surprise,
> > really, because the path defined in autoexec.bat isn't the one that
> > shows up in the command prompt anyway.  
> 
> It's not the exact same PATH, right.  But it's the same set of
> directories in there, with one exception that can easily be attributed
> to Windows trying to "fix" what it would perceives as a problem in
> that PATH.  The only major difference is that the order is reversed.
> 
> My guess: your upgrade to XP really is the root of this.  During the
> upgrade, XP probably saw the same autoexec.bat you're seeing now, and
> it converted that to an autoexec.nt for use with DOS sessions.
> Getting it backwards is exactly the kind of silliness to be expected
> from M$ hirelings coding such a converter, I'd say.
> 
> So: find autoexec.nt and rename that, and see how that changes things.
> 
> As a last resort, you may have to search your whole hard drive for
> occurences of that particular PATH listing.

- Raw text -