How to know which env vars a software wants

xekhz · Post by **xekhz** » Fri Mar 14, 2008 11:42 am

Hello ppl.
Im trying to install an aplication and for some reason ir says.
"Cannot get enviorment variables"
I spoke with the developer and he told me that it is because i dont have microsoft DAC installed.
I installed it and the problem persists.
I need to know how to see which ENV vars the software wants in order to create them.

It is not a wine problem because I get the same error instaling in a XP Home edition

Thanks for the help in advance
[email protected]

Dan Kegel · Post by **Dan Kegel** » Fri Mar 14, 2008 12:06 pm

On Fri, Mar 14, 2008 at 9:42 AM, xekhz <[email protected]> wrote:

Im trying to install an aplication and for some reason ir says.
"Cannot get enviorment variables"
I spoke with the developer and he told me that it is because i dont have microsoft DAC installed.
I installed it and the problem persists.
I need to know how to see which ENV vars the software wants in order to create them.

It is not a wine problem because I get the same error instaling in a XP Home edition

What Windows version does the app install on properly?

Figuring out why an installer is unhappy is a bit of an art.
Mostly, we use log files to do that. So, for example,
get the installer to fail
WINEDEBUG=+text,+file,+reg,+relay wine setup.exe > /tmp/log.txt 2>&1
Then look at the log file, search for the error message, and
then read backwards and try to guess which failed call might
have triggered the error. It's not always easy!
- Dan

xekhz · Post by **xekhz** » Mon Mar 17, 2008 7:58 am

With the help of Dan Kegel, the problem was solved.

In the relay log, the files
c:/windows/system32/drivers/etc/services
c:/windows/system32/drivers/etc/hosts

Must exist.

A simple touch ~/c:/windows/system32/drivers/etc/{services,host}
did the trick
Thanks Dan

This was not a WINE problem but a generic problem maybe from powerbuilder.

In XP Home edition and starter edition I had the same problem.
In those i used to install informix sdk 2.7.0 and the problem was solved.

Dan Kegel · Post by **Dan Kegel** » Mon Mar 17, 2008 8:34 am

On Mon, Mar 17, 2008 at 5:58 AM, xekhz <[email protected]> wrote:

A simple touch ~/c:/windows/system32/drivers/etc/{services,host}
did the trick

xekhz also wrote:
"in windows Home edition and starter the problem was the same
but in those i installed informix sdk 2.7 and problem solved"

So perhaps this will help other Informix-based apps?

vitamin · Post by **vitamin** » Mon Mar 17, 2008 8:45 am

Dan Kegel wrote:On Mon, Mar 17, 2008 at 5:58 AM, xekhz <[email protected]> wrote:
A simple touch ~/c:/windows/system32/drivers/etc/{services,host}
did the trick
xekhz also wrote:
"in windows Home edition and starter the problem was the same
but in those i installed informix sdk 2.7 and problem solved"

So perhaps this will help other Informix-based apps?

Should probably add these files to Wine tree. "hosts" shouldn't need anything more then standard 127.0.0.1 localhost
And services should be empty.

Dan Kegel · Post by **Dan Kegel** » Mon Mar 17, 2008 9:06 am

vitamin <[email protected]> wrote:

A simple touch ~/c:/windows/system32/drivers/etc/{services,host}
So perhaps this will help other Informix-based apps?
Should probably add these files to Wine tree. "hosts" shouldn't need
anything more then standard 127.0.0.1 localhost
And services should be empty.

Yep. Filed as
http://bugs.winehq.org/show_bug.cgi?id=12076