- NSIS Discussion
- Compiler error #12345
Archive: Compiler error #12345
Thetotoman
22nd January 2003 15:10 UTC
Compiler error #12345
Hi! I'm french so I hope you will undrestand what i say:
there is an error ahen I compile a big file (600~700 MB). The compiler writes:
Internal compiler error #12345: error mmapping datablock to 855985079.
Note: you may have one or two (large) stale temporary file(s)
left in your temporary directory (Generally this only happens on Windows 9x).
I'm under windows XP pro. I tryed to delete all the files who was in the temp dir but doesn't works...
How can I do ??
Thank you for helping me.
kichik
22nd January 2003 15:17 UTC
There shouldn't be any problems on Windows NT (including XP) for files up to 2GB. Are you sure you have enough memory and free hard disk space?
Thetotoman
22nd January 2003 15:29 UTC
yes i have enough free hard disk space and enouch virtual memory. But I have only 256 mb of ram maybe it's that. I will buy 512 mb at the end of the week
kichik
22nd January 2003 15:36 UTC
It should work without it. Virtual memory is good enough for it. Maybe your swap file is too small. According to the error you were trying to make an installer larger than 850MB.
virtlink
22nd January 2003 18:01 UTC
(KiCHiK isn't clear sighted:weird:, he read his 850 Mb in the error you posted: 855985079 bytes) ;)
kichik
22nd January 2003 18:05 UTC
OK... 816, my mistake :p
kichik
30th January 2003 17:15 UTC
Are you by any chance using FAT16/32 and not NTFS?
AnalogKid
30th January 2003 22:59 UTC
The maximum file size on a:
* FAT16 partition under Windows 9.x and ME is 2 GB.
* FAT16 partition Under WinNT or 2K is 4 GB
* FAT32 partition under any OS is 4 GB.
* NTFS partition is ~16 exabytes or 18,446,744,073,709,551,616 bytes (2^64 sectors). I don't think we'll be whining about that limit any time soon.
...AnalogKid
Mark_Ive
6th February 2003 08:57 UTC
i am also having the same problem but i know what the resolution to mine is even if you are outputting to a different drive my c: has to have enough space for the same size as the installer is going to be...
If anyone knows how to move the location the temp files nsis uses as i cannot free up enough space on c: to compile please help
kichik
6th February 2003 11:17 UTC
NSIS uses the system temporary directory. All you need to do is change it. You must also have a NTFS drive if you want to compile very big installers (800+ MB).
Mark_Ive
6th February 2003 11:21 UTC
Was just about to reply i worked around the problem by changing my environment variable tmp and temp paths to my bigger drives as you said this works fine now
Thanks
AnalogKid
7th February 2003 19:16 UTC
Ahh .. as far as the NTFS drive requirement goes, it didn't do anything for me to make them NTFS. I still run into the same problem, but I haven't had time to run through the code and figure out where. Do you have any ideas? Also, has anyone heard from Thetotoman to see if his predicament was fixed by this (or even if he was in fact using FAT)?
Thanks again,
...AnalogKid
kichik
7th February 2003 20:30 UTC
I will get deeper into this after I release b1.
virtlink
4th April 2005 23:41 UTC
Thanks for the theadsplit kichik :p, the notification e-mail driected me to this thread, with me finding nothing new here, and the intended replies in the other thread. :rolleyes:
Btw I still appreciate the work you guys do on NSIS, altough I'm not using it very often these days (thinking back to those good ol' days). :up: :D Keep up the good work!
nco2k
8th July 2007 12:21 UTC
when i try to create my installer which is about 3.4gb large, i am getting the same error. :(
"Internal compiler error #12345: error mmapping file (2087921070, 33554432) is out of range."
using:
- vista home premium x64
- 2gb ram
- about 23gb free disk space (ntfs)
- virtual ram is set to "automatically by os"
- nsis 2.28
any ideas?
slloyd
30th October 2008 18:56 UTC
Are there plans to increase the 2GB nsi limit?
With OS, memory, and hard drives getting larger I was wondering if you have plans to increase the 2GB setup limit?
We provide installs (web downloads) for large companies and there are times that I have to zip up the install instead of providing a nullsoft setup.exe
Today, I had to build a single install that was 2.2GB. Of course, nullsoft failed and I had to use CopyFiles and zip up the install using WinZip instead.