inflating: CORE.NFO
▄ ▀ ▀ ▄
▄ ▄▄█▀ ▀█▄▄ ▄
▄▀▀█▄ ▄█▀ ▄▄▀██▀ ▀██▀▄▄ ▀█▄ ▄█▀▀▄
▄ ▐█▄▀ ▄ ▀▀ ▄██▀ t h e c r a c k e r s o f ▀██▄ ▀▀ ▄ ▀▄█▌ ▄
▀▄ ███▄ ▀ ▄▄▄▀ ███ ███ ▀▄▄▄ ▀ ▄███ ▄▀
▀ ▄▄ ▀▀▀▄▀███▀ ███ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄▄ ▄▄▄ ███ ▀███▀▄▀▀▀ ▄▄ ▀
███ ▀█▀ ███ ▄██▓▓██▄ ▄███▓██▄ ████▓██▄ ▐█▓▓███▓█▌ ███ ▀█▀ ███
███ ▀ ███ ██▓█▀▀███▌█▓██▀▀██▓█▐█▓█▀███▌ ▓▓██▀██▀▀ ███ ▀ ███
███ ███ ▐███▌ █▓█▐███▌ ▐██ ███▌ █▓█ ▐██▌ ███ ███
█████ ▐█▓█ ▐██▀▐███ ███▌███ ▄███▌██▓█▄▄▄ █████
███ ███▌ █▓█▌ ▐█▓ ▐▓███▓█▀ ▐██████▌ ███
▄█▄▄▄█▄ ▐███ ██▄▐███ ███▌███▀▀███ ▓██▓▀▀▀ ▄█▄▄▄█▄
[rAD!s] ███▀▀ ▀▀▄ █▓█▌ ▐██▌███▌ ▐▓█ █▓█ █▓█▌▐███▌▄▄ ▄▀▀ ▀▀███
██▀ ▐█▓██▄█▓█▌▐█▓██▄███▌ ███ ▐███ █▓███▓█▄ ▀██
▓██▄ ▀███▓██▀ ▀███▓▓█▀ ▐█▓█▌ ▐█▓▌▐▓██▓████▌ ▄▓█▓
▀▓▓█ ▀▀▀ ▀▀▀ ▀▀▀▀▀ ▀▀▀ ▀▀▀▀▀ █▓█▀
▓▌ ▄ ▀█▌ ▐█▀ ▄ ▐▓
▐▌ █ █▌ p r e s e n t ▐█ █ ▐▌
▓ ▓ ■▀▀ ▀▀■ ▓ ▓
▐▌ █▌ NexusDB Memory Manager v2.03 *RETAIL* ▐█ ▐
■ ▐█ █▌ ■
█▌ ▐█
▐█ Cracked by....: CORE Release-Name..: CR-NM203.ZIP █▌
██ Supplied......: CORE Release-Date..: 01/06/2005 ██
██▌ Packaged......: CORE Release-Type..: Util ██
█▓▌ Protection....: n/a OS............: Delphi BCB ▐▓█
▐██ Crack/SN......: Retail Language......: English ██▌
▐██▌ Rating........: [You decide!] Disks.........: 01 ██▌
▐██ ██▌
█▓█ █▓█
███ ▀█▄ ▄▀▀▀▄ ▄█▀ ███
███▄ ▀▄ ▄█▓▀▄▄▀ ▀▄▄▀▓█▄ ▄▀ ▄███
■ ▀█▓█▄▄ ▀▀▄▄ ▄▀▀ ▀▄ ▄▀ ▀▀▄ ▄▄▀▀ ▄▄█▓█▀ ■
▀▄▄ ▀▀█████▄ ▀▄ ▐ ▀▄▄ ▄▀ ▀▄ ▄▄▀ ▄▀ ▄█████▀▀ ▄▄▀
▀▀█▄▄▄ ▀█▓██ █ ▀ ▀▀█▄ ▄█▀▀ ▀ █ ██▓█▀ ▄▄▄█▀▀
▄ ▀▀██▀ ▀█ ■▀ ▄▀▀ ▐░▓ ▓░▌ ▀▀▄ ▀■ █▀ ▀██▀▀ ▄
▄■ ▄ ▄ ▐▌ ▒▒▌ ▐▒▒ ▐▌ ▄ ▄ ■▄
█▌ ▀ ▓▄▄▀ ▀▄▄ ▀▄▄ ▓▓█ █▓▓ ▄▄▀ ▄▀▀ ▀▄▄▓ ▀ ▐█
▐▓█▄▄▒ ▄▄▄██▀ ▀ ▄▄▓▓▀ ▀▓▓▄▄ ▀ ▀██▄▄▄ ▒▄▄█▓▌
▀▓█▓████▓▓█ ▄█▓▀ ▀▓█▄ █▓▓█████▓█▓▀
▀▀▀▀▀ ░█▀ ▀█░ ▀▀▀▀▀▀▀
░█ ▄▀▀▄ ▄▀▀▄ █
▐▌░▓▀ ▐▌ ▐▌ ▀▓░▐
▀▄ ▄▀ ▀▄ ▄▀
▀▀ ▀▀
▄■ ■▄ ▄▄▀ ▄▀▓▄
▄▓▀▄ ▀▄▄ █▌ ▀ ▓▄▄▀ ▀▄▄▓ ▀ ▐█ ▄▀▀ ▄▄▄ █
█ ▄▄▄ ▀▀▄ ▐▓█▄▄▒ ▄▄▄██▀ ▀██▄▄▄ ▒▄▄█▓▌ ▐▌ ▄▓░ ▀▀▄▄
▄▄▀▀ ░▓▄ ▐▌ ▀▓█▓████▓▓█ █▓▓█████▓█▓▀ ▀▄ ▀ ▀ ▄ ▀▄
▄▀ ▄ ▀ ▀ ▄▀ ▀▀▀▀▀ ▀▀▀▀▀▀▀ ▀▀▓░ █▀ ▐█
█▌ ▀█ ░▓▀▀ ■▀ ▓▌
▐▓ ▀■ ..: DESCRiPTiON :.. ▓▌
█▓ ▓█
█▓ ▓█
█▓ Memory fragmentation occurs when many different objects are ▓█
█▓ created and then destroyed repeatedly. As each object is created, ▓█
█▓ it consumes memory from the heap. If objects were created and then ▓█
█▓ destroyed in reverse order it probably wouldn't happen as all the ▓█
█▓ freed memory could be merged into one large block. But in any ▓█
█▓ system with a large number of objects the order of creation and ▓█
█▓ destruction will never be symmetrical. A process can easily have ▓█
█▓ up to 50,000 objects in memory at the same time. So when an object ▓█
█▓ is destroyed, a pointer to the freed memory block is added to a ▓█
█▓ free-block list. ▓█
█▓ ▓█
█▓ When other requests for memory are made, Windows tries to allocate ▓█
█▓ those requests out of the freed list first. Fragmentation happens ▓█
█▓ where a large block like 1Mb has been requested and subsequently ▓█
█▓ freed up, followed by a request for a smaller block. This is taken ▓█
█▓ from the first block on the free-list that may well be the 1Mb, ▓█
█▓ which leaves only 900Kb free. Then another request for a large 1Mb ▓█
█▓ block comes along, it cannot be satisfied from the free list and ▓█
█▓ so it is taken from the heap. If the creation/destruction cycle ▓█
█▓ happens enough times the large blocks on the heap are chopped into ▓█
█▓ smaller bits; the physical ram is exhausted and replaced with ▓█
█▓ virtual ram. Windows heap memory management (and Delphi) is quite ▓█
█▓ clever- it takes a lot to get it to fragment. But under the ▓█
█▓ relentless pressure of a large number of objects being created and ▓█
█▓ destroyed, the memory manager will gradually cave in. ▓█
█▓ ▓█
█▓ When Windows runs out of free ram, it starts swapping pages of ram ▓█
█▓ to disk, and performance takes a nosedive. Your app could be ▓█
█▓ galloping happily along at 100% CPU until swapping starts. It then ▓█
█▓ becomes a funeral march crawling along at maybe 7-10% of CPU, ▓█
█▓ taking forever to run. You can imagine the outcome. ▓█
█▓ ▓█
█▓ The Nexus Memory Manager helps preventing this by using a multi ▓█
█▓ stage allocation system which pre-allocates small chunks of memory ▓█
█▓ and leases parts of them to the application, whenever required. In ▓█
█▓ addition to this, a background thread detects unused blocks and ▓█
█▓ address space chunks, returning them to the operating system. It ▓█
█▓ reduces heap fragmentation and enables threaded allocation and ▓█
█▓ de-allocation. Most default memory managers (including the Delphi ▓█
█▓ one) synchronize all memory allocation and de-allocation, thus ▓█
█▓ creating a huge bottleneck for multi-threaded applications. For ▓█
█▓ server applications it is essential to minimize fragmentation and ▓█
█▓ maximize threaded memory allocation. The NexusDB replacement ▓█
█▓ memory manager does exactly this and it can be used in all your ▓█
█▓ applications as well. ▓█
█▓ ▓█
▐▓▌▄ ▄▐▓▌
▀░▀ ▀░▀
■▀ ▀■
▀▄ ▄▄ ▄ ▄ ▄▄ ▄▀
▀ ▄ ■ ▄▀▀ ▀ ▀▒▀ ▀▒▀ ▀ ▀▀▄ ■ ▄ ▀
▐▌ ▀ ▄ ▄ ▄ ▄ ▀ ▐▌
▄▓▀▄ ▀▄▄ ▀■ ▄ ■▀ ▀■ ▄ ■▀ ▄▄▀ ▄▀▓▄
█ ▄▄▄ ▀▀▄ ▄▀▀ ▄▄▄ █
▄▄▀▀ ░▓▄ ▐▌ ▐▌ ▄▓░ ▀▀▄▄
▄▀ ▄ ▀ ▀ ▄▀ ▀▄ ▀ ▀ ▄ ▀▄
█▌ ▀█ ░▓▀▀ ..: iNSTALL/REGiSTER NOTES :.. ▀▀▓░ █▀ ▐█
▐▓ ▀■ ■▀ ▓▌
█▓ ▓█
█▓ ▓█
█▓ Install. ▓█
█▓ ▓█
█▓ ▓█
█▓ ▓█
█▓ ..: iMPORTANT NOTE :.. ▓█
█▓ ▓█
█▓ Run CORE10k.EXE to verify this release, if CRC-check fails or ▓█
█▓ even CORE10k.EXE is missing - you are probably using webshit! ▓█
█▓ ▓█
█▓ else ▓█
█▓ ▓█
█▓ Thanks for choosing ▓█
█▓ (C)hallenge (O)f (R)everse (E)ngineering! ▓█
█▓ ▓█
▐█▓ ▓█▌
▐█▓ ▄■ ■▄ ▄▄▀ ▄▀▓▄▓█▌
▀▄ ▀▄▄ █▌ ▀ ▓▄▄▀ ▀▄▄▓ ▀ ▐█ ▄▀▀ ▄▄▄
▄▄▄ ▀▀▄ ▐▓█▄▄▒ ▄▄▄██▀ ▀██▄▄▄ ▒▄▄█▓▌ ▐▌ ▄▓░ ▀▀▄▄
▄▄▀▀ ░▓▄ ▐▌ ▀▓█▓████▓▓█ █▓▓█████▓█▓▀ ▀▄ ▀ ▀ ▄ ▀▄
▄▀ ▄ ▀ ▀ ▄▀ ▀▀▀▀▀ ▀▀▀▀▀▀▀ ▀▀▓░ █▀ ▐█
█▌ ▀█ ░▓▀▀ ■▀ ▓▌
▄▄ ▄ ..: CORE NEWS AND iNFOS :.. ▄ ▄▄
▄████ ▀▄ ▄▀ ████▄
▐██▓██▌ ▐▌ ▐▌ ▐██▓██▌
██▓███ █ - not available - █ ███▓██
▐▓█▓█▌ ▄▀ ▀▄ ▐█▓█▓▌
█▓██ ▐▌ ▐▌ ██▓█
▐█▓▌ ▀▄▄ ▄▄▀ ▐▓█▌
██▌ ▀▄ ▄▀ ▐██
▀█ ▐▌ ▐▌ █▀
▓ ▄▀ ▀▄ ▓
▄█ ▀▀█▄
▄▀▀ ▀▀▄
▄▀ ▀▄
▄█▌ ▐█▄
▓█▌ ██▓
▐██ ▐█▌
██ ██
██ ██
██ ██
▓██ ██
▐██▌ ■▀▄ ▄▀■ ▐█▌
█▓█▄ ▐▌ ▐▌ ▄█▓
▀████▄▄ ▄▄▄▄█▀ ▀█▄▄▄▄ ▄▄████
████▓█████▀▀ ▀▀█████▓████
▐▓█ ▀▀▀ ▀▀▀ █▓▌
▐█▌ ▐█▌
▐█▌ ▐█▌
█▓ ▓█
▐█▌ ▐█▌
█▓ ▓█
▐█▌ ▐█▌
█▓ ▓█
█▌ ██
██ ▐█▌
▐█▌ ▐█▌
▐▓▌ ▐▓▌
██ ▄ ▀■ ■▀ ▄ ██
▐▓▌ ■ ▀ ▀ ■ ▐▓▌
██ ▄█▀▀▄▄ ▄ ▀ ▀ ▀ ▀ ▄ ▄▄▀▀█▄ ██
▐▓▌▄▀▀ ▀█▄ ▀▓▀ ▀▓▀ ▄█▀ ▀▀▄▐▓▌
██ ▀ ▀ ██
███ ███
▓██ ██▓
▐██▌ ▐██▌
▓██ ██▓
██▓ ▓██
▓██ █▓█
███ ███
███ ███
██ ██
▐▌ ▐▌
█ ▄▄▄ ▄▄▄ █
█ ▄▀▀ ▀▀▄ lAYOUt & hEADER bY. [rAD!s] ▄▀▀ ▀▀▄ █
▀▄ ▀▄ █ nfO UPdATED ON [12/02/2004] █ ▄▀ ▄▀
▀▀▄▄▄ ▄▄▄▀ ▄ (c) C.O.R.E. 2 0 0 4 ▄ ▀▄▄▄ ▄▄▄▀▀
▀▀▀▀▀ ▀▀▀▀▀
· CRC C0FA:DECB