Denmark
Great explanation, really explains everything about the troubles we're having. I added you to my msn, i have a lot of time the following week.
IMON support (1 Viewer)
- Thread starter chemelli
- Start date
according log file, you have the same situation as me.
"Device VID:15C2, PID:0038 cannot be opened." It's caused by exclusive use these HID devices (mouse, keyboard) by system. Because windows have used regular drivers for HID-mouse, HID-keyboard which have HID_SYSTEM_MOUSE and HID_SYSTEM_KEYBOARD are set, what dictate to use these devices by system exclusively (to prevent key logging by security reason)
I've no solution yet. Anyone?
There are some guys having this problem with newest build, but right now we don't know why.
One of them already agreed in helping us find the issue.
Pls stay tuned!
according log file, you have the same situation as me.Here u go
"Device VID:15C2, PID:0038 cannot be opened." It's caused by exclusive use these HID devices (mouse, keyboard) by system. Because windows have used regular drivers for HID-mouse, HID-keyboard which have HID_SYSTEM_MOUSE and HID_SYSTEM_KEYBOARD are set, what dictate to use these devices by system exclusively (to prevent key logging by security reason)
I've no solution yet. Anyone?
There are some guys having this problem with newest build, but right now we don't know why.
One of them already agreed in helping us find the issue.
Pls stay tuned!
Belcom, thank you for your efforts.
My investigations says that any version of IRSS i've tried had failed. Because of exclusive use of devices according http://www.microsoft.com/taiwan/whdc/archive/HID_HWID.mspx , if there is anybody who has working IRSS with iMON could check the provider of drivers for HID-devices and Hardware ID's in their properties (in device manager).
Mine for 15C2:0038 are exact Microsoft and HID_SYSTEM_MOUSE/HID_SYSTEM_KEYBOARD, which says that device cannot be opened anyhow.
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
guys for your support and patience!i did some further testing today and it was a bit strange. I uninstalled 3217 and completely deleted everything that belongs to irss and tried to install 3217 with the same (non working) result. After that i went back to 3120 and it did not work either. So i decided to go back to 3099 and guess what i did not work. Of course i did several reboots and even completly shut down my pc. After all that did not work i decided to check my imon version, so i opened up imon, looked up my version, closed it - and guess what irss worked, the error in the log was gone.
So i installed 3217 fired up imon and now it's working. This might be all a coincidence but maybe it helps. Right now were going to watch a movie so i can't do any more testing, but tomorrow i will investigate it further
Joe
So i installed 3217 fired up imon and now it's working. This might be all a coincidence but maybe it helps. Right now were going to watch a movie so i can't do any more testing, but tomorrow i will investigate it further
Joe
Hmm tried the same, but didn't work. Belcom is currently in a remote session with me. But no luck until now.
Ok. After a lot of trying we made some progress.
Belcom had a newer firmware than me and that changes apparently something.
We tried to make a USB over network connection, but the imon device was quite buggy and this didn't succeed. I contacted Fabula Tech, the maker of USB over network, and their developers are looking into this problem. I tried with a new driver, but no luck. The device remains buggy and caused a few BSOD.
So tomorrow i have a appointment with them and their senior USB over Network developer. If this succeeds Belcom is able to remote control my imon device and will make this a bit easier than remote control.
Neither the less Belcom tried to change some code in his test app for imon devices and made that made it possible to us to find out that there are a few seconds between the clicks. After trying to adapt this to Irss build 3128 this happened:
You could change between them and they still worked.
We still need to investigate this further though:
And test if it's stable and running good enough and of cause maybe some more. Thanks to Belcom this i probably soon working after spending quite some time looking into i.
JoeSmith: I think we have the same case, Thermaltake 101, if you have the same firmware version this should work for you too.
Belcom had a newer firmware than me and that changes apparently something.
We tried to make a USB over network connection, but the imon device was quite buggy and this didn't succeed. I contacted Fabula Tech, the maker of USB over network, and their developers are looking into this problem. I tried with a new driver, but no luck. The device remains buggy and caused a few BSOD.
So tomorrow i have a appointment with them and their senior USB over Network developer. If this succeeds Belcom is able to remote control my imon device and will make this a bit easier than remote control.
Neither the less Belcom tried to change some code in his test app for imon devices and made that made it possible to us to find out that there are a few seconds between the clicks. After trying to adapt this to Irss build 3128 this happened:
- Imon remote: Works with both mouse and keyboard
- MCE: Works
You could change between them and they still worked.
We still need to investigate this further though:
- Imon reverst to default(imon pad) when system shuts down. If it were possible to avoid this we're able to turn on our htpc with MCE remote as it's working for the imon pad.
- Need to test this with MP plugin.
- And to test it with minidisplay running in MP
And test if it's stable and running good enough and of cause maybe some more.
Thanks to Belcom this i probably soon working after spending quite some time looking into i.JoeSmith: I think we have the same case, Thermaltake 101, if you have the same firmware version this should work for you too.
1stdead:
First of all i have to apologize for leading you on the wrong trail. Here is what happened:
I uninstalled 3127 as it did not work. I went down to 3120 and it didn't work anymore. Went up to 3127 - didn't work.I went down to 3099 and it did not work. I started imon to look up my imon version (7.64.0930, IMON Firmware Ver. 0x3801, LCD HID OEM) and suddenly it worked again, and i thought i was still on 3127.
I've never had a problem with irss and my imon before and i'm using it at last until 2975 (thats the one that i still have in my download folder, i guess im using it much longer)
Today i upgraded from the (still working) 3099 to 3120 and its not working right now (but that has been working before for ~ 1 week, without a single detection problem).
I'll try various things today and see what is going to happen.
Thanks
Joe
edit : now all of a sudden after reboot x 3120 suddenly works. i'll do some reboots to see if that stays that way (but i guess it will because i had it running that way for some time)
First of all i have to apologize for leading you on the wrong trail. Here is what happened:
I uninstalled 3127 as it did not work. I went down to 3120 and it didn't work anymore. Went up to 3127 - didn't work.I went down to 3099 and it did not work. I started imon to look up my imon version (7.64.0930, IMON Firmware Ver. 0x3801, LCD HID OEM) and suddenly it worked again, and i thought i was still on 3127.
I've never had a problem with irss and my imon before and i'm using it at last until 2975 (thats the one that i still have in my download folder, i guess im using it much longer)
Today i upgraded from the (still working) 3099 to 3120 and its not working right now (but that has been working before for ~ 1 week, without a single detection problem).
I'll try various things today and see what is going to happen.
Thanks
Joe
edit : now all of a sudden after reboot x 3120 suddenly works. i'll do some reboots to see if that stays that way (but i guess it will because i had it running that way for some time)
Please tell us your Firmware version.
And may you can check and provide logs with newest build? (3129)