From:	Andrew Cottrell <andnews AT ihug DOT com DOT oz DOT au>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: gawk 3.1.1 DJGPP v2.04 on Windows 2000 Pro problem using system() function and LFNs
Date:	Sun, 26 Jan 2003 16:26:11 +1100
Organization:	ECLiPSE
Lines:	37
Message-ID:	<mjr63vohi8bavc541fptejdvomm1698qb7@4ax.com>
References:	<b0ttav$pnu$2$8302bc10 AT news DOT demon DOT co DOT uk>
NNTP-Posting-Host:	p232-tnt8.syd.ihug.com.au
Mime-Version:	1.0
X-Trace:	lust.ihug.co.nz 1043558775 6406 203.173.147.232 (26 Jan 2003 05:26:15 GMT)
X-Complaints-To:	abuse AT ihug DOT co DOT nz
NNTP-Posting-Date:	Sun, 26 Jan 2003 05:26:15 +0000 (UTC)
X-Newsreader:	Forte Agent 1.92/32.572
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

>gawk 3.1.1 seems to have a problem when using the system() function
>on Windows 2000 Pro and LFNs.  I have been using the version from
>the v2.04 set from the Rice download page at
Please ensure that you read the info on the page and try to follow it.

>Here's an example session running is a W2K "dos" window (i.e.,
>not using a full DJGPP environment):
Are you using cmd.exe or command.com?

What is the date of gawk.exe?
What do you have comspec set to? 

..SNIP..
>i.e., using system("cmd /c whatever") appears to work OK, but
>system("whatever") doesn't.

>Previous versions of DJGPP gawk have run OK in Windows "DOS"
>boxes for me in the past.  
What are the previous versions? Are these from a previous downlload
from clio?

> Is this a known problem with this
>combination of "DOS" and LFNs?  If so is it a DJGPP or W2K
>problem?  If the former is there a bug report in hand (I
>couldn't find one when I did a quick search at
>www.delorie.com/djgpp )
Please check back at the unofficial 2.04 page in a few days for the
next update and give it another try. There are a few problems with
find that was uploaded in Decmber and Janurary which have since been
fixed in a build I did last week usign the latest LIBC code. 

If previosu 2.04 gawk versions worked then I expect that this should
be fixed in the enxt update. If you cannot wait then email me at the
address given on the 2.04 page.


Andrew

- Raw text -