Mail Archives: djgpp/2003/06/04/06:06:35
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.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -