Displaying 1 result from an estimated 1 matches for "pxenv_exit_failur".
Did you mean:
pxenv_exit_failure
2007 Jan 06
6
PXE stack access via com32
...inputRegs.edi.w[0] = OFFS(__com32.cs_bounce);
inputRegs.eax.w[0] = 0x0009;
/* call PXE stack */
inputRegs.ebx.w[0] = 0x0071;
/* PXENV_GET_CACHED_INFO opcode */
__intcall(0x22, &inputRegs, &outputRegs);
However, when setup this way, 'outputRegs.eax.w[0]' contains 'PXENV_EXIT_FAILURE' (and the status field of the PXE call argument struct indicates failure as well). The instructions from the previous thread on this topic are contrary to that documentation and indicate something more like (not sure about the PXE opcode being in edi, of course, but that wasn't specified...