Help... Problems with touch screen - lose settings after reboot

[AS]

Hi All,

I'm posting this again coz I've still not been able to resolve the issue...
I have an Advantech board with xpe loaded... I want to get the touch screen
working.. For this I loaded the Dynaprosc3 component from xpefiles.com and
included that as part of my image.. I also have the std components,
ntloader, fat, fat format,
acpi,english langugae, UI core, Winlogon, explorer shell, ole dialog etc as
well as my devices and dynapro component.

After FBA runs w/o any errors, I don't see any touch features the next time
the device comes up.. Even though I have the dynapro app inside the
C:\Programs Files\ folder, I don't see it in the Start->Programs menu. So I
install the touch screen app manually by running the corresponding exe file.
I can see the app has installed in the Start->Programs-> folder. After
that I at least get the touch features (when I tap, I can see the pointer
move somewhere) and I calibrate it and things seem fine until I reboot...
After reboot, the app is still there in the Start->programs-> folder but no
touch features, the mouse pointer doesn't seem to move if I tap the screen.
If I try to recalibrate it, it seems to recognize the touch taps that I make
during calibration (i.e. doesn't time out) but once again, no touch after
that..If I install the app again, I know it'll work fine. But I cannot
accept that..

I'd appreciate any help or ideas on what I should be doing.. or any
components, I should be adding to get it to work...

Thanks
Regards,

 

[Mario Dambauer]

I had simmilar problems with my touch screen... (Elo Touch Serial)
I am not exactly sure, but I think it was Terminal Services Core Component
which overwrites my touch screen reg entrys.

At pre SP1 I solved the problem in that way, that I didn't add this
component...

But At XPE with SP1 the problem had gone away, so check out if you are using
SP1!


Best Regards,
Mario

 

[Roy Hodgkinson]

AS

Have you tested the Touchscreen install and subsequent
behavior on a full XP Image?

Touch screens need to wait until Port enumeration is
complete before they can initialize for touch input; some
use services, others a registry Run key executable. Most
have a registry setting identifying the port name to be
used (COM1, etc.).

Checking these items as possible sources of the failure
may help. Otherwise, you can probably get assistance from
the touch screen vendor website or tech support -- but
often only for issues you can re-create on a full XP
image.

I use both ELO and Microtouch serial touch screens. If I
try to load both drivers on my XPE image they "fight" for
COM1 resources and both fail. I chose to install each one
manually on top of my XPE image, reseal and capture with
Ghost.

HTH, Roy

 

[Mario Dambauer]

At elo touch the com port is only one reg entry.
I think at microtouch this could be the same, so I would modify the inf
files to set elo to e.g. com 1 and microtouch to com 2.

At first boot I would detect if elo is really connected to com1.
if yes than there is no conflict and the driver works.

if elo is not connected to com1 than change elo com port to another and set
microtouch to com1, reboot and check if microtouch is connected...

This is only a alternative, to manually install the drivers....

Best Regards,
Mario

 

[AS]

Well, I use Win2000 on the development platform and it works fine there, and
I was thinking the settings would be very similar on XP too.. Are there a
lot of differences .??.
Mine uses USB instead of COM1 so I changed the port type to USB instead of
COM1. This helped resolve conflicts with the mouse as earlier the mouse
stopped working when the touch worked..

Also I'm using XPe with SP1 so the other issue wouldn't be a problem and I'm
also not using the terminal services component..
How do you get the system to load them manually and do the reseal.. My
C:\windows\fba\ dir only has the fba.exe in it and no fbareseal and
C:\windows\ has the fbastart.exe none of which work after the image
completes fba..

Thanks,
Regards,
AS

 

[Guest]

AS,

Add FBReseal.exe to your image -- its in the System
Cloning Tool component.

Make all your changes to your fully booted XP Embedded
image. Here's the checklist I use before Reseal and image
capture (you may not care about some of these steps and
you may not have all the tools in your image).

· Delete all *.log files in the C:\WINNT folder (but not
those in its sub-folders).
· Clear the Recycle Bin
· Clear Event Logs
· Clear remembered docs from Taskbar menu
· Change Control Panel | Mouse | Pointers | Scheme to Elo
· Start | Run to open a CMD window
· Release the IP address
· In the command window, navigate to C:\WINNT\System32
· Run FBReseal.exe
· Close the Command window
· A message box will pop up saying "Machine resealed.
Press OK to reboot".
· Enter OK and allow Windows XPE to shutdown. Do not
allow machine to reboot from the hard drive.
· Capture the drive image as your new master.

Roy

 

[Roy Hodgkinson]

Mario,

Thank you. My situation is that I support multiple
hardware configurations (motherboards, display adapters,
monitors, flat panels) with one common XPE image. Because
both the ELO and Microtouch screens will need to use
COM1, I just leave the drivers out of TD. I then add each
of them to a post-FBA image, Reseal, and capture a
separate GHOST image for each configuration (more details
in my reply to AS above). This also allows me to set the
Display resolution, color depth etc. for the same driver
differently in each GHOST image as needed.

Roy