Y
YB_unique
Unregistered / Unconfirmed
GUEST, unregistred user!
Upon startup of a compressed EXE/DLL, all of the code is decompressed from the disk image into memory
in one pass, which can cause disk thrashing if the system is low on memory and is forced to access the
swap file. In contrast, with uncompressed EXE/DLLs, the OS allocates memory for code pages on demand
(i.e. when they are executed).
Multiple instances of a compressed EXE/DLL create multiple instances of the code in memory. (So if your
EXE is 1 MB and the user starts 5 instances of it, that adds up to 5+ MB.) With uncompressed EXE/DLLs,
the code is only stored in memory once and shared between instances.
Some older virus scanners flag compressed EXE/DLLs as being virus-infected.
in one pass, which can cause disk thrashing if the system is low on memory and is forced to access the
swap file. In contrast, with uncompressed EXE/DLLs, the OS allocates memory for code pages on demand
(i.e. when they are executed).
Multiple instances of a compressed EXE/DLL create multiple instances of the code in memory. (So if your
EXE is 1 MB and the user starts 5 instances of it, that adds up to 5+ MB.) With uncompressed EXE/DLLs,
the code is only stored in memory once and shared between instances.
Some older virus scanners flag compressed EXE/DLLs as being virus-infected.