.exe file larger than 4Gb does not open in windows

[Imagem-VIP]

Can anyone tell me why AutoPlay Media Studio 8.5, when the .exe file is larger than 4 Gb, does not open? I am having this problem.

I created an application that I compiled into an .exe and the file was larger than 4 Gb, but windows does not run the application.

Is there any configuration to do in AutoPlay Media Studio 8.5, so this doesn't happen?

[herrin]

Can anyone tell me why AutoPlay Media Studio 8.5, when the .exe file is larger than 4 Gb, does not open?

dude
u can't build exe file larger than 4 GB.

[Imagem-VIP]

Thanks a lot friend herrin, I really didn't know about this condition of AutoPlay Media Studio.

[Imagine Programming]

Thanks a lot friend herrin, I really didn't know about this condition of AutoPlay Media Studio.

I don't think it's a limit of AMS, I believe 32-bit Windows (and the syswow64 subsystem) do not support executables larger than 4 gb.

[Imagem-VIP]

It may indeed have something to do with windows, because in the AMS preferences menu you can choose other types of project size.

[Nickj]

It's all down to signed integers with a maximum 2^32 / 2 bytes being historically employed in the implementation of the format from the early days of windows and memory limitations imposed by the architechture - Windows binaries on 64bit versions can address over 2 (32 bit) / 4 GB (64bit) of memory, but maximum binary size limitation still applies to modern .exe implementation.
So the limit could be 'updated' but on embeded systems using 32 bits they could cause real problems so the limit stays in place.
If it's your created binary re-hash it and have some of the file load as external elements.

[kingzooly]

You can work around this by creating it as a HDD build and packing it with a 64 bit exe packer if any still are around most people no longer seem to care about since exe's also think of it this way that is 4 gig that as to unpack to the temp folder it's a lot hdd build means it runs from where it's created.

[Imagem-VIP]

The purpose of creating an .exe file is so that people do not have access to the files and images of the project, a person with good knowledge knows that if they go to the TEMP folder, they will find the project files there, but that is few people who know.

[Imagine Programming]

The purpose of creating an .exe file is so that people do not have access to the files and images of the project, a person with good knowledge knows that if they go to the TEMP folder, they will find the project files there, but that is few people who know.

The people you don't want to have your project files and images are precisely the ones that know exactly how to do it.

[Imagem-VIP]

That's why you don't have to worry about this kind of things, like hiding files, everyone nowadays knows a lot about computer.

[kingzooly]

The purpose of creating an .exe file is so that people do not have access to the files and images of the project, a person with good knowledge knows that if they go to the TEMP folder, they will find the project files there, but that is few people who know.

I am not even sure why you added this comment it makes no sense as this is what your trying to do put it all in one exe and that's how AMS works it puts it in the temp folder, I know what the reason is for so please don't try school when it has no place in the post in the first place.

Right that done, why are you trying to put it all in to one exe if you don't want to hide the files as any exe that holds all the resources need to unpack them resources that's how it works so if your not trying to protect the files in some strange way what are you trying to do?

Also this does NOT change the way to fix the problem, you create your software in a already 64 bit aware or you have to repack it after the fact so your last few posts have one off task you have started to state what we stated in the first place.

So to answer you first post
Use a HDD build and if you want it still in one exe use a different packer that supports 64 bit but like we stated there isn't any need for this packing files was never to protect a file when it comes to big companies or the OS it's self there was to just find a easy way to move the file form A to B and then install the files to the right place, protected files as on the file level and processed level.

Not sure why you side railed your own post but that's how you will fix this problem.

Another way you could fix this downsize your files compress files where you can and cut out any fat so it's blow 4 gig but it will run slow as it will have to decompress in to the temp files this is the facts of how AMS works.


Good luck with your project.

[Imagem-VIP]

friend kingzooly

I didn't understand why you were desperate to criticize me for my post, this is a place for debates and exchanges of ideas, I'm not an amateur, I know what I'm doing, the purpose of my post was to know why AMS limits size of the file if it itself has options to create files larger than 4Gb, as I showed in the image above, nowhere does it specify the .EXE limit, I'm sorry if you got stressed with this post, but like you said, that's how it works.
Thank you for your help, it sure is very useful.
Have a nice week.

[Imagine Programming]

the purpose of my post was to know why AMS limits size of the file if it itself has options to create files larger than 4Gb, as I showed in the image above, nowhere does it specify the .EXE limit

I believe the project size you refer to in the screenshot merely indicates what the size bar in the UI shows, so that the developer knows when they are reaching their own set limit. It's defaulted to 700MB, the size of a CD, as that is what AMS was originally made for. It does not specify the maximum size for the exe nor any derived file.

[Imagem-VIP]

So friend, it was exactly what I was looking for, if AMS really supports files larger than 4 Gb or not, but what I don't understand is why AMS gives you the conditions to increase your project up to 100 Gb or defined by you, if he only manages to create a .exe of only 4Gb, even on CD or DVD it would not fit in any if his project was over 4.7 Gb.

[Imagine Programming]

So friend, it was exactly what I was looking for, if AMS really supports files larger than 4 Gb or not, but what I don't understand is why AMS gives you the conditions to increase your project up to 100 Gb or defined by you, if he only manages to create a .exe of only 4Gb, even on CD or DVD it would not fit in any if his project was over 4.7 Gb.

Again; it has nothing to do with the size of the executable, it has to do with a virtual limit for you to look at during development (see attached). For example, I have seen a lot of AMS applications that merely ship as HDD folder through a 64-bit installer. These projects are installed on a users system (i.e. Program Files) and can be any arbitrary size, the project size setting gives those developers a guideline to keep track of how much the total project will 'weigh'.