Touch screen driver in Win CE 6.0

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

Guest

Hi
I am creating the Win CE OS in VS 2005. I am adding the touch screen drivers
supplied by the vendor by referncing them in subprojects (pbpxml) and
building the OS.
Once deployed, when I boot the OS, the touch screen LCD is not working. The
LCD shows the picture and stuff but the touch is not working.
There is a alignment exe which came with the monitor. When I build that in
the OS and double click on that in Windows CE, nothing happens.
Please help!! Am stuck on this big time..

Thanks
Rama
 
Sorry... forgot to add that I am working on Windows CE 6.0. Even the touch
screen driver is for Win CE 6.
 
Serial debug messages? It could be practically anything. My guesses would
be: 1) missing the registry entries to start the driver, 2) missing the
driver itself because you didn't put it in a BIB file, 3) you put it in the
BIB file, but not as a kernel mode driver and it won't work as a user mode
driver, but there's no obviously-right
here's-why-your-touchscreen-driver-doesn't-load-typically answer...

Paul T.
 
Thanks a lot for the reply Paul.
1. From Vendor's instructions, I learnt that the registry (.reg) files will
be automatically included in the OS and be a part of the registry in the OS.
There is indeed a reg file in the driver.Can you lead me to some place where
I can see how to write registry values when building the OS?

2 & 3. I did put in a bib file but I guess it is a user driver. How do I
make it a kernel driver?

Just one doubt. I download the OS from VS 2005 at run time to my ebox 2300.
Do you think the problem is due to this? If I make it as a permanent NK.bin
and save it, will it work? Sounds silly but I am desperate now :0)...

Appreciate your response.
 
1. There are many ways to get things into the registry. If you don't know
what most of those are from experience, I can't really help in a newsgroup.
Check reginit.ini in the flat release folder after you've built the OS and
see if the entries you tried to add are there.

2. Read the help.

If it doesn't work as a downloaded nk.bin file, it won't work as a flashed
nk.bin file, either.

If you don't find a problem, other than reading the debug messages, I can
only suggest setting a breakpoint or two in the driver to see if it's loaded
at all (it might be loading and then return an error because your settings
for things like the interrupt number, base address, etc. are wrong in your
registry).

Paul T.
 
I should also ask why the heck we're covering questions that have *nothing*
to do with the .NET Compact Framework in
microsoft.public.dotnet.framework.compactframework? Why not
microsoft.public.windowsce.platbuilder?

Paul T.

"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:[email protected]...
 
Thank you for the hints Paul. I will try this out.
Apologise for posting questions in this thread, will post further queries in
Windows CE. A newbie mistake :0)

Thanks again.
Rama

Paul G. Tobey said:
I should also ask why the heck we're covering questions that have *nothing*
to do with the .NET Compact Framework in
microsoft.public.dotnet.framework.compactframework? Why not
microsoft.public.windowsce.platbuilder?

Paul T.

"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:[email protected]...
1. There are many ways to get things into the registry. If you don't know
what most of those are from experience, I can't really help in a
newsgroup. Check reginit.ini in the flat release folder after you've built
the OS and see if the entries you tried to add are there.

2. Read the help.

If it doesn't work as a downloaded nk.bin file, it won't work as a flashed
nk.bin file, either.

If you don't find a problem, other than reading the debug messages, I can
only suggest setting a breakpoint or two in the driver to see if it's
loaded at all (it might be loading and then return an error because your
settings for things like the interrupt number, base address, etc. are
wrong in your registry).

Paul T.
Click to expand...
Click to expand...
 
Back
Top