Detect Wine environment out of NSIS?

[Hadron]

Hi,

I tried to install a custom application under Wine and it seems like the installation procedure has to be slightly different (e.g. under Wine Fedora 9 no PATH environment variable is set).

So my question is how can I detect that the NSIS installer is running under wione or under a native Windoze-system?

Had

[vitamin]

Hi,

I tried to install a custom application under Wine and it seems like the installation procedure has to be slightly different (e.g. under Wine Fedora 9 no PATH environment variable is set).

This shouldn't happen. It's should _always_ be set. Remove ~/.wine directory and try again. If you still have a problem please open a bug report in bugzilla.

Of course make sure you using the latest Wine version.

So my question is how can I detect that the NSIS installer is running under wione or under a native Windoze-system?

Simple answer - DO NOT ever do that. You will create broken installer. As soon as Wine will get fixed your installer will break.

[Hadron]

I noticed the problem with PATH using the standard packages of Fedora 9. Unfortunately I can't switch to the VCS version because I have to used a defined environment.

Independent from that it is not only the PATH-problem: it looks like I do _not_ have to install some DLLs within the Wine environment that are necessary when native Windows is used. So at least for that it seems like there are differences.

Thx

Had

[Hadron]

Just an other argument for the need to detect the Wine environment out of NSIS:

Currently there are some additional drivers/setups installed within my NSIS setup that are not necessary. And one of these sub-setups fails to be installed under wine, a subprocess of it crashes in background and causes the setup itself to issue an error message.

So I think there are two good reasons for giving a possibility to detect the Wine environment ouf of NSIS:

- installing of drivers that are useless under Wine can be avoided
- installing of not working and not required data/setups can be avoided

Possibly a specific environment variable that tells about Wine is a solution?

[jeffz]

Just an other argument for the need to detect the Wine environment out of NSIS:

Currently there are some additional drivers/setups installed within my NSIS setup that are not necessary. And one of these sub-setups fails to be installed under wine, a subprocess of it crashes in background and causes the setup itself to issue an error message.

So I think there are two good reasons for giving a possibility to detect the Wine environment ouf of NSIS:

- installing of drivers that are useless under Wine can be avoided
- installing of not working and not required data/setups can be avoided

Possibly a specific environment variable that tells about Wine is a solution?

Please a bug report for the program which crashes, if you can isolate it and give further detail in the report that would be great.

[Hadron]

Hi jeffz,

the program that is crashing during installation is a setup that tries to install drivers for a hardware that in no case can be used under Wine, so it is useless in every case. But I'll file a report.

Had