beyond infinity wrote:
Have given the vm86vesa module a test and got a small bilou in the upper left corner on blue background.
Then I have decided to press space and got this:
Code:
exception occured<Dhandler@00325270:vm86 monitor(code = 003244d8, info=00000c17):called(00c5df83,00000000):1>Exception resolved--Exception occured<Dhandler@00325270:vm86 monitor(code = 003244d8, info = 00000c17):called(00c5df83,00000000):1>Exception resolved--
termination successful
remark: tested in qemu 0.6.1-windows version.
yUP. That's something "normal" (though i admit the word "exception" will frighten everybody ...
What occurs is that your BIOS issued some INT nn for internal reason. This triggers a GPF (as the vector isn't a user-allowed INT) which is trapped by the exception mechanism (verbose atm)
It then says "exception D" >> trying handler "vm86 monitor" >> result value was 1 >> exception resolved (no need to worry anymore, returning to normal operations).
This repeats for every INT nn encountered. You can get more info about this on the log (Shift+F3) where you should see info about instruction flow patching ...
i'll enclose those stuff with #ifdef __PARANOIA__ for later releases...