hi.
i'm trying to program my ps2 keyboard in c.
i want to write the keyboard port (60h) and to for example get the number 3 on the screen.
i searched on google how to do this, and i know that there is scan code sets (every letter have it's own make code and break code) i tried to send the keyboard port the make code for the number 3 (04h) and than to send the break code (84h) but it didn't worked.
the scan code set is listed in this link - Scan Codes -- Set 1
please help me.
thank's, shachar.
Lemme guess, you're using TurboC on XP ?
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
It'll "work," just don't delude yourself in thinking that you're actually reading from a physical port. It's a virtual environment, which means you're NOT actually talking to hardware. Only the OS can do that.Originally Posted by Salem
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
He really should get into the 21 century for real projects, if he has no reason to stay locked in the past.
Everyone else's comment aside, you can't SEND key codes TO the keybaord controller. Whilst it is not strictly a one-way communication, it is not possible to "feed keypresses" into the keyboard controller.
I know this because once I wrote code that simulated what the keyboard controller does. On that system, there was a SPECIAL register to write to for feeding stuff into port 60 and 64. And there possibly is such a port in other systems too, but it's normally used by code that handles the USB keyboard when running non-USB capable OS (which is sort of what I was doing in the case where I wrote the code in question, except it was a PS/2 keyboard on a non-PS/2 capable machine).
And of course, as everyone has pointed out, if you are actually using an operating system released in the last 10 years or so, you can't actually read/write i/o ports from code that isn't a driver. So if you are doing something like reading/writing ports in a Turbo C program, it doesn't ACTUALLY access port 60/64 - it is trapped by Windows and translated to a "check keyboard status" call to Windows (so for example, you can read via port 60 to get a USB keyboard input - because it's not ACTUALLY reading port 60).
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
