eGalax touch screen- Windows 8 thinks it's a mouse

[DOSSTONED]

You still won't be able install them as they are self-signed. I'm not sure if you can install the certificate I created and this would be a security risk. Microsoft have just made the release candidate available and I'll be installing this over the British long weekend!

Actually I install the created certificate into Trusted Root Certification Authorities, it's still error 10. I also forced installed other vendors drivers, they all return error 10, the device cannot start. So is this driver designed for my device?
In hardware ID zone, I got USB\VID_0EEF&PID_0001&REV_0100 in first line and USB\VID_0EEF&PID_0001 in second line.

 

[KriLL3]

Urgh, Win8RP doesn't like "display1_downscalingsupported" it seems, every time I set it and then restart my monitor remains black, worked nicely in Win8CP

 

[coldcoffee]

*bamp* ... (less important text is grey)

Hi folks, i'm new here. Nice forum, thanks for the help so far.

I'm really interested in this affair, too. I'm testing Win 8 beta right now with a seperate HDD.

I have a "Lilliput" Touchscreen with exactly that eGalax TouchKit. It was previously mounted in my car (running WinXP...), but today my cell phone is much better and faster in navigation and entertaining than the "car-pc" ever was, so i stripped that setup down and "renaturalized" the car with a phone dock.

So i wanted to "recycle" the touchscreen now with Windows 8 as additional "metro-monitor" at my quite new machine. Wow, finally Microsoft delivers a really new and useful application for my screen!
Mounted it 45 degree, next to my keyboard, above my mouse.
On first sight it performs nice and handy and metro stays on this display while classical desktops stay on the other two big screens. Really nice so far.

But it's handicapped. I know this solution will never deliver multitouch but there is no swiping at all since it's recognized just as a mouse as you discribed it here. No real "touch feeling".

I have an "older" convertible laptop, too, that has a touchscreen. This one is "HID-compliant" and works much better when testing Win 8. Swiping no problem.

As you all mentioned, I installed a 32-Bit Win 8 on my main machine to test those mentioned beta-drivers. With (every incarnation of) them it works fine. Swiping, display keyboard and stuff. Like on the convertible.
But 32 Bit is no option later on a machine having 32GB of RAM.

So, reinstalled the Win8_x64, I tried all the way discribed to certificate this x64 beta driver. Every step worked! (It's not an absolute n00b writing here )
The created driver is installed and recognized successfully, I deactivated forced driver singing of course.
But I also just get as far as to an error code 10 (0x0a), that the device could not be started then.

I used WinMerge to compare the inf-files for differences with the inf-files of (those working) 32-Bit incarnations. No differences except the x64-stuff, looks like a standard 64-bit compliant for me. IDs are all correct. Of course i have not (/could not) look into the drivers *.sys-files.

Of course one could buy a more modern capacitive touchscreen. But where would be the fun in that? And also i refuse to do, 'cause in the end, it's a toy. So up to now, metro is more (interesting!) playing than working output. One should keep that in mind.
Although "this tiny additional touch on your desk" already performs nice as media player controller and even Media Center (MCE) controller and display, averting you with some television while browsing for other things or doing the correspondance. With the touch instead of mouse you even more quickly jump over the annoying commercials in the program.

So I hope this thread stays alive. I think you can gain benefit out of controversial metro with having a touch. But showing, that "old stuff" can do the thing, too!

Thanks for reading.

 

[dagobert]

Download this drivers: EETI eGalax Touch , http://www.ideacom.com.tw/download/DRIVE/setup_3.3.0000.05_WHQL.rar . The drivers are for W7 but works also on W8.

 

[coldcoffee]

Heyho, interesting reply Dagobert!
I tried a litte bit around with this driver. Unfortunately not *that* successfully ;-)
It does not work when installed alone (fresh Win8). What I can say, the eGalax Screen changes at least from it's not working Usbmini-Beta-Driver to "unknown device" when installing the new driver from ideacom. So at least there is some interaction. I tried a little bit replacing files between those two drivers, but without further success.
At least, looking deeper, the device id's do not match.
While the usbmini has the known
%eGalax.DeviceDesc0% = usbmini, USB\VID_0EEF&PID_0001
the ideacomuses several more (and different) lines
%IdcInst% =idcInst,USB\VID_1CB6&PID_6680
%IdcInst% =idcInst,USB\VID_1CB6&PID_6681
%IdcInst% =idcInst,USB\VID_1CB6&PID_1681
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6690
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6680&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6681&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_1681&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6690&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6650&MI_00
%ETTInst% =idcInst,USB\VID_22B9&PID_6681
%ETTInst% =idcInst2,USB\VID_22B9&PID_6681&MI_00
Is there any point of start changing the ID's there? Which driver to what? Uses usbmini.inf with idcfltr.sys or other way around or just add 0EEF&PID_0001 in idcfltr.inf? Of course all the certificate stuff has to be re-done then.
I'm not so much into drivers. It's more a trail&error right now. Would appreciate any suggestions directing to a solution and think there will be way more eGalax users when Win8 gets to final stages.

 

[DOSSTONED]

Heyho, interesting reply Dagobert!
I tried a litte bit around with this driver. Unfortunately not *that* successfully ;-)
It does not work when installed alone (fresh Win8). What I can say, the eGalax Screen changes at least from it's not working Usbmini-Beta-Driver to "unknown device" when installing the new driver from ideacom. So at least there is some interaction. I tried a little bit replacing files between those two drivers, but without further success.
At least, looking deeper, the device id's do not match.
While the usbmini has the known
%eGalax.DeviceDesc0% = usbmini, USB\VID_0EEF&PID_0001
the ideacomuses several more (and different) lines
%IdcInst% =idcInst,USB\VID_1CB6&PID_6680
%IdcInst% =idcInst,USB\VID_1CB6&PID_6681
%IdcInst% =idcInst,USB\VID_1CB6&PID_1681
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6690
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6680&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6681&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_1681&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6690&MI_00
%IdcInst% =idcInst2,USB\VID_1CB6&PID_6650&MI_00
%ETTInst% =idcInst,USB\VID_22B9&PID_6681
%ETTInst% =idcInst2,USB\VID_22B9&PID_6681&MI_00
Is there any point of start changing the ID's there? Which driver to what? Uses usbmini.inf with idcfltr.sys or other way around or just add 0EEF&PID_0001 in idcfltr.inf? Of course all the certificate stuff has to be re-done then.
I'm not so much into drivers. It's more a trail&error right now. Would appreciate any suggestions directing to a solution and think there will be way more eGalax users when Win8 gets to final stages.

Normally, there's always a pid/vid check in the driver entrance, if the pid/vid don't match, the driver do nothing. So changing the inf file cannot make sense.

 

[primo7]

Hi, i install Win 8 on my CarPC. ZOTAC ION ITX F-E mainboards and LinITX 7" Sunlight Readable Widescreen VGA/Composite with Touchscreen - 500 cd/m2 ( link: LinITX.com - LinITX 7" Sunlight Readable Widescreen VGA/Composite with Touchscreen - 500 cd/m2). During installation I use an normal monitor and than I have connected my Car LinItx monitor. I install eGalax driver from EETI eGalax Touch . But the touch screen not work at all. Windows only recognizes the touch screen as a mouse. So the same problem as net8021.
I appreciate any help.
Primo

 

[primo7]

Hi Doolster,

Go into the Device Manager, then Programs and Features, then click "turn windows features on or off" and scroll down to make sure that "tablet pc components"are enabled.

View attachment 5652

I do not have this option: "tablet pc components"

 

[KriLL3]

Does touch not work for any of your sans drivers? works out of the box for me except awful calibration

 

[coldcoffee]

Heyho Guys!

Just wanted to say i tried several changes and re-combinations of the availiable driver, files, IDs as mentioned before, but without any success. Still "device could not be started" error 10 (0x0a). Think you were right.
I'm going to give up the project. Always this ordeal with the signing and stuff. Ev'thing unhandy as my testing Win8 ist not really arranged. It's not funny anymore . Throw the "touch"screen, forget about it, don't waste precious time.

Anyway, so will enjoy Win8 just on the laptop.

Good luck to other tries.

 

[conandrum]

[!!!!!!!SOLVED!!!!!!] in Windows 7 x64
I also have an eGalax touch (usb version) on an Origen S21T case.
The eGalax drivers work fine, but break windows integration.
When I uninstall the drivers, Windows 7 automatically recognizes the touch screen functionality and enables all features except for calibration, inking, flicks etc. However, onscreen keyboard is there on the login screen and docked when I log in.

The way I solved it was by a simple modification to the registry. All remaining features came back as soon as I logged out and back in again. Now I can calibrate, do inking in Office, flick in firefox etc! Remember, I removed the eGalax driver and let windows install a default driver (USB input device).

Here is the registry key.

please do not blame me if you mess up your registry. Back up the key first before you do anything.
Then, copy paste the following text leaving out the dotted line, into notepad and save it as xxxx.reg on your desktop.
Then double-click on it to insert it into the registry.

Good luck and I hope this solves it for some of you at least!

-------------------------------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}]
"@"="wisptis"
"RunAs"="Interactive User"
"LaunchPermission"=hex:01,00,14,80,64,00,00,00,74,00,00,00,14,00,00,00,30,00,\
00,00,02,00,1c,00,01,00,00,00,11,00,14,00,04,00,00,00,01,01,00,00,00,00,00,\
10,00,10,00,00,02,00,34,00,02,00,00,00,00,00,18,00,1f,00,00,00,01,02,00,00,\
00,00,00,05,20,00,00,00,20,02,00,00,00,00,14,00,0b,00,00,00,01,01,00,00,00,\
00,00,01,00,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,\
00,00,00,00,00,05,20,00,00,00,20,02,00,00
-----------------------------------------------------------------------------------

 

[coldcoffee]

Heyho conandrum!
Very interesting. Could you explain it a little bit more? Exact steps? Which exact driver did you use? Original one? (The official "All_In_One" or the newer 5.11?). There are so many drivers mentioned in this thread, especially x64...

Where do you have those reg entries from?
Thanks a lot for any response!!

Edit: I found these entries on my machine, too. Already there but no functionality. What am I doing wrong? Thanks for any answers.
Oh, and I have an additional dword called "PreferredServerBitness" in there, its value is 0x3.

 

[ztec]

I have the same issue , and the tip of the registry tweak don't work on me at all. Windows say to me that I have no right to modify the registry keys. I tried changing right and set Full control to Administrator, but nothing work.

How can I put data in this key and force windows giving me the right change data at this place in the registry ?

My account is an administrator account. I event try with the real administrator account, and run as admin regedit .....

 

[FSeal]

I have the same issue , and the tip of the registry tweak don't work on me at all. Windows say to me that I have no right to modify the registry keys. I tried changing right and set Full control to Administrator, but nothing work.

How can I put data in this key and force windows giving me the right change data at this place in the registry ?

My account is an administrator account. I event try with the real administrator account, and run as admin regedit .....

Right click and add your actual user account to the permissions list and give full control. Has to be the actual account you are logged in as. Though you may be an admin (which is the only reason you are allowed to change permissions in the first place) you are not logged in as "Administrator" which is why that didn't work.

 

[ztec]

I have the same issue , and the tip of the registry tweak don't work on me at all. Windows say to me that I have no right to modify the registry keys. I tried changing right and set Full control to Administrator, but nothing work.

How can I put data in this key and force windows giving me the right change data at this place in the registry ?

My account is an administrator account. I event try with the real administrator account, and run as admin regedit .....

Right click and add your actual user account to the permissions list and give full control. Has to be the actual account you are logged in as. Though you may be an admin (which is the only reason you are allowed to change permissions in the first place) you are not logged in as "Administrator" which is why that didn't work.

Thanks, but this didn't work.
I had to put my user into the owner field and then i was allowed to modify data.


to get back to the topic, the registry tweak does nothing on my computer. the touchscreen still act as a mouse and is't calibrated , so unusable.

 

[conandrum]

Hi guys,
I do not remember the website address but it was an official microsoft user forum where microsoft certified people help others find solutions. This tip was posted by someone who was given the tip from a call to microsoft.
Now, as I said in my post, I DID NOT INSTALL THE eGalax driver. If you have it installed, UNINSTALL IT if you want windows inking, flicking, etc functionality. If you keep the eGalax, all you have is a glorified mouse driver! (FYI, I did install the eGalax latest driver posted on the website eGalaxTouch_7_Vista_XP_2K_5.11.0.9126.zip I also tried the driver posted on the origenae website for S21T Win7_5.6.0.6806.zip. Both excibited the same useless behaviour for my liking so I uninstalled them or restored my machine from a previous backup before the install took place. In both cases, my solution works - there is no need for the eGalax driver in my case - it fixes nothing).

OK. without the eGalax driver installed, Windows 7 on my machine is able to recognize my display and installs a generic driver for it. I have NO UNRECOGNIZED DEVICES in my device manager without having to install ANYTHING - all done by windows 7 by default. The 2 devices that windows installs are a HID compliant mouse (hardware ID=HID\VID_0EEF&PID_0001&REV_0100&Col01) (same ms driver as any other HID compliant mouse) and a USB input device (hardware ID=USB\VID_0EEF&PID_0001&REV_0100) (same ms driver as any other USB input device) - so generic drivers for generic functionality. (if you ever install the eGalax drivers, these devices are changed to other devices with other hardware ID - If you uninstall the driver, they return back to the above).

To prove that my Windows installation was recognizing the touchscreen I went to my control panel. There, if you search for tablet (in control panel search at top right), I could see listed, 'Tablet PC Settings' & 'Pen & Touch'. If you do not have those listed, then you have to look else-where for a solution. If you do, read on. Also, when I am on the login screen, at the bottom left corner I have 2 buttons - 1 is for accessibility features and the other is the tablet pc keyboard. When I click this button, the onscreen keyboard is ALWAYS displayed by default on the login screen (this is NOT the popup keyboard). Furthermore, when I tap on my touchscreen, the keyboard is shown docked on the left side of my screen ready to be tapped upon to be flown into the screen center for typing. All these features show us that Windows is functioning as a tablet.

My problems began here. My screen needed CALIBRATION because pen input was not accurate.
To calibrate the screen you must go to Tablet PC settings in control panel. However, ALL BUTTONS there including the calibrate button were greyed out. I also noticed that I could not draw in MS Word or One Note (Error 'Tablet drivers are not installed on the system. You must install them to enable Tablet features').

The solution I posted in my earlier post SOLVED my problem. If you are facing a similar problem it could be what you need.

 

[coldcoffee]

Thanks, but this didn't work.
I had to put my user into the owner field and then i was allowed to modify data.

You have to take over the possession of this reg-entry to your user (click the advanced button in the middle of the menu you already were (to change access rights) and then go on to "change owner", select your user). After that you can change the rights as you prefer in previous menu. (Sry, maybe buttons/tabs are named little different, my windows is not english...)
--------
Thanks for the comprehensive explanation conandrum, I really appreciate it!
Unfortunately still could not re-enact it now with my Win7. My Win8-Test is unfortunately inaccessable, I'm not even able to reboot my Win7 for the next week or so. But maybe I have (legal) access to Win8 Final/RTM in 2-3 weeks and then will try using a fresh installation. My Win7 is quite clogged up by different touch drivers (touchscreen not working at all at the moment - but not that neccessary as it's Win7) and as I said even can't be rebooted right now.

Windows 7 on my machine is able to recognize my display and installs a generic driver for it.

Unfortunately, what I remeber is: Windows 7 has no driver but gives you a link to eGalax. It's the All_In_One, and works the handicapped mouse-replacement way. But this was some time ago when i installed Win7. Maybe driver availibility has changed in-between. But the Win8 beta did not have one either. Maybe, our eGalax screens (foils) are different models. Then me and others would be still stranded.

 

[coldcoffee]

Sorry. Obviously I'm unable to read what I quote, you already took the rights of the entry, ztec.

 

[ztec]

Hi guys,
I do not remember the website address but it was an official microsoft user forum where microsoft certified people help others find solutions. This tip was posted by someone who was given the tip from a call to microsoft.
Now, as I said in my post, I DID NOT INSTALL THE eGalax driver. If you have it installed, UNINSTALL IT if you want windows inking, flicking, etc functionality. If you keep the eGalax, all you have is a glorified mouse driver! (FYI, I did install the eGalax latest driver posted on the website eGalaxTouch_7_Vista_XP_2K_5.11.0.9126.zip I also tried the driver posted on the origenae website for S21T Win7_5.6.0.6806.zip. Both excibited the same useless behaviour for my liking so I uninstalled them or restored my machine from a previous backup before the install took place. In both cases, my solution works - there is no need for the eGalax driver in my case - it fixes nothing).

OK. without the eGalax driver installed, Windows 7 on my machine is able to recognize my display and installs a generic driver for it. I have NO UNRECOGNIZED DEVICES in my device manager without having to install ANYTHING - all done by windows 7 by default. The 2 devices that windows installs are a HID compliant mouse (hardware ID=HID\VID_0EEF&PID_0001&REV_0100&Col01) (same ms driver as any other HID compliant mouse) and a USB input device (hardware ID=USB\VID_0EEF&PID_0001&REV_0100) (same ms driver as any other USB input device) - so generic drivers for generic functionality. (if you ever install the eGalax drivers, these devices are changed to other devices with other hardware ID - If you uninstall the driver, they return back to the above).

To prove that my Windows installation was recognizing the touchscreen I went to my control panel. There, if you search for tablet (in control panel search at top right), I could see listed, 'Tablet PC Settings' & 'Pen & Touch'. If you do not have those listed, then you have to look else-where for a solution. If you do, read on. Also, when I am on the login screen, at the bottom left corner I have 2 buttons - 1 is for accessibility features and the other is the tablet pc keyboard. When I click this button, the onscreen keyboard is ALWAYS displayed by default on the login screen (this is NOT the popup keyboard). Furthermore, when I tap on my touchscreen, the keyboard is shown docked on the left side of my screen ready to be tapped upon to be flown into the screen center for typing. All these features show us that Windows is functioning as a tablet.

My problems began here. My screen needed CALIBRATION because pen input was not accurate.
To calibrate the screen you must go to Tablet PC settings in control panel. However, ALL BUTTONS there including the calibrate button were greyed out. I also noticed that I could not draw in MS Word or One Note (Error 'Tablet drivers are not installed on the system. You must install them to enable Tablet features').

The solution I posted in my earlier post SOLVED my problem. If you are facing a similar problem it could be what you need.

I tried everything said in this topic, nothing work. Event the original driver does not work. the touch screen is not detected and cannot be calibrated.

i tested on win 7, 8 fresh install multiple times.

my screen isn't calibrated and the up/down is reversed (only up/down):-(

I don't understand how to make this thing work !!!


edit : I have the tablet config in the panel config and calibration button are not disable. the calibration tool actually lunch it self, but no touch the screen don,t do anything !!!

 

[coldcoffee]

Ok, I don't even get the tablet config in the control panel. No matter what configuration.
I also only have one device in the device manager, only the mouse, no USB-input device in HID. If i force it to the usb-input device (input.inf instead of msmouse.inf), the other device is gone (of course) and device cannot be started (code 0xa) as always.
Upside-down problem i had once, too (Win8), but no real touch was there as always.
Funnily, i want it to be upside-down in the end (for45°mount), but always stayed upright for testing purposes.

Ok it's late (here). And didn't i want to stop to play around with that stuff some time ago?