From: address@is.invalid   
      
   Zaidy036,   
      
   > One way is to use SETX which provides an environmental variable for   
   > another batch to read.   
      
   Ahhh... no.  That command writes into the top-level user / system   
   environment, and thereby makes that variable evailable to *all* programs   
   that are started *after* it.   
      
   There are a few problems with that :   
      
   1) I only need the process which started the batchfile to receive the   
   changes.   
      
   2) As my process has been started before running SETX it will not receive   
   the changes.   
      
   And there is the likelyhood that putting a few what /should/ be local to my   
   process environment variables there could cause problems for/with other   
   programs.  Including possibly overwriting a variable which I should leave   
   alone.   
      
   Thanks for the suggestion though.   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)