CONTEXT_FULL flag is not set, ZERO is obviously incorrect
Posted on 2003-02-19 16:33:55 by Axial
In case you have SoftIce, load it (ctrl-d) and type
GDT to display ALL selectors.
I doubt you can find selector 0000.
Posted on 2003-02-19 18:46:27 by The Svin
Wish I did have soft ice. They want about a grand for it don't they?
Posted on 2003-02-19 21:07:27 by mrgone
Jmp Far f000:FFF0 worked in 16bit
Posted on 2003-02-19 21:42:15 by mrgone
I keep getting Email that someone responded but when I go to link I just see my You know there are several back doors. I'm just getting into this MASM32 stuff myself. These guys have made it possible for us to program Windows with our crude low level methods of programming. But as far as "jmp" goes I don't have alot of time to get into problem right now but a suggestion would be that if the jump instruction is not supported in MASM then put some NOP's in your program. Then open the EXE file with DOS "DEBUG" and machine code the instruction yourself. Make sure you have all the litterature on COFF / PE file particulars.
Posted on 2003-02-20 10:24:51 by mrgone
First I just did: mov eax,cs and I got "1b"

then I used thid code and got "1b" again


mov context.ContextFlags, CONTEXT_FULL
invoke GetThreadContext,pi.hThread, addr context
invoke wsprintf, addr buffer, addr displayregs,context.regCs,context.regDs,context.regEs,context.regSs,
invoke MessageBox,0, addr buffer, addr AppName, MB_OK+MB_ICONINFORMATION

I do have a problem I've been looking into where after CreateProcess I'm supposes to have full thread access but after a the first single step operation it does not set the Eip to the child process like it does in Win98. Trying to figure out why.
Posted on 2003-02-20 18:51:02 by mrgone