Touchkit problem

RyanB95 · 08-19-2008, 09:34 PM

Hey guys,

I'm just wondering if anyone else has had trouble with Touchkit recognizing their touchscreen being plugged into a USB port? Upon searching I found a bunch of threads regarding the touchscreen controller's functionality itself -- I don't believe that's my problem at all though, rather just getting the touchkit to recognize that my touch panel is actually plugged into the USB port. I say that the touch controller itself is not broken because I had it working last week... but I unplugged everything from it and powered the carPC down while I relocated it within the car. After I plugged everything back in, the touchscreen failed to work. Whether or not I plugged the USB back into the same port that touchkit had it assigned to I'm not sure. But since it didn't work initially after the move, I tried all other ports and have been un and re-installing the drivers ever since with no luck. Is there any sort of combination or trick to getting it to work right without thinking that the mouse I have plugged in is the touch controller (it did that once or twice)? I've tried it with the mouse plugged into a USB port and with it plugged into a PS/2 port with no luck. Any suggestions?

Thanks!

RyanB95 · 08-21-2008, 05:07 PM

No one?

russoxley187 · 08-21-2008, 05:10 PM

drivers?

RyanB95 · 08-21-2008, 09:02 PM

I'm using the same ones that I used when I had it working before

pancit175 · 08-21-2008, 09:08 PM

Try reinstalling the drivers. In some cases i have seen with some USB devices, the protocol that designates the location of the device, as far as wiring through which ports or through a hub, may not have been reinitiallized when you changed the port.
For example, I have the turtle beach advantage micro usb sound-dongle. If I unplug it while shutdown, move it over one plug and restart, before I can be used again I have to reinitallize it, but I have to do it manually which they have set through the taskbar icon.

RyanB95 · 08-21-2008, 11:27 PM

I've tried reinstalling the drivers a few times with no luck. I feel like theres a trick to get it working with my particular setup. I guess I'm just gonna have to mess with it some more unless anyone has any other suggestions.