OK .. Bob ..

 BJ> My test install of GCC 3.2.1 (from the GCC321.zip 
 BJ> file) did *not* modify config.sys.....  :|  .  So, EMX 
 BJ> still works, but the paths aren't in there to allow 
 BJ> GCC (and related utilities) to run....  

But where did it put the required items for GCC?  Did it put them in the
#:\emx diretory?   That's what I sort of gleaned from reading the readme1st
text file was going to happen.

OK, that being so, I suppose it would modify-overwrite-update whatever was
in the EMX directory to the latest and greatest, together with adding
whatever down-drill it needed for the GCC321 variant to work.

That being so, does what I posted also still have to be in the CONFIG.SYS
file in order to get things going?  Or, conversely, in this implementation
of GCC, does the application suite teach itself where the EMX stuff is, and
.. in your case and mine ... if we install GCC in other than C:, we will
get a non-functional operation related to EMX?

If that's true, we are right back to your original question about how do we
move this off C:, yet keep C:\emx, so as to not mung everything else that
depends on it, no?


--> Sleep well; OS/2's still awake! ;)

Mike {at} 1:117/3001




--- Maximus/2 3.01