I was recently creating an installer that had some post install code associated with it. It kept failing to compile because of the post install code. After some messing around with the code it turned out that the install code was formatted for unicode and while creating the installer this cause an error.
There has been a lot of talk about moving away from ANSI and towards unicode. Shouldn't the installer support unicode in the PortableApps.comInstallerCustom.nsh file?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Did you try PortableApps.comInstallerU_1.0.3_Development_Test_2
https://portableapps.com/node/21879
It's on the bottom of the topic
Or for a direct link:
http://www.mediafire.com/?ym20gmozmk4
Is this about CUESplitterPortable ?
Formerly Gringoloco
Windows XP Pro sp3 x32
I actually did not try that. I didn't see the topic, I was just using the regular PortableApps.comInstaller from the development page. Thanks for the heads up.
CUESplitter is actually working fine and I didn't have to do anything with the install to make it work properly. I was messing around with RevoUninstaller trying to get it to prompt you to run with Admin rights. The current launcher neglects that, and if you don't launch as Admin, it just closes without letting the user know.
Please do let me know if you experience any behavior difference between this installer and the original !!! (and same for the Unicode NSIS ofcourse)
Even if you are not sure it's related !
Thanx
Formerly Gringoloco
Windows XP Pro sp3 x32
You can't use the Unicode PA.c Installer for any official releases yet. But we will be switching to it in the near future.
Sometimes, the impossible can become possible, if you're awesome!