NTVDM: invalid opcode

[Ignacio González]

I have to run an old MS-DOS aplication unaware of the existence of
386/486/586 processors.

Its code is adapted from another old non-MS-DOS 8086 aplication, which
happens to run on an embedded multiprocessor platform.

As you may know, the LOCK instruction can be executed before almost any
instruction (such as MOV) in 8086, but NOT on its newer cousins (it is
allowed only before XCHG)

Well. That old application works OK, except when such opcode is found. In
fact, if I press "Ignore" when the NTVDM warning dialogue pops up, it
continues to work, but that's very annoying, as you may guess.

Well again. Here is the question: is there any way to tell the NTVDM to
ignore always the f0 (LOCK) opcode ? Any hacker out there?

[Jake]

In article <88bajh$ha...@esiami.tsai.es>, igtorque...@eliopDOT.es says...

Heh - Just Hex -edit it out : a 90 (nop) should do the trick ..

[Patrick Smout]

Write a WIN32 program that uses the WIN32 debug facilities. If it is an
exception, you should be able to handle it in the WIN32 program. Take a look
at the DEBUGAPP application in MSDN.

Patrick Smout

Ignacio González <igtorque...@eliopDOT.es> schreef in berichtnieuws
88bajh$ha...@esiami.tsai.es...