Filesize Limitations - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

treadmill
Posts: 7
Joined: Mon Sep 24, 2012 9:41 pm

Filesize Limitations

Hi,

I'm new to the AI and the forum....

I'm trying to include an 8GB SQL script file into my project. I noticed that if I add it as a temporary file, AI will not build the project and reports a "bad allocation" error, no other error detail is reported.

Secondly, if I add the file into Application Folder and then reference that SQL script to execute via a BAT file (which works BTW) the project builds and it splits the SQL file into 2GB file chunks. However, upon running the installer, it appears that when it uncompresses the EXE and spits out the 2GB files, it doesn't actually put them back together as one 8GB file, though it does appear to be doing just that in the log file.

Under Media I chose the options:- Single EXE setup (resources inside) and "Archive installation files using LZMA compression.

I've also attached the log file of the installation. The SQL file in question is called "hes-final-release-v1.sql" which you will see in the log.

The installer is running on Windows 7 64-bit with 4GB RAM.

What's going on and how do I resolve this issue?
Attachments
package.zip
Log of AI installer
(220.52 KiB) Downloaded 280 times
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Filesize Limitations

Hi and welcome to Advanced Installer forums,
However, upon running the installer, it appears that when it uncompresses the EXE and spits out the 2GB files, it doesn't actually put them back together as one 8GB file, though it does appear to be doing just that in the log file.
That's a very large file indeed and I'm afraid the only solution is running it through the command line like you tried. What is your current related concern since you already use LZMA and it works? If you didn't already know, Advanced Installer supports packing files larger than 2GB only if the "Place files unpacked next to the MSI database" option or LZMA compression is used.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
treadmill
Posts: 7
Joined: Mon Sep 24, 2012 9:41 pm

Re: Filesize Limitations

mihai.petcu wrote:Hi and welcome to Advanced Installer forums,
However, upon running the installer, it appears that when it uncompresses the EXE and spits out the 2GB files, it doesn't actually put them back together as one 8GB file, though it does appear to be doing just that in the log file.
That's a very large file indeed and I'm afraid the only solution is running it through the command line like you tried. What is your current related concern since you already use LZMA and it works? If you didn't already know, Advanced Installer supports packing files larger than 2GB only if the "Place files unpacked next to the MSI database" option or LZMA compression is used.

All the best,
Mihai
I created the whole project and then Built the project and low-and-behold it's all ok. As I said, the project was building correctly and it was compressing the 8GB file into 2GB chunks, but when the installer was run, the uncompression worked up until the point where it put the 2GB pieces together and for some reason never managed to piece them back together. With a freshly created project, that problem has now disappeared.

Can you see anything in the previously attached project that would confuse the build and installation process for this to happen?
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Filesize Limitations

Hello,
Can you see anything in the previously attached project that would confuse the build and installation process for this to happen?
No, not really but if it happens again please contact us so we can replicate the issue and further investigate. You could generate a verbose log so we can see why the decompression failed.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”