I tried woodman, but I think that url goes up and down throughout the day. It would still be nice to just have a simple 10 steps type of tut that gives me the missing bytes so I can drop them at the OEP and fix everything up. I have no problem finding where the bytes are to be pasted, but I can tell that aspr handles different languages in different ways. Some of the steps in Labba's tut can't be duplicated if you were attacking say VC or VB. I think with time more tutorials will show up and explain the variations. There doesn't seem to be a very clear cut approach to every single target. It depends on what options were used when the packer was applied and what language the target was written in (at least that is my perception).

If you are the same manko that writes aspr debugger, I've tried your tool a few times (and admittedly it confuses the hell out of me since it tells me the stolen bytes are at some very high memory range that makes no sense to me... I should probably see if there is documentation or something as I get lost very fast when using it =)

Thanks for the reply nonetheless.