Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.asm.x86    |    Ahh, the lost art of x86 assembly    |    4,675 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,688 of 4,675    |
|    Rick C. Hodgin to R.Wieser    |
|    Re: Interpreting (the data following) a     |
|    04 Dec 18 13:17:44    |
      From: rick.c.hodgin@gmail.com              On Tuesday, December 4, 2018 at 12:56:44 PM UTC-5, R.Wieser wrote:       > Looking in the "The IA-32 Intel Architecture Software Developer's Manual,       > Volume 2 - Instruction Set Reference (24547112).pdf" document I can find       > multiple entries having the 0xD9 opcode, and from it I take it that the       > bytes following the above INT 0x35 are also playing a role: 0x7E 0xFA 0x8A       > ...       >       > I have abslutily *no* idea how to match it up with the 0x7E opcode folowing       > the INT 0x35. The explanation for the "/6" is as follows:              I apologize, Rudy. I completely misunderstood what you were posting       here. My mistake.              Is it possible 0x8afa or 0xfa8a is a memory pointer to the instruction       to emulate, or an offset in the current data segment? I would trace       into the interrupt in the debugger and see how it decodes those values.              Also, interrupts are usually signaled with values in the registers or       on the stack being setup. What does it do before that INT 35h?              --       Rick C. Hodgin              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca