View Single Post
Old 06-15-2016, 08:53 PM   #3
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
I tried to test this on my PW2 using USBnet (because flaky touchscreen). On this computer I have Tobii eye tracker drivers installed for some of my eye tracker development. My eye tracker device is not plugged in. My PW3 is detected as a Tobii eye tracker "networking device" and the WRONG DRIVERS are loaded into win10!

I was able to configure an IP address anyway, even though it identified as a Tobii eye tracker instead of RNDIS. It must just be a customized RNDIS driver. I got in via ssh on my win10 bash shell.

The lipc command fails on my recent firmware too. It worked on 5.6.5. Here was the reported error:
PHP Code:
com.lab126.pillow failed to set value for property configureChrome (0x8 lipcErrNoSuchProperty
It seems that recent firmware no longer supports the "configureChrome" lipc property.

Last edited by geekmaster; 06-16-2016 at 12:17 AM.
geekmaster is offline   Reply With Quote