home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Products
IR Server Suite (IRSS)
IMON support
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="belcom" data-source="post: 523961" data-attributes="member: 89055"><p>Any version fails?? From other users I heard, that 3120 works, while 3127 doesn't.</p><p></p><p>Sideinfo:</p><p>Basically you are right, Windows blocks direct hardware access to well known HID devices like Mouse and Keyboard, but we don't connect directely to the hardware layer but to a Windows software layer which collects, shares and manages access to such devices, called "rawInputDevices". It's a function of user32.dll and not available in any other context. The dll itself is only available to logged in users and thats why access to HID only works with IRSS as application in Vista and newer.</p><p></p><p>Back to the road:</p><p>My iMON device (have the same like you, Vid_15c2&Pid_0038) is also handled by standard Microsoft HID drivers. And it works.</p><p>After doing a lot of different tests with different OS'es, IRSS, MP and iMON Manager versions (all worked as expected), I'm pretty sure that the cause of your problem is a very very strange thing happening in background. Maybe there's something left from a very old installation, which interacts... or something else?? I really don't know it by now.</p><p></p><p>But please, don't give up on giving me hints! Even if I clarify that it couldn't be the problem. Coming closer to the cause by excluding working things may be also a way <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /> guys for your support and patience!</p></blockquote><p></p>
[QUOTE="belcom, post: 523961, member: 89055"] Any version fails?? From other users I heard, that 3120 works, while 3127 doesn't. Sideinfo: Basically you are right, Windows blocks direct hardware access to well known HID devices like Mouse and Keyboard, but we don't connect directely to the hardware layer but to a Windows software layer which collects, shares and manages access to such devices, called "rawInputDevices". It's a function of user32.dll and not available in any other context. The dll itself is only available to logged in users and thats why access to HID only works with IRSS as application in Vista and newer. Back to the road: My iMON device (have the same like you, Vid_15c2&Pid_0038) is also handled by standard Microsoft HID drivers. And it works. After doing a lot of different tests with different OS'es, IRSS, MP and iMON Manager versions (all worked as expected), I'm pretty sure that the cause of your problem is a very very strange thing happening in background. Maybe there's something left from a very old installation, which interacts... or something else?? I really don't know it by now. But please, don't give up on giving me hints! Even if I clarify that it couldn't be the problem. Coming closer to the cause by excluding working things may be also a way :) :thx: guys for your support and patience! [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
IR Server Suite (IRSS)
IMON support
Contact us
RSS
Top
Bottom