flat assembler
> DOS > C4 C4 in NTVDM |
| Author |
|
|
Is there document about NTVDM api? With new AVX instruction set will the hack stop working?
|
|||
23 Jan 2019, 16:31 |
|
|
0xc4, 0xc4 = les eax,esp?
That would certainly become a new VEX prefix with AVX in the CPU. |
|||
|
23 Jan 2019, 16:53 |
|
|
Quote: BOP code 60 gives you the 'version' of ntvdm that's running (well. whichever antiquated version of SoftPC it's based on). Install a trap handler for invalid opcodes, and then execute c4/c4/60. If you get the version, probably 3.0, you're probably under NTVDM, and if you enter your trap handler, then you probably aren't. Obviously this wouldn't work for DosBox et al Quote: If you want some quick fun, manually enter "c4 c4 50 41" into debug and try to trace over it. Even though Debug will choke on the trace, you will see that the windows host name magically got put into the address specified in ds:dx. |
|||
|
23 Jan 2019, 18:52 |
|
|
It should be using ud2 (or ud0/ud1) to guarantee an invalid opcode. All other encodings might be used for future instructions that don't yet exist.
|
|||
|
23 Jan 2019, 19:10 |
|
|
revolution wrote: It should be using ud2 (or ud0/ud1) to guarantee an invalid opcode. All other encodings might be used for future instructions that don't yet exist. |
|||
|
24 Jan 2019, 02:38 |
|
|
0xc4,0xc4 also raises an exception. It is supposed to be a invalid instruction, just like ud2.
The difference is that 0xc4,0xc4 is not guaranteed to always be invalid. Ud2 is. |
|||
|
24 Jan 2019, 02:42 |
|
< Last Thread | Next Thread > |
Forum Rules:
|