Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!iuvax!silver!creps From: creps@silver.bacs.indiana.edu (Steve Creps) Newsgroups: comp.sys.ibm.pc Subject: Re: MSC spawn() problem Message-ID: <474@silver.bacs.indiana.edu> Date: Thu, 3-Dec-87 20:19:26 EST Article-I.D.: silver.474 Posted: Thu Dec 3 20:19:26 1987 Date-Received: Tue, 8-Dec-87 02:31:30 EST References: <149000015@inmet> Reply-To: creps@silver.UUCP (Steve Creps) Organization: Indiana University Computer Science Department Lines: 23 In article <149000015@inmet> ronw@inmet.UUCP writes: > >I believe that the Microsoft C Compiler has problems with environment >space when spawn-like library functions are used. Consider the following (deleted) >examine the environment variables with the SET command they appear fine >except there is a little string of garbage at the end of the list that >always contains the string ";C_FILE_INFO". To make matters worse, if you >attempt to use SET to change old variables or create new ones, they are >placed at the end of the list (after the garbage). When this happens, I don't think it's a bug; I think it's a feature, a feature of MS-DOS. When you spawn a new shell in DOS it should return the environment the same as before you spawned it, when you return from the new shell. That means a "set" will only have effect within the shell in which it's performed. That ";C_FILE_INFO" is probably something that is set to save the old environment. - - - - - - - - - Steve Creps on the VAX 8650 running Ultrix 2.0-1 at Indiana University. creps@silver.bacs.indiana.edu "F-14 Tomcat! There IS no substitute."