You are here

Home » Forums » Support Forums » PortableApps.com Platform

Stuck on 'Generating Installer Code' | [Also] Error: resolving install function "Nsis2Io"

12 posts / 0 new
Log in or register to post comments
Last post
February 11, 2010 - 6:20am
#1
Panarchy
Offline
Last seen: 13 years 7 months ago
Joined: 2008-02-15 22:24
Stuck on 'Generating Installer Code' | [Also] Error: resolving install function "Nsis2Io"

Hello

I'm stuck on 'Generating Installer Code'. (format wasn't correct, pressed yes to all the prompts)

Any ideas on how I can get past this step? (been stuck there with no progress for over an hour)

I've tried manual compilation with the included MakeNISW, however got the following (after troubleshooting all I could);

Processed 1 file, writing output:
Adding plug-ins initializing function... Done!
Error: resolving install function "Nsis2Io" in function "mui.FinishPre_151.5.9"
Note: uninstall functions must begin with "un.", and install functions must not
Error - aborting creation process

However I can't find either "Nsis2Io" nor "mui.FinishPre_151.5.9" in any of the files...

Please help me solve this/these problems.

Thanks in advance,

Panarchy

Top
February 11, 2010 - 7:00am
Simeon
Simeon's picture
Offline
Last seen: 8 years 11 months ago
DeveloperTranslator
Joined: 2006-09-25 15:15
Hm

Do you have everything in the right place as required by the PortableApps.com Format Spec?

Most likely you have something missing. Unfortunately its not easy to debug these errors.

"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate

Top
February 11, 2010 - 7:53am
John T. Haller
John T. Haller's picture
Offline
Last seen: 1 hour 37 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Parenthesis?

Are you, by chance, using parenthesis in your DisplayVersion in appinfo.ini? I just found a bug related to that that causes the installer to hang. I'm working out the particulars still.

Sometimes, the impossible can become possible, if you're awesome!

Top
February 12, 2010 - 12:07am
(Reply to #3)
Panarchy
Offline
Last seen: 13 years 7 months ago
Joined: 2008-02-15 22:24
ERROR: AppInfo.ini - Control - Start is missing.

Hmm, thanks. That fixed it.

However I'm now getting this error;
ERROR: AppInfo.ini - Control - Start is missing.

I've checked the file, the line is there, with the correct .exe name. I've even tried copying that .exe into every related sub-directory, to no avail.

Please help me resolve this final issue.

Thanks in advance,

Panarchy

Top
February 12, 2010 - 12:14am
(Reply to #4)
Chris Morgan
Chris Morgan's picture
Offline
Last seen: 8 years 3 months ago
Joined: 2007-04-15 21:08
Like this

Your application directory is AppNamePortable; you should have an AppNamePortable.exe in that directory. Then in App\AppInfo\appinfo.ini there should be a section [Control] with a value Start=AppNamePortable.exe.

I am a Christian and a developer and moderator here.

“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1

Top
February 12, 2010 - 12:33am
(Reply to #5)
Panarchy
Offline
Last seen: 13 years 7 months ago
Joined: 2008-02-15 22:24
Oh, I thought it was like an

Oh, I thought it was like an environmental variable within the documentation, for us to replace with the name of our .exe

*Tries your method now

Top
February 12, 2010 - 12:45am
(Reply to #6)
OliverK
OliverK's picture
Offline
Last seen: 2 years 3 months ago
Developer
Joined: 2007-03-27 15:21
of course, it could be due to

of course, it could be due to the "crazy" compression on the installer. I can't compile with my desktop anymore. I know its only 512 megabytes, but that shouldn't matter!

I does compile fine on my vista laptop. With 3gb of ram.

Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world

Top
February 12, 2010 - 11:30am
(Reply to #7)
Bruce Pascoe
Offline
Last seen: 11 years 8 months ago
Joined: 2006-01-15 16:14
Hmm

I don't know if this is what the installer is using, but I can tell you that LZMA at the "ultra64" (64MB dictionary) level requires 676MB (!) of RAM to compress.

Top
February 12, 2010 - 5:28pm
(Reply to #8)
OliverK
OliverK's picture
Offline
Last seen: 2 years 3 months ago
Developer
Joined: 2007-03-27 15:21
level requires 676MB (!) of

level requires 676MB (!) of RAM to compress.

! is right! I really don't care to have to get my laptop and boot it to create a installer.

Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world

Top
February 12, 2010 - 9:19pm
(Reply to #9)
computerfreaker
computerfreaker's picture
Offline
Last seen: 12 years 2 weeks ago
Developer
Joined: 2009-08-11 11:24
The PA installer, from what I

The PA installer, from what I can tell, uses LZMA with a 32MB dictionary (that's what's specified in the launchers, at least). Pretty slow, but absolutely a killer size-wise: a 40 MB app becomes 5-10 MB, and the smaller the filesize, the more likely the file is to be downloaded (I know from personal experience with dialup; if a file was over 5 MB, I'd pass on it unless I absolutely needed it, which wasn't usually the case).
Sure, it takes more RAM to create the installer, but users will thank you for it afterward.

"The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."

Top
February 13, 2010 - 12:02am
(Reply to #10)
John T. Haller
John T. Haller's picture
Offline
Last seen: 1 hour 37 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
That's Why

That's why we use the high compression in the installers. 1GB of RAM isn't really too much to ask from a developer box these days. Especially since 1GB of RAM for many old systems is only 20 bucks.

Sometimes, the impossible can become possible, if you're awesome!

Top
February 13, 2010 - 10:10am
(Reply to #11)
Bruce Pascoe
Offline
Last seen: 11 years 8 months ago
Joined: 2006-01-15 16:14
...

Ah, yeah, 32MB dictionary requires around 350 MB to compress, I think. That's not terribly much to ask for these days.

Top
Log in or register to post comments