Main > Main Forum
USB vs PS/2 vs COM vs LPT
SavannahLion:
--- Quote from: Bender on September 25, 2010, 10:00:23 am ---Awww come on guys the is the funniest thing I've seen in a while :jerry
--- End quote ---
Oh what the hell. Driver is a moron anyways.
:jerry :jerry :jerry
Driver-Man:
Actually I found something there...
http://msdn.microsoft.com/en-us/library/ms645546(v=VS.85).aspx
Quote:
- "In this sample, an application wants raw input from the keyboard and mouse but wants to ignore legacy window messages (which would come from the same keyboard and mouse). "
--- Code: ---RAWINPUTDEVICE Rid[2];
Rid[0].usUsagePage = 0x01;
Rid[0].usUsage = 0x02;
Rid[0].dwFlags = RIDEV_NOLEGACY; // adds HID mouse and also ignores legacy mouse messages
Rid[0].hwndTarget = 0;
Rid[1].usUsagePage = 0x01;
Rid[1].usUsage = 0x06;
Rid[1].dwFlags = RIDEV_NOLEGACY; // adds HID keyboard and also ignores legacy keyboard messages
Rid[1].hwndTarget = 0;
if (RegisterRawInputDevices(Rid, 2, sizeof(Rid[0])) == FALSE) {
//registration failed. Call GetLastError for the cause of the error
--- End code ---
---end quote
Do you notice the word "IGNORE", and the sentence "which would come from the same keyboard and mouse".
Obviously legacy input is still there, sure you can "ignore" it too, as you will, but that will not make it go away.
newmanfamilyvlogs:
http://www.microsoft.com/whdc/archive/usbhost.mspx?pf=true#usbh1
--- Quote ---The time line in Figure 1 starts with a power-up (cold boot) event on the PC.
•
Immediately after power-up and for some period of time, the BIOS controls the PC and the host controller. During this time interval, a user should be able to use a USB keyboard to enter BIOS Setup and then use all keys on the USB keyboard that are valid during BIOS Setup.
•
If the user does not choose to enter BIOS Setup, at some point the BIOS starts the operating system and the operating system takes control of the PC and the host controller. As shown in Figure 1, code in a routine in the operating system host controller driver performs the necessary steps to hand off control of the legacy keyboard support function from the BIOS to the operating system host controller driver (in this article, that routine is called StopBIOS).
•
The next event shown in Figure 1 occurs when the user employs the Shutdown menu to shutdown to MS-DOS. This causes the host controller driver to be unloaded; before unloading it executes a routine that performs the necessary steps to hand off control of the legacy keyboard support function to the BIOS (in this article, that host controller driver routine is called StartBIOS).
--- End quote ---
This kinda looks like it.
Derrick Renaud:
:banghead:
I give up. You are right. BIOS has supported multiple keyboards since day 1. Everything goes through the BIOS, even though Windows shuns programs using it. It has nothing to do with old APIs being provided from new APIs. I imagine when they make new APIs it is for the sole purpose of wrapping the old APIs in a new layer of confusion that provides no benifit.
Thanks for making me see the light. I will now move on to more important things.
D.
:cheers:
Derrick Renaud:
--- Quote from: Driver-Man on September 25, 2010, 11:16:14 am ---Do you notice the word "IGNORE", and the sentence "which would come from the same keyboard and mouse".
Obviously legacy input is still there, sure you can "ignore" it too, as you will, but that will not make it go away.
--- End quote ---
I should not respond to this, but your logic is amusingly baffling. ;D
It does not make it go away, but it does not mean it is being used. The program (MAME) can and does have direct access to the input device (keyboard, mouse, etc.) which I have stated, gets combined into the legacy device. Which eventually gets sent to the virtual BIOS for those old programs that need it.
Heck even the remote desktop mouse and keyboard get combined into the legacy devices. MAME could be coded to use those as seperate input too. It would serve no purpose, which is why they are ignored to stop MAME users from complaining about it, but I digress.
The simple logic of the fact that MAME can access individual keyboards which you can not do with the BIOS, means something else must be going on.
Anyways, good luck and keep tring to connect the dots.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version