This is the continuation of the crackme "the amazing unit converter"
I strongly suggest you familiarise yourself with the first crackme before starting this one.
I have included the readme of the first crackme at the end of this file.

deroko suggested I add IAT obfuscation to the packer, what I did.

everything else is pretty much the same, including the host program


difficulty:
-----------
I am a newbie to cracking and have never manually unpacked anything hostile.
So I dont know how difficult it will be, I hope you crack it, write a good tutorial and I can learn from it.
It might be quite hard, though.




===================================================== README OF FIRST CRACKME =========================================================

Your task:			Make the program run without the annoying Shareware reminders.
								Anything goes as long as you write a good newbie-friendly tutorial

compatibility:	This program was created on XP and was briefly tested on W2K.
								It will not run on other OSes. Dont bother, it really wont. 
								What you should see:	3 seconds delay, then some shareware-reminder Messageboxes, then a dialog-based program. 
								If you see anything different that means this program wont run on your os/machine. Im sorry. 


The following info should make it possible to crack this crackme in minutes.
If you really want to be challenged dont read it.



<spoiler space>



The program is completely harmless and normal, created with the Pelles C compiler.
It was however packed using an extremely primitive packer I just wrote.
The packer works this way:
	=> the code and data sections are encrypted in-place.
	=> another section (the decryptor) is added to the end of the file and the entrypoint placed there.
When the packed program starts, control is transferred to the decryptor section which decrypts the other sections,
the jumps at the original entrypoint.

Important points:

=> The structure of the PE-File is not touched by the decryptor. 
   (well sections are renamed and some random bits in the characteristics flipped, but that doesnt change anything)
=> There is no protection against dumping.
=> There is no protection against attaching.
=> The segment containing the imports is not touched.
=> So the packed file has the same structure as the packed file, only one section is added.

The packer has been applied several times so each time a new section has been added at the end of the file.

You can view the decryptor as a black box and find another, simpler way to solve the problem.
Therefore the decryptor is made obfuscated and debugger-hostile using the haystack-method I already used in
other crackmes. But feel free to do battle with the decryptor, if you win then more power to you.

Have fun!