I'm getting this Olly error when I try to attach to a running process. How does this process keep from being looked at ? Is there a way around this ?

It's probably protected by Armadillo and the like with the "Debug blocker" option set. There's no real way around it as the process itself is already being "debugged" by it's master process, so Ollydbg can't step in and even sniff it, nevermind debug it.

However, you can debug it's master process, and force the master to stop debugging it, place the child into an infinite loop and allow ollydbg to connect to it.

So if you run an Armadillo-protected exe that has the 'Debug blocker' option set, you'll actually have TWO executables running???

This Armadillo app runs and yes, there are 2 apps running. 1 app specifically for the registration window and the main executable. The app for the reg entry is the one that will not allow attachment. How do you setup the master process to stop debugging it ?

Yes, all kinds of debug blocker actually have two executables running.

Is there a "good" PE examiner that is recommended to tell you what packer was used on a particular target ?

yes

Which PE examiner would you recommend ?

peid 0.9

Will peid 0.9 work on dll files as well ?

yes

Are there any good tuts for unpacking and restructuring an Armadillo v2.5-v2.6 target ?