Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	"Chris Bates" <bates AT acusoft DOT com>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	Cygwin peculiarities
Date:	Tue, 14 Mar 2000 15:14:51 -0500
Message-ID:	<NDBBJJPOEMBAMABFHNEPGEDBCAAA.bates@acusoft.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300

I am running cygwin b20 under NT 4 Service Pack 6 and am having some unusual
problems that seem to be memory related.  When I run an executable from the
command line the use of my environment variables (previously set at the cmd
prompt) varies dependent upon how many parameters I pass to the program.
Some of them are not recognized if I have more parameters passed to the exe.

I know that sounds vague but it is very consistent.  I didn't think there
could be a cygwin problem in this until I noticed that some cygwin specific
commands still work even after I exit from cygwin.  For example, I can exit
from cygwin back to the cmd (DOS) prompt and still use the commands ls and
pwd.

I would greatly appreciate any feedback you might have on this question.

Thanks.

Chris Bates


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -