InstallAware 17 Compression Error

Postby **FrancescoT** » Tue Sep 17, 2013 8:59 am

Dear Iamfromk2,

The IA trial doesn't have any limitation.

Honestly, I never used a SSD drive with InstallAware and anyway, as with any other application that requires frequently disk usage, a SSD drive is not the most appropriate.

Generally, SSD drives should only keep the OS and apps that require the quickest loads ( ... having care to disable the page file because it creates unnecessary read/write cycles), but applications that require disk access should be left on a mechanical drive.

Hope this helps you.

Regards

donbrookes · Postby **donbrookes** » Wed Oct 09, 2013 5:42 pm

I am getting the same thing running the demo. I have attached my build dump.
If I switch the compression to the middle, it builds fine.

I am running WIN 7 64, IA Developer 17 (Demo)

Postby **FrancescoT** » Thu Oct 10, 2013 10:11 am

Dear Donbrookes,

which IA 17 version are you using?
your system configuration?

Regards

MortSkil · Postby **MortSkil** » Tue Nov 26, 2013 6:07 am

I got the same compression error as described above when building "Single File".
I tried the procedure suggested by Markus Dietrich. The faulting module changes, but I still get

Created Windows Installer database
Built installation executable
Injected setup languages
Storing support files: componentstree.dfm (0%)
Injected runtime files
Compressing install: mFileBagEXE.dll (49%)
Error during build: Unable to build setup files: Insufficient memory

Are there any recommended ways avoid this problem?
My CD or DVD build goes fine.

I am using InstallAware 17 (Build 8.12.13) Wide, running on a Windows 7 PC w 24 GB RAM and 64-bit operating system, 2 processors, 8 cores.

Postby **FrancescoT** » Tue Nov 26, 2013 12:16 pm

Dear MortSkil,

this specific issue for which this topic was started, It was fixed by the IA 17.02 updated and for what I see by the your product version, you already have it installed.

So I suppose that "probably" your problem is caused by something else.

I perfectly understand that what I am going to suggest you it is not the most desirable suggestion ... but have you tried if the same happen using a different machine?

Regards

MortSkil · Postby **MortSkil** » Wed Nov 27, 2013 4:59 am

That sounds reasonable. :-)

I will give it a try on another project as well as another machine. If the problem persists, I'll post a new topic.

We are also entitled to an upgrade to InstallAware 18, and will install the new version as soon as possible.

Regards,
Morten

Postby **FrancescoT** » Wed Nov 27, 2013 1:11 pm

Let me know how it goes.

Regards

MortSkil · Postby **MortSkil** » Tue Dec 03, 2013 6:15 am

I got a tip from a colleague that quitting most applications but IA could help in this case.
Just now, I ran IA after closing Lotus Notes and VS, and the project built just fine. Had to restart IA first, though, but not necessary to try on another machine.
The same colleague mentioned that the out of memory problem has been reported with IA 17 and fixed in IA 18. Downloading IA 18 now.

Morten

mikKummerfeld · Postby **mikKummerfeld** » Thu Dec 12, 2013 3:03 pm

Same Problem while moving from 15 to 18....with new license.

Every 10 minutes a new error

Great quality assurance.....*applause*
Sorry I am angry...

MortSkil · Postby **MortSkil** » Fri Dec 13, 2013 2:08 am

Still not installed IA 18, but I manage even with IA 17.
If the memory problem occurs, I can quit all VS or VMware instances or other applications to release memory.
Then restart IA, and the build works, at least for some time. When the memory error occurs again, I just follow the same procedure.

Kind of annoying, but at least I am able to create the installers I want.

Is IA still basically a 32 bit application, so that installing vast amounts of memory won't help at all?

Thanks,

Morten

Postby **FrancescoT** » Fri Dec 13, 2013 1:17 pm

Dear mikKummerfeld,

....
Every 10 minutes a new error Great quality assurance.....*applause*
Sorry I am angry...

if you only post a spot of your current mood ... how do you pretend to receive help?
If you try to be less sarcastic, it would be preferable.

Regards

Postby **FrancescoT** » Fri Dec 13, 2013 1:23 pm

MortSkil wrote:Still not installed IA 18, but I manage even with IA 17.
If the memory problem occurs, I can quit all VS or VMware instances or other applications to release memory.
Then restart IA, and the build works, at least for some time. When the memory error occurs again, I just follow the same procedure.

Kind of annoying, but at least I am able to create the installers I want.

Is IA still basically a 32 bit application, so that installing vast amounts of memory won't help at all?

Thanks,

Morten

Dear Morten,

Yes, it is a native 32 bit application.

Anyway, I am a developer as well and I use a dedicated development machine for all my jobs ... where only SDKs and Dev Tools are installed.

Regards