You might also want to modify the OllyDbg class and window names and at the very least, turn off - let the target program handle - all exceptions, at least to begin with.
I think that you should know your tools before using them on malwares. There is no "best way" to configure OllyDbg. Your configuration might suit your need.
For example, you could uncheck all exceptions handling in "Debugging Options -> Exceptions" to break on all SEH tricks. You could also check "system Breakpoint" in Events option to break before the entry point and handle TLS. You could choose to break on new thread or new module. It's up to you ! And to malware.
But if you ask this question, I think that you should learn how to use OllyDbg first.
maybe you could use ollydbg and the maleware in a vmware enviroment (depending on the maleware and protection of course) this would save you from causing damage to your system hopefullly.
pedram you have a little bit older version on your downloads there are atleast 6 more revision iirc the beta is 12 now ive uploaded the 1.26 beta 12 to my repo
check it out and if it has a few more improvements and update the download
oops repo upload says cant process upload :(
Error: Failed processing upload to repository.
ill mail you the rar
edit
possibly some ghost views or lack of sleep i can promise that the download was 1.26 version 6 when i read your message but the link in above post shows beta 12
so sorry for dumb posts
Note: Registration is required to post to the forums.