How to block specific vendor's PS/2 Keyboard?

Hi,

I am writing a keyboard filter driver to block a specific vendor’s PS/2 keyboard. But I am getting a generic pnp**** as the device/vendor id for all PS/2 keyboards irrespective of the vendor. What is the way to get the real Vendor/Device id of PS/2 keyboard? Or is there any other way to block a specific vendor’s keyboard?

Thanks in advance.

Waiting for your suggestions.
Girish

xxxxx@rediffmail.com wrote:

I am writing a keyboard filter driver to block a specific vendor’s PS/2 keyboard. But I am getting a generic pnp**** as the device/vendor id for all PS/2 keyboards irrespective of the vendor. What is the way to get the real Vendor/Device id of PS/2 keyboard? Or is there any other way to block a specific vendor’s keyboard?

PS/2 devices do not have vendor and device IDs. They are all
indistinguishable from one another, other than some
manufacturer-specific extensions.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Thank you TIM!. So is there any way to distinguish between PS/2 keyboards?

I may have missed the original post, so please accept my apologies if this
has already been answered. I’m curious as to why you would want to block a
specific vendor’s keyboard. Is there something this keyboard does that
causes problems or just general curiosity?

Thanks,
Greg

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, June 30, 2009 12:07 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] How to block specific vendor’s PS/2 Keyboard?

xxxxx@rediffmail.com wrote:

I am writing a keyboard filter driver to block a specific vendor’s PS/2
keyboard. But I am getting a generic pnp**** as the device/vendor id for all
PS/2 keyboards irrespective of the vendor. What is the way to get the real
Vendor/Device id of PS/2 keyboard? Or is there any other way to block a
specific vendor’s keyboard?

PS/2 devices do not have vendor and device IDs. They are all
indistinguishable from one another, other than some manufacturer-specific
extensions.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

xxxxx@rediffmail.com wrote:

Thank you TIM!. So is there any way to distinguish between PS/2 keyboards?

Not in the general case, no. There is a “send keyboard ID” function,
but that identifies the basic set of keys that it supports, not the
individual keyboard.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

I want to reiterate what greg asked. What feature on the keyboard makes you think that you want to block it? it has certain extra keys like volume +/-? Or it has extra hw features like a card swipe?

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Gregory Dyess
Sent: Tuesday, June 30, 2009 10:20 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to block specific vendor’s PS/2 Keyboard?

I may have missed the original post, so please accept my apologies if this has already been answered. I’m curious as to why you would want to block a specific vendor’s keyboard. Is there something this keyboard does that causes problems or just general curiosity?

Thanks,
Greg

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, June 30, 2009 12:07 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] How to block specific vendor’s PS/2 Keyboard?

xxxxx@rediffmail.com wrote:

I am writing a keyboard filter driver to block a specific vendor’s
PS/2
keyboard. But I am getting a generic pnp**** as the device/vendor id for all
PS/2 keyboards irrespective of the vendor. What is the way to get the real Vendor/Device id of PS/2 keyboard? Or is there any other way to block a specific vendor’s keyboard?

PS/2 devices do not have vendor and device IDs. They are all indistinguishable from one another, other than some manufacturer-specific extensions.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Hi,
Sorry for the long delay. I didn’t check this thread after getting the answer “NO”.

Actually I want to block specific keyboards based on the keyboard layout. For example, a keyboard designed for french layout should not work for other layouts. I am able to do this with USB keyboards because it has device/vendor id. I hope I have to forget about PS/2 now, right?

forget about ps2. the layout is determined by the user after the fact. even usb HID is not that reliable, the same keyboard (e.g. same vid / pid) can be released in different countries with different layouts screened onto the keys.

d

I agree with Doron that you should forget trying to base anything on
PS/2 PNPIDs, because there’s not much you can *do* about that problem
(short of asking the user)… but it isn’t safe to completely ignore
them either. Essentially 100% of notebook keyboards are PS/2.

xxxxx@Microsoft.com wrote:

forget about ps2. the layout is determined by the user after the fact. even usb HID is not that reliable, the same keyboard (e.g. same vid / pid) can be released in different countries with different layouts screened onto the keys.

d

OK. Thank you All for your suggestions!

Girish.