Does:
Pexec(PE_GO,...)
On that PE_LOAD binary still work correctly?
Of course, it has to. If I'm not mistaken, on the relative position 28, where usually *my* instructions are is now a relative jump into the "new" code position (28+228).
That's why I'm not sure if it's a bug or feature.