Xref:	news-dnh.mv.net comp.os.msdos.djgpp:1857
Path:	news-dnh.mv.net!mv!news.sprintlink.net!gatech!swrinde!news.uh.edu!uuneo.neosoft.com!news!sandmann
From:	Charles Sandmann <sandmann AT praline DOT no DOT NeoSoft DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: CWSDPMI & enviroment variables
Date:	Thu, 31 Aug 1995 21:39:06 CDT
Organization:	NeoSoft Internet Services +1 713 968 5800
Lines:	21
References:	<DE5wIw DOT Cnt AT jade DOT mv DOT net>
Reply-To:	sandmann AT praline DOT no DOT NeoSoft DOT com
Nntp-Posting-Host:	praline.no.neosoft.com
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

> Does anyone know what enviroment variables CWSDPMI uses for its virtual ram
> directory and so forth.  

The only environment variable CWSDPMI beta 5 and earlier look at is:
 GO32TMP, or TEMP, or TMP to decide where to put the paging file
This functionality will be changed when I get around to it to use a 
different method.  This is left over from GO32 and I haven't had a chance
to handle configurable things yet.

> I'm using DJGPP beta 2, go32 is no longer needed.  Are all the go32 enviroment
> variables no longer needed, or does CWSDPMI and/or GCC use any of these.
> I can't get redirection to work if i set go32=2r1 ansi topline..... etc

The only environment variable which needs to be set in V2 is DJGPP (which
points to the DJGPP.ENV file).  Nothing in V2 pays attention to the GO32
environment variable.  All of that functionality has been moved to the
various subsystems.  In V2, you use mshell or redir commands for redirection;
ansi is automatically detected, emu location is in djgpp.env, etc.

V2 is much more modular - each piece can be tested in a standalone manner,
or can be swapped with other parts.

- Raw text -