wine users - Oct 2001 - Environment in child processes

I've recently been trying to run the United Devices THINK agent under wine.
On installation, all was going well until the registration process tried to
connect to the UD server, when it failed to establish contact. Investigation
of the debug messages revealed that it was getting the address to contact vi
a call into msvcrt.getenv() which was returning the value "C:\WINDOWS"
for
all the values asked for. When I set shell environment variables for the
required values before running the registration process, everything worked.
I don't know where it gets these values from under native windows as that
requires no environment vars set.

When I then tried to run the client, it connected to the server fine, but
then spawned some child processes (appearing to run a DLL) which had the
same environment problem as I was initally experiencing, except all the
calls to getenv were returning ""C:=C:\PROG~FBU\UNIT~A1D".

Is there anything I have to do to ensure that child processes have the same
reported environment as the parent process, or am I barking up the wrong
tree altogether?

Apologies for the somewhat rambling mail - this is my first foray into using
wine.

Thanks in advance,


Simon

> When I then tried to run the client, it connected to the server fine, but
> then spawned some child processes (appearing to run a DLL) which had the
> same environment problem as I was initally experiencing, except all the
> calls to getenv were returning ""C:=C:\PROG~FBU\UNIT~A1D".
normally, child processes should inherit their parents' environment
which Wine version are you using ?
however, I see a potential pitfall in wine's implementation
could you trace with -debugmsg module, and send me the output just that
I 
check if it happens what I fear

A+
-- 
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle