573 posts
EncodePointer function's MSDN page.Originally Posted by Yathosho View Posti wonder where you even found that, such things should be mentioned on the website. anyway, i'm only using win 2003 because i have no legit copy of windows xp. so there should be no troubles when using xp (sp3)?
This is not a limitation of NSIS or Unicode NSIS in general. It's just a limitation of the Visual C++ 2010 CRT libraries. And, as jimpark switeched to VS2010 for his latest builds, these builds will now require Windows XP with SP-2 or later. To make it clear again: This only applies to MakeNSIS, not to the rersulting installer EXE. The created installer EXE even runs on Windows 2000...Originally Posted by Yathosho View Posti wonder where you even found that, such things should be mentioned on the website. anyway, i'm only using win 2003 because i have no legit copy of windows xp. so there should be no troubles when using xp (sp3)?
makensis - < Examples\example1.nsi
that is the biggest issue. and branching won't help - in fact i think that it's gotten us into this mess to begin with as people are using the unofficial unicode version yet expect support for it, etc. doing another branch with all of the issues i mentioned is just going to be even more of a pain for everyone concerned, ignoring the fact of who is going to do it?Originally Posted by DrO View Postas there's no proper focus on getting things done
even open-source projects need decisions and people who make them. so why not let the community decide which direction nsis will go or who will be the decision-makers? that only leaves the question who should be able to vote.Originally Posted by DrO View Postas there's no proper focus on getting things done, different people want it to be done in different ways [...] there's no consensus on how it should be done
!searchreplace PRODUCT_VERSION_DATE "${LAMEXP_DATE}" "-" "."I:\>upx --best --force "C:\DOCUME~1\User\LOCALS~1\Temp\exehead.tmp"
Ultimate Packer for eXecutables
Copyright (C) 1996 - 2013
UPX 3.09w Markus Oberhumer, Laszlo Molnar & John Reiser Feb 18th 2013
File size Ratio Format Name
-------------------- ------ ----------- -----------
upx: C:\DOCUME~1\User\LOCALS~1\Temp\exehead.tmp: CantPackException: superfluous data between sections
Packed 1 file: 0 ok, 1 error.
...
!define SND_ASYNC 1
!define SND_FILENAME 0x20000
!define SND_LOOP 8
!define SND_NAME "InstallTheme.wav"
ReserveFile "${NSISDIR}\Plugins\system.dll"
SetOutPath "$TEMP\${MOD_NAME_BASE} Installation2\bgi_ground"
ReserveFile "${SND_NAME}"
File "${SND_NAME}"
System::Call 'Winmm::PlaySound(t"$TEMP\${MOD_NAME_BASE} Installation2\bgi_ground\${SND_NAME}", i0, i${SND_FILENAME}|${SND_ASYNC}|${SND_LOOP})'
... Have you tried v3.0? It should work there.Originally Posted by MaGoth View PostPlease tell me the right to write this code in the Unicode(v.2.46.5)?
Have you tried v3.0? It should work there.I do not use this version.
I don't remember the details for the Unicode forks system plugin but it has problems when there are 3 versions of a function and PlaySound is one of these special 3 version exports. Try changing PlaySound to PlaySoundW and t to w.The problem resolved, in my case it was necessary to swap quotation marks, ' ' inside..
I'm sorry, I was not specific in my question. I was referring to the Unicode version of makensis. I understand it is not official but since a lot of comments on this thread are about it I just thought I would ask here.Originally Posted by JasonFriday13 View PostYes, I helped do the NSIS 3 posix support a year ago. Posix builds are officially supported since 3.0b0.
I used makensis (packed with NSIS 3.0b0) on Windows 7 and the compiled installer failed to show Arabic characters correctly, it just showed ANSI. makensis on Linux is at version 2.46 and also didn't encode properly... so I feel pretty confused right now.Originally Posted by JasonFriday13 View PostThe unicode fork by scratchpaper.com does not support posix, so the main reason to use NSIS 3 is for unicode support. Everything up to 2.46 is ansi based.
I feel slightly embarrassed to admit that in my entire hunt for unicode support, I failed miserably to read any of these:Originally Posted by JasonFriday13 View PostYou did read the documentation right? In NSIS 3, unicode support is turned on using 'Unicode True' in the script.
Will do, for sure.Originally Posted by JasonFriday13 View PostProbably because it's still beta software. There is nothing stopping you from compiling the source on linux, you just need scons, if you need zip2exe: windows zlib files, and if you need NSIS Menu: wxWidgets.