GGWALTER
19th April 2005 06:11 UTC
Nsis And Xphome Fat32
I have encountered some problems using NSIS on XPHOME (FAT32): it seems thar SYSTEM plugin does not support NSIS variables like $TEMP under FAT32; also you have to create standard DOS-like names directory if you have to call your own DLLs during installation.
Have anyone encountered troubles like this ?
Afrow UK
19th April 2005 09:44 UTC
I can say that I never have. I have XP (Pro) running on this machine, with two drives both of which are FAT32.
Probably a silly question, but are you putting quotes around paths in case they contain spaces?
-Stu
GGWALTER
19th April 2005 10:01 UTC
The problem is not about blanks, example: during installation I create a directory named C:\VERYLONGNAME that contains some DLLs; "System::" fails to load DLLs; but if I use a directory named C:\SHORT it works fine !!
DrO
19th April 2005 13:18 UTC
on fat32, the folder/file paths are limited to a maximum length of 260 characters (my guess since you mention 'C:\VERYLONGNAME' is that your path is too long)
-daz
Afrow UK
19th April 2005 13:54 UTC
Use GetFullPathName /short "path" to convert
-Stu
DrO
19th April 2005 17:13 UTC
if the 260 limit is passed for a fullpath then the shortpath version i think would be exceeded as well (think it's something like 90 chars or something silly due to the 8.3 formatting). isn't the filesystem just great to deal with :)
-daz