[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  3835
Date     :  2003-02-24
Author   :  Garry Deane
Subject  :  Re: Errorlevel is not the same as an exit code.
Size(KB) :  1


--- In xxcopy@yahoogroups.com, Kan Yabumoto  wrote:

> As far as I know, what you are doing here is equivalent to
> calling "System("SET XXX=1234"). But, this is not the answer
> because it does not modify the parent's environment variable.
> Therefore, as soon as the program which calls the INT2E function
> (e.g., XXCOPY16) terminates, the environment variable just set
> will be gone. In other words, the INT2E technique you mentioned
> would not change the parent's environment variable and therefore,
> it does not work for the purpose we are discussing here.
>

I must admit it's been a LONG time since I've dabbled in system calls 
and I only have a few half documented notes on INT 2E from way back 
without the supporting articles. My notes referred to INT 2E 
modifying the master environment and after a bit of further 
investigation, this is true but not 100% reliable so probably of no 
great use. The following links 
(http://www.snippets.org/snippets/dos/ENVIRON+TXT.php3 & 
http://www.snippets.org/snippets/dos/GLBL_ENV+C.php3) discuss the 
issues.

> Do you know CONSET's author's Email address?
> If so, please let me know personally (It is not
> appropriate to publish one's Email address in this
> forum). I'm not interested in asking his full source
> code. All I want is to confirm my strong suspicion
> that his magic is not a clean Win32 API but a messy
> kludge.

I'll reply privately.

Garry



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.