elo touchscreen files problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an ELO serial touchscreen monitor, and I'm trying to install the
component to use the touchscreen in the XP Embedded environment. I downloaded
the drivers for the touchscreen, got the .sld file, and added the "elo serial
touchmonitor interface" component on the target image. Then I built the
image. But after the FBA finishes, when the XP Embedded system starts to run,
it doesn't detect the file eloser.sys, and therefore the touchscreen doesnt
work. I checked the files included in the component, and it is included 3
times (in 2 different paths). But one of those three times, the file is 0
bytes long. That's strange. But I don't know why this happens. When I first
add the component, all files are included, with "normal" file sizes. But once
I check dependencies and build the target image, this one file without reason
converts to a 0 byte-size file. I hope someone can help me to find a solution
for this.
 
Thanks a lot for your help KM. But one thing, I have to change the COM port
from 1 to 4. And I don't find the friendly name where I can do that. Do you
have any suggestion to do that?

Juan Carlos
 
Juan, my company uses elo Touchscreens (1725L) with our XPe systems,
as well. Actually, we use two per system, one connected via USB and
the other serial (COM). I had to add eloser.sys manually in the C:
\Windows\system32 directory because it incorrectly looks for it there,
instead of C:\Windows\system32\drivers, where the rest of the files
are located. The COM1/COM4 issue is a new one, for me. Your default
serial port should be COM1, unless you're using a PCI expansion card
for the serial ports.

Oh, FYI, the USB connection creates a conflict that causes a blue
screen of death (BSoD) if you leave it enabled as a Generic HID
Device. Make sure that the touchscreen is listed under both mouse and
HID branches in the Device Manager. I simply removed the Generic HID
entry and it prevents that from happening on my systems. However, I
still have, as yet, to figure out how to get an unknown keyboard or
mouse to be recognized without it. Small matter, though. Our
application runs on a custom shell that doesn't allow user access to
Windows, anyway. You might say we've got "control issues."

Mucho gusto, señor.
- Jodie
 
Back
Top