Compile Write Error

CGTV · 18th November 2005, 16:28

Hello,

If anyone can help, I would appreciate it. I recently compiled an installer successfully using NSIS. It is a setup file that installs alot of data. The setup file came out to be around 980MB and when uncompressed, it requires about 11.5 GB of space.

I went back and added just a few more files to the folders that I am compressing in the install, and now when it gets to the end when compiling, I am getting this error:

Error: can't write 62968023 bytes to output
Error - aborting creation process

here also is what else is printed right before it fails:

Processed 1 file, 1 command line command, writing output:
Adding plug-ins initializing function... Done!
warning: Uninstall section found but WriteUninstaller never used - no uninstaller will be created.
Processing pages... Done!
Removing unused resources... Done!
Generating language tables... Done!

Output: "C:\Program Files\NSIS\setup_UsefulFX.exe"
Install: 6 pages (384 bytes), 19 sections (1 required) (19912 bytes), 5224 instructions (146272 bytes), 1540 strings (44032 bytes), 1 language table (346 bytes).
Uninstall: 4 pages (256 bytes),
0 sections (0 bytes), 150 instructions (4200 bytes), 102 strings (1568 bytes), 1 language table (278 bytes).
Datablock optimizer saved 21234951 bytes (~2.1%).

Using bzip2 compression.

EXE header size: 49152 / 34304 bytes
Install code: 54789 / 211370 bytes
Install data: 1002492119 / 1276080775 bytes
Error: can't write 62968023 bytes to output
Error - aborting creation process

Can anyone tell me why adding just a few more files that are most likely under 2MB worth of data would now cause this problem? or is it unrelated?

it sounds like a memory or HD space issue, but I think I have enough space... maybe not enough memory? it worked before..... arg.

thanks for any help,

-CGTV

Afrow UK · 18th November 2005, 16:53

Firstly you need WriteUninstaller in an install Section to create your uninstall.exe.
That won't fix your problem though.

-Stu

CGTV · 18th November 2005, 18:05

thanks for the response... Yes I'm quite aware of the uninstall issue - I purposely left that out because I dont want to make an uninstaller now, so I commented out that stuff... but that has nothing to do with the problem.

Can someone else address the issue that I asked about?

thanks,

-CGTV

dandaman32 · 18th November 2005, 21:31

How much RAM do you have? I'd recommend at least 1GB-1.5GB before compiling an installer that huge. and 1.5-2GB if you're using Windows Vista ÃŸ1. Also it very well could be a HDD space issue. NSIS uses a lot of temporary space on the disk when it's compiling, so you want at least 15GB free, or 20GB for Vista ÃŸ1.

Quote:

Originally posted by CGTV

Can anyone tell me why adding just a few more files that are most likely under 2MB worth of data would now cause this problem? or is it unrelated?

Not sure if you hit the limit for installer size. That could be the problem, though you should be able to create setups as big as 2GB in Win2000/XP/2003/Vista

-dandaman32

CGTV · 19th November 2005, 06:30

thanks for the reply...

I freed up some extra HD space and also setup larger Virtual Memory disks on the HD partitions and it finally worked.

My system is Win2K and only has 512MB RAM, so I must have been pushing the limits.

but it works now, so if anyone has this issue try increasing the HD space and Virtual Memory.

thanks,

-CGTV

18th November 2005, 16:28	#1
CGTV Junior Member Join Date: Oct 2005 Location: CA Posts: 8	Compile Write Error Hello, If anyone can help, I would appreciate it. I recently compiled an installer successfully using NSIS. It is a setup file that installs alot of data. The setup file came out to be around 980MB and when uncompressed, it requires about 11.5 GB of space. I went back and added just a few more files to the folders that I am compressing in the install, and now when it gets to the end when compiling, I am getting this error: Error: can't write 62968023 bytes to output Error - aborting creation process here also is what else is printed right before it fails: Processed 1 file, 1 command line command, writing output: Adding plug-ins initializing function... Done! warning: Uninstall section found but WriteUninstaller never used - no uninstaller will be created. Processing pages... Done! Removing unused resources... Done! Generating language tables... Done! Output: "C:\Program Files\NSIS\setup_UsefulFX.exe" Install: 6 pages (384 bytes), 19 sections (1 required) (19912 bytes), 5224 instructions (146272 bytes), 1540 strings (44032 bytes), 1 language table (346 bytes). Uninstall: 4 pages (256 bytes), 0 sections (0 bytes), 150 instructions (4200 bytes), 102 strings (1568 bytes), 1 language table (278 bytes). Datablock optimizer saved 21234951 bytes (~2.1%). Using bzip2 compression. EXE header size: 49152 / 34304 bytes Install code: 54789 / 211370 bytes Install data: 1002492119 / 1276080775 bytes Error: can't write 62968023 bytes to output Error - aborting creation process Can anyone tell me why adding just a few more files that are most likely under 2MB worth of data would now cause this problem? or is it unrelated? it sounds like a memory or HD space issue, but I think I have enough space... maybe not enough memory? it worked before..... arg. thanks for any help, -CGTV

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

18th November 2005, 16:53	#2
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	Firstly you need WriteUninstaller in an install Section to create your uninstall.exe. That won't fix your problem though. -Stu

18th November 2005, 18:05	#3
CGTV Junior Member Join Date: Oct 2005 Location: CA Posts: 8	thanks for the response... Yes I'm quite aware of the uninstall issue - I purposely left that out because I dont want to make an uninstaller now, so I commented out that stuff... but that has nothing to do with the problem. Can someone else address the issue that I asked about? thanks, -CGTV

19th November 2005, 06:30	#5
CGTV Junior Member Join Date: Oct 2005 Location: CA Posts: 8	thanks for the reply... I freed up some extra HD space and also setup larger Virtual Memory disks on the HD partitions and it finally worked. My system is Win2K and only has 512MB RAM, so I must have been pushing the limits. but it works now, so if anyone has this issue try increasing the HD space and Virtual Memory. thanks, -CGTV