[NSIS-Bugs] [ nsis-Bugs-848173 ] Failing on WINE

[SourceForge.net <no...@so...>]

Bugs item #848173, was opened at 2003-11-24 12:07
Message generated for change (Comment added) made by kichik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=848173&group_id=22049

Category: General
Group: 2.0 Beta Series
>Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Amir Szekely (kichik)
Summary: Failing on WINE

Initial Comment:
Hi,

when I run a setup created with v2.0b4 on Linux using 
WINE, I get an error: "Error! Can't initialize plug-ins 
directory. Please try again later.".
I found out, that it is only when TEMP variable is set 
to /tmp (which is Linux file system). When setting TEMP 
to a fat32 drive, it works.
Can you tell me what API call(s) will have to fail to get 
this error message? Maybe it can be fixed on either NSIS 
or WINE side...

Thank you,
Genrot


----------------------------------------------------------------------

>Comment By: Amir Szekely (kichik)
Date: 2003-11-27 18:50

Message:
Logged In: YES 
user_id=584402

On second thought, it was supposed to use 
C:\Windows\Temp if the %TEMP%/%TMP% was invalid... Yet 
another check...

Still better than littering the hard disk as it was probably 
doing in b3.

----------------------------------------------------------------------

Comment By: Amir Szekely (kichik)
Date: 2003-11-24 14:19

Message:
Logged In: YES 
user_id=584402

It fails because NSIS validates all paths to make sure they 
are valid Windows paths. Especially the temporary folder, 
without which installers using solid compression will not work 
and plug-ins will not load.

There isn't any specific API function failing on WINE's side, 
it's just the fact that it allows to mix *nix paths with 
Windows paths. I think this is a bad idea, cool feature, but a 
bad idea if you want to retain full compatibility.

If you want to change this behavior on the NSIS side take a 
look in the function validate_filename in 
Source\exehead\Util.c.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373085&aid=848173&group_id=22049