Message-ID:	<9160E2E0D3C0D1118C9C0060973136625D28@mail.rkk.cz>
From:	"Holejsovsky, Pavel" <PHolejs AT rkk DOT cz>
To:	"'djgpp-workers AT delorie DOT com'" <djgpp-workers AT delorie DOT com>
Subject:	FW: PATH and Path
Date:	Thu, 2 Apr 1998 14:27:34 +0200
MIME-Version:	1.0

> Answer is simple;
> 
> 	On NATIVE NT Box, there are really Path and ComSpec variables.
> But djgpp programs don't use NATIVE NT Box, it uses 16bit subsystem,
> and this subsystem sets PATH and COMSPEC as old-fashioned dos did. So
> 
> 	If you run 'cmd.exe' (Win32 console application) and type 'SET',
> you will see 'Path=...' & 'ComSpec=C:\WINNT\system32\cmd.exe'
> 
> 	BUT
> 
> 	If you run 'command.com' (16bit application) and type 'SET', you
> will see 'PATH=...' & 'COMSPEC=C:\WINNT\SYSTEM32\COMMAND.COM'
> 	and that is what DJGPP program sees...
> 
> bye
> Pavel
> 
> -----Original Message-----
> From:	Eli Zaretskii [SMTP:eliz AT is DOT elta DOT co DOT il]
> Sent:	Wednesday, April 01, 1998 6:46 PM
> To:	djgpp-workers AT delorie DOT com
> Subject:	PATH and Path
> 
> Boy, is it good to NOT know some things!
> 
> I have recently learned that on NT box, you have Path instead of PATH
> and 
> ComSpec instead of COMSPEC.
> 
> Given this mess, how does DJGPP work for those of you who use NT?  I'd
> 
> expect everything in DJGPP to fail, beginning with GCC itself and
> Make, 
> in that situation.  I really cannot sleep until I hear the solution to
> 
> this puzzle ;-).

- Raw text -