X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
Message-ID:	<29950134.post@talk.nabble.com>
Date:	Wed, 13 Oct 2010 00:14:31 -0700 (PDT)
From:	Autotoonz <david DOT topley AT acma DOT gov DOT au>
To:	cygwin AT cygwin DOT com
Subject:	Re: nodosfilewarning not working
In-Reply-To:	<4CB5591A.4000901@veritech.com>
MIME-Version:	1.0
References:	<29948673 DOT post AT talk DOT nabble DOT com> <20101013011127 DOT GA14097 AT ednor DOT casa DOT cgf DOT cx> <29948823 DOT post AT talk DOT nabble DOT com> <20101013014122 DOT GA14285 AT ednor DOT casa DOT cgf DOT cx> <29948971 DOT post AT talk DOT nabble DOT com> <20101013053646 DOT GA15747 AT ednor DOT casa DOT cgf DOT cx> <29949816 DOT post AT talk DOT nabble DOT com> <4CB5591A DOT 4000901 AT veritech DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Lee D. Rothstein wrote:
> 
> DOS 'setx' in batch file "A" will affect all subsequently invoked batch 
> files from outside "A".
> Is this what you did? 
> 

No. I used the DOS set command, as discussed. This probably failed due to a
typo on my part, but I'm uncertain.



> 'setx' can also be invoked from shell scripts but 
> still only impacts
> subsequently invoked shells. In both cases, the results obtain even 
> after reboot.
> 

Thankyou for this info. Setx will be useful for me in the future because our
Windows PCs are locked down, and I cannot modify any Windows System
variables via the GUI.



> The GUI way to invoke these "environmental variables is:
> 
> Control Panel (Classic View) / System / Advanced Systems Settings / 
> Environment Variables / ...
> 

As discussed, I'm unable to modify env variables this way because Windows
has been locked down.
I will be using the set command instead to suppress the warning on
individual scripts. This now appears to work correctly with CYGWIN, so my
problem seems to have been solved.
Cheers
-- 
View this message in context: http://old.nabble.com/nodosfilewarning-not-working-tp29948673p29950134.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -