Mistrel wrote:Can you be more specific? I've seen plenty of exes larger than 64mb.
Exes without Resource-Section greater than 64 MB?
Use Resources for your Installer, so you have no problem with 700 MB or larger
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
Of course exes can get big, but the data was not compiled inside for them. It was appended. Of course, even my installer can create 2GB sfx's but the data is appended, not compiled in the resource section.
Last edited by Inf0Byt3 on Sat Apr 12, 2008 2:45 am, edited 1 time in total.
None are more hopelessly enslaved than those who falsely believe they are free. (Goethe)
here is a 114 MB exe compiled with PB: www.realsource.de/tmp/12.rar
is packed, so the download is only some kb
only manifest-resource and no append datas
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
No good idea so big data is to be packed into a DataSection, the data must be loaded 2x
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
The limit in this case, I think, is an artificial limit in the linker - the EXE file can't be larger than 64MB (I my opinion not that much of a limitation...)