Clicker 0.9.1 -- Draw a Bilou

[Pype.Clicker]

thanks to SANik's mouse driver and the OSLib's vm86 code i'm now almost ready to start doing GUI stuffs right at the moment, i have a disk image with two new "test" modules: one that show mouse movements on screen ('mouse' module) and one that perform basic screen mode changes (inlcuding the drawing of a small Bilou character in 320x200x256 mode ('vm86vesa' module)...

here you got the disk image

Note that due to the work-under-progress nature of that module, you'll have to repeatedly press the space bar to make things evolve. Once the module is loaded (Shift+F4, Ctrl+F5 to access the module loader), head yourself back to blue console (Shift+F1) to see progress messages ...

Enjoy ...

[distantvoices]

Hehe, that's a way cool thing.

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: Select all

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.

Gonna check the mouse movement thing now.

[distantvoices]

again me: have given the mouse module a shot:

is it correct that this spills out a lot of info to the log console? (shift+f4). Mouse movement is recognized, Mouse buttons are recognized.

[Pype.Clicker]

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: Select all

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...