------------------------------------------------------------

Subject:  HOW TO DEFEAT DECOMPILER - Msg Number: 511780
   From:  Daniel Berlin 72440,1573
     To:  all 
  Forum:  MSBASIC   Sec: 21-Developer Exchange
   Date:  31-Aug-95  16:47:42

OK, since people decided to upload it to a couple places, I decided to write
how to defeat it.
Decompilers do have legitamate uses, and have been around as long as
compilers. I will not go into ethical/moral/other arguments about right/wrong.
I am only going to post how to defeat the decompiler.  These are only some
techniques.  I have others that i'll post/implement if it becomes neccessary.
Try using all these techniques at once .  Technique three just makes
decompiler output unusable for all practical purposes, so combine with other
techniques.  All need a hex editor.  Standard legal disclaimers and such
saying i'm not liable for anything would go here. Just pretend

Technique 1:
Create a new form in VB, in your project.
Don't do anything to it.
Compile the project.
Hex edit the compiled product.
Go to the end of the file.
If you followed directions, the last couple lines of 16 bytes will start with
"FF CC 2C"
Overwrite everything after/including the hex bytes "FF CC 2C" with a LETTER OR
NUMBER. NO FF'S OR 00'S

Technique 2:
hex edit the compiled exe.
search for "03 20 81" (this depends on vb version number. this is for version
3).
Zero (00) out JUST THE NAMES of the Forms. Not the name of the executable
(usually comes first), or the help file.

Technique 3:
Hex edit the compiled exe.
Search for "FF CC 2C"
After the many bytes of 00's, you should see control/form names.
Just 00 the whole thing.

Voila!
No more decompilation
--Dan


