thanos wrote:SFSxOI wrote:BTW, there is also another way to put bloat into a program without really putting bloat in to affect the memory footprint. You create an empty .txt file of the size you choose and simply include it in your program. There is code in the forum for producing empty .txt files of any size that you choose. Its more precise then guessing that 100000 = nearly 400kbyte as you can choose the exact size. Plus it doesn't affect the memory footprint as long as the .txt file is really empty becauzse there is no data in the .txt to allocate memory too.
Hi to all.
I did the bloating trick by including a bitmap image at the end of the executable file.
Does this technique affects the memory?
Empty .txt file: do you mean a text file which include a sequence of null characters?
An empty file does not really affects the memory?
Regards.
Thanos
I'm sorry Thanos, I intended to answer you earlier but got distracted. The .txt file was just empty, did not contain anything at all. I guess its possible that it could contain a sequence of null characters but i could'nt find anything in it. Its a little snippet of code i picked up here in the forums, i'm sure I saved it somewhere in my colletion of snippets. Tell you what, as soon as I get home today from work i'll dig it out an post it for you. I didn't see any effect on the memory space size occupied when it was included in an app. Like I said above in another post; I didn't do any real in depth testing as its something i'm not really interested in, it was mostly a curiousity thing, but I could not tell any difference in the memory space size occupied between the empty .txt being included or not included. I guess its possible for there to be some effect, but just looking at the size occupied I couldn't really see any difference in memory but on the hard drive the size was as expected (according to how big the empty .txt file was).
EDIT: Oh wait, it wasn't code in the forum after all actually, well it was as I got the idea for the use from some code in the forum as I had never used that particular PB function before at the time, I just used CreateSizedFile(wrte_file_dir$,size); where write_file_dir$ = the full path to the file your going to create (i.e...C:\file.txt or C:\file.bin) and the 'size' is the file size (see the PureBasic help for info). Then I included as binary in the test.exe file.
The advantage of a 64 bit operating system over a 32 bit operating system comes down to only being twice the headache.