For the FAQ: NT PATH problems

For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Q: I'm on NT, and bash can't find any commands unless I give the
whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
see this - it magically disappears again.

A: Under Settings/Control Panel/System/Environment, there are
system and user variables. You need to have both a "Path" entry in
the upper window, and a "PATH" entry in the lower window. The
latter is probably missing.

Just type PATH into the Variable field, leave Value blank, and click
on Set.

(Don't ask me why Microsoft decided to do it this way.)



>>> Someone with an US NT should check that I guessed all the
translations right.

Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Corinna Vinschen]

Kai Henningsen wrote:
> 
> Q: I'm on NT, and bash can't find any commands unless I give the
> whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
> see this - it magically disappears again.
> 
> A: Under Settings/Control Panel/System/Environment, there are
> system and user variables. You need to have both a "Path" entry in
> the upper window, and a "PATH" entry in the lower window. The
> latter is probably missing.
> 
> Just type PATH into the Variable field, leave Value blank, and click
> on Set.
> 
> (Don't ask me why Microsoft decided to do it this way.)

I dont know, why you think so, but that is neither a general
problem, nor a solution. NT concat's both PATHs to generate the
path for the current user. They also doesn't disappear if
they are correct. One problem seems to be the existence of a
trailing semicolon but I don't remember the exact effect. Maybe,
another reader can explain it?

Regards,
Corinna

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]

On 1 Oct 99, at 11:43, Corinna Vinschen wrote:

> Kai Henningsen wrote:
> >
> > Q: I'm on NT, and bash can't find any commands unless I give the
> > whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
> > see this - it magically disappears again.
> >
> > A: Under Settings/Control Panel/System/Environment, there are
> > system and user variables. You need to have both a "Path" entry in
> > the upper window, and a "PATH" entry in the lower window. The
> > latter is probably missing.
> >
> > Just type PATH into the Variable field, leave Value blank, and click
> > on Set.
> >
> > (Don't ask me why Microsoft decided to do it this way.)
>
> I dont know, why you think so, but that is neither a general
> problem, nor a solution.

It is an exact description of what happened to me, and how I solved
it. Nothing else worked; this worked immediately.

Of course, now that I try to reproduce it, I can't.

(At one time, I had two or three versions of the cygwin directory in
the PATH in a DOS window, and after calling CYGWIN.BAT, bash
showed none of them in the PATH.)

>NT concat's both PATHs to generate the
> path for the current user. They also doesn't disappear if
> they are correct. One problem seems to be the existence of a
> trailing semicolon but I don't remember the exact effect. Maybe,
> another reader can explain it?

Maybe it's something that got broken installing SP5, and got
repaired once the Control Panel poked around. I certainly don't
know.

Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Chris Faylor]

On Fri, Oct 01, 1999 at 01:26:40PM +0200, Kai Henningsen wrote:
>On 1 Oct 99, at 11:43, Corinna Vinschen wrote:
>> Kai Henningsen wrote:
>> > 
>> > Q: I'm on NT, and bash can't find any commands unless I give the
>> > whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
>> > see this - it magically disappears again.
>> > 
>> > A: Under Settings/Control Panel/System/Environment, there are
>> > system and user variables. You need to have both a "Path" entry in
>> > the upper window, and a "PATH" entry in the lower window. The
>> > latter is probably missing.
>> > 
>> > Just type PATH into the Variable field, leave Value blank, and click
>> > on Set.
>> > 
>> > (Don't ask me why Microsoft decided to do it this way.)
>> 
>> I dont know, why you think so, but that is neither a general
>> problem, nor a solution. 
>
>It is an exact description of what happened to me, and how I solved 
>it. Nothing else worked; this worked immediately.
>
>Of course, now that I try to reproduce it, I can't. 
>
>(At one time, I had two or three versions of the cygwin directory in 
>the PATH in a DOS window, and after calling CYGWIN.BAT, bash 
>showed none of them in the PATH.)
>
>>NT concat's both PATHs to generate the
>> path for the current user. They also doesn't disappear if
>> they are correct. One problem seems to be the existence of a
>> trailing semicolon but I don't remember the exact effect. Maybe,
>> another reader can explain it?
>
>Maybe it's something that got broken installing SP5, and got 
>repaired once the Control Panel poked around. I certainly don't 
>know.

In that case, this will not be going into the FAQ.  Sorry.

-chris

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3506 bytes --]

Well, I've had it happen again. Details below.

On 1 Oct 99, at 8:09, Chris Faylor wrote:

> On Fri, Oct 01, 1999 at 01:26:40PM +0200, Kai Henningsen wrote:
> >On 1 Oct 99, at 11:43, Corinna Vinschen wrote:
> >> Kai Henningsen wrote:
> >> >
> >> > Q: I'm on NT, and bash can't find any commands unless I give the
> >> > whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
> >> > see this - it magically disappears again.
> >> >
> >> > A: Under Settings/Control Panel/System/Environment, there are
> >> > system and user variables. You need to have both a "Path" entry in
> >> > the upper window, and a "PATH" entry in the lower window. The
> >> > latter is probably missing.
> >> >
> >> > Just type PATH into the Variable field, leave Value blank, and click
> >> > on Set.
> >> >
> >> > (Don't ask me why Microsoft decided to do it this way.)
> >>
> >> I dont know, why you think so, but that is neither a general
> >> problem, nor a solution.
> >
> >It is an exact description of what happened to me, and how I solved
> >it. Nothing else worked; this worked immediately.
> >
> >Of course, now that I try to reproduce it, I can't.
> >
> >(At one time, I had two or three versions of the cygwin directory in
> >the PATH in a DOS window, and after calling CYGWIN.BAT, bash
> >showed none of them in the PATH.)
> >
> >>NT concat's both PATHs to generate the
> >> path for the current user. They also doesn't disappear if
> >> they are correct. One problem seems to be the existence of a
> >> trailing semicolon but I don't remember the exact effect. Maybe,
> >> another reader can explain it?
> >
> >Maybe it's something that got broken installing SP5, and got
> >repaired once the Control Panel poked around. I certainly don't
> >know.
>
> In that case, this will not be going into the FAQ.  Sorry.
>
> -chris

This is my CYGNUS.BAT:

@ECHO OFF
SET MAKE_MODE=UNIX
SET PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
SET CDPATH=
SET HOME=/home
SET CYGWIN=ntsec
bash --login

This is the 'Path' system environment var definition:

E:\Perl\bin;%SystemRoot%\system32;%SystemRoot%;F:\Programme\Personal Communications;f:\aintx;%SystemRoot%\system32\nls\ENGLISH;%SystemRoot%\system32\nls;E:\NTReskit

The first (and second) Cygwin window opened today had the
following PATH:

PATH='/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/'

Then I added an empty user environment var PATH, and lo and
behold, the next Cygwin window opened had:

PATH='/gcc-2.95.1-mingw32/bin:/gcc-2_95-mingw32/bin/:/cygnus/cygwin-b20/H-i586-cygwin32/bin:/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal
Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/:/cygdrive/c/WIN95.US:/cygdrive/c/WIN95.US/COMMAND:/cygdrive/c/WIN98.US/COMMAND:/cygdrive/c/WIN98:/cygdrive/c/WIN98/COMMAND:/f/READIBMW:/f/vim/vim55'

So: absence of this variable does not always produce the bug, but
*if* the bug shows up, creating said variable removes it.


Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3506 bytes --]

Well, I've had it happen again. Details below.

On 1 Oct 99, at 8:09, Chris Faylor wrote:

> On Fri, Oct 01, 1999 at 01:26:40PM +0200, Kai Henningsen wrote:
> >On 1 Oct 99, at 11:43, Corinna Vinschen wrote:
> >> Kai Henningsen wrote:
> >> >
> >> > Q: I'm on NT, and bash can't find any commands unless I give the
> >> > whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
> >> > see this - it magically disappears again.
> >> >
> >> > A: Under Settings/Control Panel/System/Environment, there are
> >> > system and user variables. You need to have both a "Path" entry in
> >> > the upper window, and a "PATH" entry in the lower window. The
> >> > latter is probably missing.
> >> >
> >> > Just type PATH into the Variable field, leave Value blank, and click
> >> > on Set.
> >> >
> >> > (Don't ask me why Microsoft decided to do it this way.)
> >>
> >> I dont know, why you think so, but that is neither a general
> >> problem, nor a solution.
> >
> >It is an exact description of what happened to me, and how I solved
> >it. Nothing else worked; this worked immediately.
> >
> >Of course, now that I try to reproduce it, I can't.
> >
> >(At one time, I had two or three versions of the cygwin directory in
> >the PATH in a DOS window, and after calling CYGWIN.BAT, bash
> >showed none of them in the PATH.)
> >
> >>NT concat's both PATHs to generate the
> >> path for the current user. They also doesn't disappear if
> >> they are correct. One problem seems to be the existence of a
> >> trailing semicolon but I don't remember the exact effect. Maybe,
> >> another reader can explain it?
> >
> >Maybe it's something that got broken installing SP5, and got
> >repaired once the Control Panel poked around. I certainly don't
> >know.
>
> In that case, this will not be going into the FAQ.  Sorry.
>
> -chris

This is my CYGNUS.BAT:

@ECHO OFF
SET MAKE_MODE=UNIX
SET PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
SET CDPATH=
SET HOME=/home
SET CYGWIN=ntsec
bash --login

This is the 'Path' system environment var definition:

E:\Perl\bin;%SystemRoot%\system32;%SystemRoot%;F:\Programme\Personal Communications;f:\aintx;%SystemRoot%\system32\nls\ENGLISH;%SystemRoot%\system32\nls;E:\NTReskit

The first (and second) Cygwin window opened today had the
following PATH:

PATH='/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/'

Then I added an empty user environment var PATH, and lo and
behold, the next Cygwin window opened had:

PATH='/gcc-2.95.1-mingw32/bin:/gcc-2_95-mingw32/bin/:/cygnus/cygwin-b20/H-i586-cygwin32/bin:/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal
Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/:/cygdrive/c/WIN95.US:/cygdrive/c/WIN95.US/COMMAND:/cygdrive/c/WIN98.US/COMMAND:/cygdrive/c/WIN98:/cygdrive/c/WIN98/COMMAND:/f/READIBMW:/f/vim/vim55'

So: absence of this variable does not always produce the bug, but
*if* the bug shows up, creating said variable removes it.


Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Corinna Vinschen]

Kai Henningsen wrote:
> 
> Q: I'm on NT, and bash can't find any commands unless I give the
> whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
> see this - it magically disappears again.
> 
> A: Under Settings/Control Panel/System/Environment, there are
> system and user variables. You need to have both a "Path" entry in
> the upper window, and a "PATH" entry in the lower window. The
> latter is probably missing.
> 
> Just type PATH into the Variable field, leave Value blank, and click
> on Set.
> 
> (Don't ask me why Microsoft decided to do it this way.)

I dont know, why you think so, but that is neither a general
problem, nor a solution. NT concat's both PATHs to generate the
path for the current user. They also doesn't disappear if
they are correct. One problem seems to be the existence of a
trailing semicolon but I don't remember the exact effect. Maybe,
another reader can explain it?

Regards,
Corinna

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Chris Faylor]

On Fri, Oct 01, 1999 at 01:26:40PM +0200, Kai Henningsen wrote:
>On 1 Oct 99, at 11:43, Corinna Vinschen wrote:
>> Kai Henningsen wrote:
>> > 
>> > Q: I'm on NT, and bash can't find any commands unless I give the
>> > whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
>> > see this - it magically disappears again.
>> > 
>> > A: Under Settings/Control Panel/System/Environment, there are
>> > system and user variables. You need to have both a "Path" entry in
>> > the upper window, and a "PATH" entry in the lower window. The
>> > latter is probably missing.
>> > 
>> > Just type PATH into the Variable field, leave Value blank, and click
>> > on Set.
>> > 
>> > (Don't ask me why Microsoft decided to do it this way.)
>> 
>> I dont know, why you think so, but that is neither a general
>> problem, nor a solution. 
>
>It is an exact description of what happened to me, and how I solved 
>it. Nothing else worked; this worked immediately.
>
>Of course, now that I try to reproduce it, I can't. 
>
>(At one time, I had two or three versions of the cygwin directory in 
>the PATH in a DOS window, and after calling CYGWIN.BAT, bash 
>showed none of them in the PATH.)
>
>>NT concat's both PATHs to generate the
>> path for the current user. They also doesn't disappear if
>> they are correct. One problem seems to be the existence of a
>> trailing semicolon but I don't remember the exact effect. Maybe,
>> another reader can explain it?
>
>Maybe it's something that got broken installing SP5, and got 
>repaired once the Control Panel poked around. I certainly don't 
>know.

In that case, this will not be going into the FAQ.  Sorry.

-chris

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]

On 1 Oct 99, at 11:43, Corinna Vinschen wrote:

> Kai Henningsen wrote:
> >
> > Q: I'm on NT, and bash can't find any commands unless I give the
> > whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
> > see this - it magically disappears again.
> >
> > A: Under Settings/Control Panel/System/Environment, there are
> > system and user variables. You need to have both a "Path" entry in
> > the upper window, and a "PATH" entry in the lower window. The
> > latter is probably missing.
> >
> > Just type PATH into the Variable field, leave Value blank, and click
> > on Set.
> >
> > (Don't ask me why Microsoft decided to do it this way.)
>
> I dont know, why you think so, but that is neither a general
> problem, nor a solution.

It is an exact description of what happened to me, and how I solved
it. Nothing else worked; this worked immediately.

Of course, now that I try to reproduce it, I can't.

(At one time, I had two or three versions of the cygwin directory in
the PATH in a DOS window, and after calling CYGWIN.BAT, bash
showed none of them in the PATH.)

>NT concat's both PATHs to generate the
> path for the current user. They also doesn't disappear if
> they are correct. One problem seems to be the existence of a
> trailing semicolon but I don't remember the exact effect. Maybe,
> another reader can explain it?

Maybe it's something that got broken installing SP5, and got
repaired once the Control Panel poked around. I certainly don't
know.

Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Q: I'm on NT, and bash can't find any commands unless I give the
whole pathname. CYGWIN.BAT sets the PATH, but bash doesn't
see this - it magically disappears again.

A: Under Settings/Control Panel/System/Environment, there are
system and user variables. You need to have both a "Path" entry in
the upper window, and a "PATH" entry in the lower window. The
latter is probably missing.

Just type PATH into the Variable field, leave Value blank, and click
on Set.

(Don't ask me why Microsoft decided to do it this way.)



>>> Someone with an US NT should check that I guessed all the
translations right.

Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: For the FAQ: NT PATH problems

[Andrew Dalgleish]

Let me guess - you are using NT's boot loader to multiboot, correct?
(You say you are using NT, but your path contains references to
C:\WIN95.US and C:\WIN98.US)

When you use the NT boot loader to boot DOS/95/98 it copies autoexec.bat
and config.sys into c:\, and leaves them there the next time you boot
into NT.
NT does not execute autoexec.bat, but it does parse it for PATH
statements.
This means your NT environment may depend on what other OS you last
used.
Personally I have a one-line autoexec.bat call another batch file
(autodos.bat, auto95.bat, etc) which does the real work.
Because autoexec.bat doesn't contain any path statements NT doesn't get
confused.
(Now this could go in the FAQ :-)

If you add the following to the start of your cygwin.bat it might help
pin down what is going on.
echo %PATH%
pause

Do you also have a ~/.bashrc and/or ~/.bash_profile?


Regards,
Andrew Dalgleish


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Earnie Boyd]

--- Kai Henningsen <kai@cats.ms> wrote:
-8<-
> This is my CYGNUS.BAT:
> 
> @ECHO OFF
> SET MAKE_MODE=UNIX
> SET
>
PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
> SET CDPATH=
> SET HOME=/home
> SET CYGWIN=ntsec
             ^^^^^
Don't overlook this setting with this problem.  Although I can't imagine why it
would cause it, this has issued numerous changes that could cause this.

> bash --login
> 
> This is the 'Path' system environment var definition:
> 
> E:\Perl\bin;%SystemRoot%\system32;%SystemRoot%;F:\Programme\Personal
>
Communications;f:\aintx;%SystemRoot%\system32\nls\ENGLISH;%SystemRoot%\system32\nls;E:\NTReskit
> 
> The first (and second) Cygwin window opened today had the
> following PATH:
> 
> PATH='/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal
>
Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/'
> 
> Then I added an empty user environment var PATH, and lo and
> behold, the next Cygwin window opened had:
> 
>
PATH='/gcc-2.95.1-mingw32/bin:/gcc-2_95-mingw32/bin/:/cygnus/cygwin-b20/H-i586-cygwin32/bin:/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal
>
Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/:/cygdrive/c/WIN95.US:/cygdrive/c/WIN95.US/COMMAND:/cygdrive/c/WIN98.US/COMMAND:/cygdrive/c/WIN98:/cygdrive/c/WIN98/COMMAND:/f/READIBMW:/f/vim/vim55'
> 
> So: absence of this variable does not always produce the bug, but
> *if* the bug shows up, creating said variable removes it.
> 


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Chris Faylor]

On Mon, Oct 11, 1999 at 05:21:41AM -0700, Earnie Boyd wrote:
>--- Kai Henningsen <kai@cats.ms> wrote:
>-8<-
>> This is my CYGNUS.BAT:
>> 
>> @ECHO OFF
>> SET MAKE_MODE=UNIX
>> SET
>>
>PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
>> SET CDPATH=
>> SET HOME=/home
>> SET CYGWIN=ntsec
>             ^^^^^
>Don't overlook this setting with this problem.  Although I can't imagine why it
>would cause it, this has issued numerous changes that could cause this.

I don't see any reason for NTSEC to cause this problem.

Blaming ntsec for every problem that crops up is not really very productive.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]

On 12 Oct 99, at 10:06, Andrew Dalgleish wrote:

> Let me guess - you are using NT's boot loader to multiboot, correct?

Well, if booting something different less than 1% of the time counts
as multibooting ...

> When you use the NT boot loader to boot DOS/95/98 it copies autoexec.bat
> and config.sys into c:\, and leaves them there the next time you boot
> into NT.
> NT does not execute autoexec.bat, but it does parse it for PATH
> statements.
> This means your NT environment may depend on what other OS you last
> used.

There's only one other OS, and it's only changing when I need to
test software with another Win version, which hasn't happened in a
_long_ time. So I don't see why the environment should change.
Indeed, the modification date of the autoexec.bat is from 1999-09-
20, more than three weeks ago.

Plus, this doesn't explain why changing PATH does not work,
which is the real problem (not whatever is in PATH before trying to
change it).

> If you add the following to the start of your cygwin.bat it might help
> pin down what is going on.

I'll probably try that if it happens again. One of the peculiarities is
that I know how to remove the problem, but not how to provoke it -
once it's removed, it stays removed, at least for some days.

> Do you also have a ~/.bashrc and/or ~/.bash_profile?

The latter. This is it:

#! bash
echo "profile speaking"
umask 022



Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On 11 Oct 99, at 5:21, Earnie Boyd wrote:

> --- Kai Henningsen <kai@cats.ms> wrote:
> -8<-
> > This is my CYGNUS.BAT:
> >
> > @ECHO OFF
> > SET MAKE_MODE=UNIX
> > SET
> >
> PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
> > SET CDPATH=
> > SET HOME=/home
> > SET CYGWIN=ntsec
>              ^^^^^
> Don't overlook this setting with this problem.  Although I can't imagine why it
> would cause it, this has issued numerous changes that could cause this.

Given that I didn't have anything like this the last time, it can't be
related.


Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]

On 12 Oct 99, at 10:06, Andrew Dalgleish wrote:

> Let me guess - you are using NT's boot loader to multiboot, correct?

Well, if booting something different less than 1% of the time counts
as multibooting ...

> When you use the NT boot loader to boot DOS/95/98 it copies autoexec.bat
> and config.sys into c:\, and leaves them there the next time you boot
> into NT.
> NT does not execute autoexec.bat, but it does parse it for PATH
> statements.
> This means your NT environment may depend on what other OS you last
> used.

There's only one other OS, and it's only changing when I need to
test software with another Win version, which hasn't happened in a
_long_ time. So I don't see why the environment should change.
Indeed, the modification date of the autoexec.bat is from 1999-09-
20, more than three weeks ago.

Plus, this doesn't explain why changing PATH does not work,
which is the real problem (not whatever is in PATH before trying to
change it).

> If you add the following to the start of your cygwin.bat it might help
> pin down what is going on.

I'll probably try that if it happens again. One of the peculiarities is
that I know how to remove the problem, but not how to provoke it -
once it's removed, it stays removed, at least for some days.

> Do you also have a ~/.bashrc and/or ~/.bash_profile?

The latter. This is it:

#! bash
echo "profile speaking"
umask 022



Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Kai Henningsen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

On 11 Oct 99, at 5:21, Earnie Boyd wrote:

> --- Kai Henningsen <kai@cats.ms> wrote:
> -8<-
> > This is my CYGNUS.BAT:
> >
> > @ECHO OFF
> > SET MAKE_MODE=UNIX
> > SET
> >
> PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
> > SET CDPATH=
> > SET HOME=/home
> > SET CYGWIN=ntsec
>              ^^^^^
> Don't overlook this setting with this problem.  Although I can't imagine why it
> would cause it, this has issued numerous changes that could cause this.

Given that I didn't have anything like this the last time, it can't be
related.


Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: For the FAQ: NT PATH problems

[Andrew Dalgleish]

Let me guess - you are using NT's boot loader to multiboot, correct?
(You say you are using NT, but your path contains references to
C:\WIN95.US and C:\WIN98.US)

When you use the NT boot loader to boot DOS/95/98 it copies autoexec.bat
and config.sys into c:\, and leaves them there the next time you boot
into NT.
NT does not execute autoexec.bat, but it does parse it for PATH
statements.
This means your NT environment may depend on what other OS you last
used.
Personally I have a one-line autoexec.bat call another batch file
(autodos.bat, auto95.bat, etc) which does the real work.
Because autoexec.bat doesn't contain any path statements NT doesn't get
confused.
(Now this could go in the FAQ :-)

If you add the following to the start of your cygwin.bat it might help
pin down what is going on.
echo %PATH%
pause

Do you also have a ~/.bashrc and/or ~/.bash_profile?


Regards,
Andrew Dalgleish


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Chris Faylor]

On Mon, Oct 11, 1999 at 05:21:41AM -0700, Earnie Boyd wrote:
>--- Kai Henningsen <kai@cats.ms> wrote:
>-8<-
>> This is my CYGNUS.BAT:
>> 
>> @ECHO OFF
>> SET MAKE_MODE=UNIX
>> SET
>>
>PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
>> SET CDPATH=
>> SET HOME=/home
>> SET CYGWIN=ntsec
>             ^^^^^
>Don't overlook this setting with this problem.  Although I can't imagine why it
>would cause it, this has issued numerous changes that could cause this.

I don't see any reason for NTSEC to cause this problem.

Blaming ntsec for every problem that crops up is not really very productive.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: For the FAQ: NT PATH problems

[Earnie Boyd]

--- Kai Henningsen <kai@cats.ms> wrote:
-8<-
> This is my CYGNUS.BAT:
> 
> @ECHO OFF
> SET MAKE_MODE=UNIX
> SET
>
PATH=E:\gcc-2.95.1-mingw32\bin;E:\gcc-2_95-mingw32\bin\;E:\cygnus\cygwin-b20\H-i586-cygwin32\bin;%PATH%
> SET CDPATH=
> SET HOME=/home
> SET CYGWIN=ntsec
             ^^^^^
Don't overlook this setting with this problem.  Although I can't imagine why it
would cause it, this has issued numerous changes that could cause this.

> bash --login
> 
> This is the 'Path' system environment var definition:
> 
> E:\Perl\bin;%SystemRoot%\system32;%SystemRoot%;F:\Programme\Personal
>
Communications;f:\aintx;%SystemRoot%\system32\nls\ENGLISH;%SystemRoot%\system32\nls;E:\NTReskit
> 
> The first (and second) Cygwin window opened today had the
> following PATH:
> 
> PATH='/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal
>
Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/'
> 
> Then I added an empty user environment var PATH, and lo and
> behold, the next Cygwin window opened had:
> 
>
PATH='/gcc-2.95.1-mingw32/bin:/gcc-2_95-mingw32/bin/:/cygnus/cygwin-b20/H-i586-cygwin32/bin:/Perl/bin:/WINNT/system32:/WINNT:/f/Programme/Personal
>
Communications:/f/aintx:/WINNT/system32/nls/ENGLISH:/WINNT/system32/nls:/NTReskit:/cygdrive/w/:/cygdrive/z/:/cygdrive/y/:/cygdrive/x/:/cygdrive/c/WIN95.US:/cygdrive/c/WIN95.US/COMMAND:/cygdrive/c/WIN98.US/COMMAND:/cygdrive/c/WIN98:/cygdrive/c/WIN98/COMMAND:/f/READIBMW:/f/vim/vim55'
> 
> So: absence of this variable does not always produce the bug, but
> *if* the bug shows up, creating said variable removes it.
> 


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com