by Pr0n » Tue Jan 15, 2013 1:52 pm
calli wrote:n1k wrote:With an IEM 3.0 and Win 7 x64 myself i was about to post the same trick from the link, but with 2 additional steps. On "check the Filter on Device box and select your desired sample rate" you should press install service after, and if you are also on x64 bit windows, then you should repeat "choose Sign a System file and insert full path to the installed HIDUSBF.sys file (For example: C:\Windows\System32\Drivers\HIDUSBF.sys)" on C:\Windows\SysWOW64\Drivers\HIDUSBF.sys also. Hope it helps, it works flawlessly for me since Windows 7 release.
Did what you said since I had forgotten to Sign a system file to the 64 system files. And also I didnt push Install Service.
But it doesnt work, my 3.0 is dead. But when I connect my steelseries in that port it works, with a rate of 500.....
Did what this guy said:
https://www.youtube.com/watch?v=0_hZipKt72M
you are talking about two different drivers here i assume, the ports got nothing to do with how the systems behind work, it's all driver based. If the Intelli driver isn't the same as the steelseries driver which i doubt (but cant confirm due to the fact i never used any of those mice), the comparison of these 2 mice doesn't tell us anything.
one thing that maybe works is using compatibility mod and set it to windows XP SP3 if it's and *.exe or *.msi file for install progress if you just got *.sys or *.dll files i dont now if it works and before every new install attempt you better get rid of all old driver files (files and data). You may should check if you in general installed drivers from the manufacturer (chipset, Audio, etc.) and not the partially generic driver shit windows update is installing.
the other thing i would try to check, even though it probably is hard, since these work around seems to work on other windows 7 systems but yours. Set up a virtual machine and test it with an empty system if it works there then another driver or program is coursing the problems you are currently experiencing.
hopefully this helps at least a little bit, like i said before never used that mice so all above isn't from something i ever tried out practically, just a hunch due to experience with driver problems
[quote="calli"][quote="n1k"]With an IEM 3.0 and Win 7 x64 myself i was about to post the same trick from the link, but with 2 additional steps. On "check the Filter on Device box and select your desired sample rate" you should press install service after, and if you are also on x64 bit windows, then you should repeat "choose Sign a System file and insert full path to the installed HIDUSBF.sys file (For example: C:\Windows\System32\Drivers\HIDUSBF.sys)" on C:\Windows\SysWOW64\Drivers\HIDUSBF.sys also. Hope it helps, it works flawlessly for me since Windows 7 release.[/quote]
Did what you said since I had forgotten to Sign a system file to the 64 system files. And also I didnt push Install Service.
But it doesnt work, my 3.0 is dead. But when I connect my steelseries in that port it works, with a rate of 500.....
Did what this guy said: https://www.youtube.com/watch?v=0_hZipKt72M[/quote]
you are talking about two different drivers here i assume, the ports got nothing to do with how the systems behind work, it's all driver based. If the Intelli driver isn't the same as the steelseries driver which i doubt (but cant confirm due to the fact i never used any of those mice), the comparison of these 2 mice doesn't tell us anything.
one thing that maybe works is using compatibility mod and set it to windows XP SP3 if it's and *.exe or *.msi file for install progress if you just got *.sys or *.dll files i dont now if it works and before every new install attempt you better get rid of all old driver files (files and data). You may should check if you in general installed drivers from the manufacturer (chipset, Audio, etc.) and not the partially generic driver shit windows update is installing.
the other thing i would try to check, even though it probably is hard, since these work around seems to work on other windows 7 systems but yours. Set up a virtual machine and test it with an empty system if it works there then another driver or program is coursing the problems you are currently experiencing.
hopefully this helps at least a little bit, like i said before never used that mice so all above isn't from something i ever tried out practically, just a hunch due to experience with driver problems :D