In most cases, to debug a .dll, you'll want to write a small program to call several of its exports one after another anyway. You can use ollydbg or windbg to load your .exe and trace through the .dll code.
My personal experience is that in many cases, the best approach would be using IDA first to get an overview over the unknown binary, then use ollydbg or the IDA debugger to trace on the processor instruction level, and only use a high level debugger when i have some symbols to trace on the source code level.
I just did a thorough learning of the pixtopian file. When I downloadedthat tutorial I get the file pixtopian107.exe only. Since it didn't agree with the tutorial I investigated further. That file is an installation file. It produces a regular pixtopian.exe file which is the file you wish to play with.I also noticed that in running the file it never enters the main module.this is because of the TLS callback. right now I am trying to learn how to overcome this which is how i came to this site in the first place.I am using ollydbg vs2.01e very effectively.
f5d0e4f075