CommieCausey

this is kind of old but i felt the need to come to PriitK's defense since no one else did. unlike bmps, gifs and pngs are compressed images. bmps are bitmaps and can be loaded into memory and then directly displayed on the screen. pngs and gifs have to be loaded into memory, decompressed into another memory spot as a bitmap which is saved for later, drawn, and the original file data freed from memory. there really isnt a way around the extra steps and its not PriitK's fault. the loading time comes from having to decompress the bitmaps into ram. pngs/gifs advantage of compression is only on the hard drive not in ram. someone else said that bmps take up more space in RAM? is subspace like that? i am thinking they meant the hard drive. CC

i just remembered, if it closes after starting the createprocess infinite loop that is not the packer's fault. that is custom made to stop debuggers and annoy you! i didnt examine what caused it to happen. CC

it used to be on exetools next to the pex download but like i said its long gone. someone named codeinside also made a tutorial but his page is also gone. oliver, if you need help with it feel free to send me an email.

i am positive it is packed & compressed with pex written by "bart". priitk just changed a few bytes to ruin the signature and fool dex, the unpacker. i used a tutorial written by bart to manually unpack continuum but i cant find an active link. i also used ollydbg, a user-level debugger. you dont need softice. CC

oops it posted twice sry connection problems

there is a tool called PEid that can identify which packer was used. then google the name... i am pretty bummed that i can't use wine because i am using linux on an old mac but i think wine is awesome and best of luck to you! CC