Re

[wndproc]

Thanks for the post, as I tried to send you my source I found the "source" of the problem.

I printed the keys with the following function:
Print((byte)keymap[keydata]);

Right now I would really like to dig a hole and stay in there for a week.

To make this threat at least a bit usable I'd like to ask if anyone of you knows why I get 2 bytes on a cursor-key-down in bochs and 4 bytes in MS VPC.

I.e.:
Cursor left KeyDown (Bochs): 0xE0, 0x2A, 0xE0, 0x4B
Cursor left KeyDown (MS VPC): 0xE0, 0x4B

[ru2aqare]

Thanks for the post, as I tried to send you my source I found the "source" of the problem.

I printed the keys with the following function:
Print((byte)keymap[keydata]);

Right now I would really like to dig a hole and stay in there for a week.

To make this threat at least a bit usable I'd like to ask if anyone of you knows why I get 2 bytes on a cursor-key-down in bochs and 4 bytes in MS VPC.

I.e.:
Cursor left KeyDown (Bochs): 0xE0, 0x2A, 0xE0, 0x4B
Cursor left KeyDown (MS VPC): 0xE0, 0x4B

Some keys send a "fake" left-shift for some compatibility reason. Read more here.

[wndproc]

Thanks