Hello
i m looking for how bypass TouchScreen calibrate after a hardreset on a PDA.
i think about looking in the rom and reflash pda with modify rom (but i
think this impossible), or rebuilding a new winCE with platform builder. i
think that build a new driver only will not be efficient cause after an
hardreset my new driver will not be reload during the first start of the
PDA. but rebuild a winCE like HP or Asus done will be not easy i think....
Thanks


Benoît Raynaud

Re: TouchScreen Calibrate by Peter

Peter
Sat Apr 02 04:58:29 CST 2005

If you place an empty file called welcome.not in the root of a storage card
which is inserted on boot (on some devices you can place this file in the
stable storage folder but it varies from one manufacturer to another) this
will disable the welcome wizard. However your touchscreen may not function
if you do not apply the calibrary data in the registry. You can work around
this by taking existing readings from a device of the same model and writing
them to the registry, then soft reset the device after you have finished
installation. This can allow you to perform installation un-interuppted on
hard reset, however it's good practise to allow the user to calibrate the
device properly once it's up and running. Take a look at this article for
some pointers:-
http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=06b4072d-3585-43d4-8605-f7cebc6387f7

Peter

--
Peter Foot
Windows Embedded MVP
http://www.inthehand.com | http://blog.opennetcf.org/pfoot/

"Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
news:424e7115$0$25033$8fcfb975@news.wanadoo.fr...
> Hello
> i m looking for how bypass TouchScreen calibrate after a hardreset on a
> PDA.
> i think about looking in the rom and reflash pda with modify rom (but i
> think this impossible), or rebuilding a new winCE with platform builder. i
> think that build a new driver only will not be efficient cause after an
> hardreset my new driver will not be reload during the first start of the
> PDA. but rebuild a winCE like HP or Asus done will be not easy i think....
> Thanks
>
>
> Benoît Raynaud
>
>
>
>



Re: TouchScreen Calibrate by Benoît

Benoît
Sat Apr 02 05:22:16 CST 2005

your solution will work even after an hard reset of the PDA ?

"Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le message
de news:esikpL3NFHA.164@TK2MSFTNGP12.phx.gbl...
> If you place an empty file called welcome.not in the root of a storage
card
> which is inserted on boot (on some devices you can place this file in the
> stable storage folder but it varies from one manufacturer to another) this
> will disable the welcome wizard. However your touchscreen may not function
> if you do not apply the calibrary data in the registry. You can work
around
> this by taking existing readings from a device of the same model and
writing
> them to the registry, then soft reset the device after you have finished
> installation. This can allow you to perform installation un-interuppted on
> hard reset, however it's good practise to allow the user to calibrate the
> device properly once it's up and running. Take a look at this article for
> some pointers:-
>
http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=06b4072d-3585-43d4-8605-f7cebc6387f7
>
> Peter
>
> --
> Peter Foot
> Windows Embedded MVP
> http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
>
> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
> news:424e7115$0$25033$8fcfb975@news.wanadoo.fr...
> > Hello
> > i m looking for how bypass TouchScreen calibrate after a hardreset on a
> > PDA.
> > i think about looking in the rom and reflash pda with modify rom (but i
> > think this impossible), or rebuilding a new winCE with platform builder.
i
> > think that build a new driver only will not be efficient cause after an
> > hardreset my new driver will not be reload during the first start of the
> > PDA. but rebuild a winCE like HP or Asus done will be not easy i
think....
> > Thanks
> >
> >
> > Benoît Raynaud
> >
> >
> >
> >
>
>



Re: TouchScreen Calibrate by ctacke/>

ctacke/>
Sat Apr 02 05:28:07 CST 2005

So if you don't have calibration data, how is the device usable?

-Chris


"Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
news:424e7115$0$25033$8fcfb975@news.wanadoo.fr...
> Hello
> i m looking for how bypass TouchScreen calibrate after a hardreset on a
> PDA.
> i think about looking in the rom and reflash pda with modify rom (but i
> think this impossible), or rebuilding a new winCE with platform builder. i
> think that build a new driver only will not be efficient cause after an
> hardreset my new driver will not be reload during the first start of the
> PDA. but rebuild a winCE like HP or Asus done will be not easy i think....
> Thanks
>
>
> Benoît Raynaud
>
>
>
>



Re: TouchScreen Calibrate by Peter

Peter
Sat Apr 02 05:47:17 CST 2005

Provided you follow those steps - have the welcome.not file on a bootable
storage card, and make sure the first things you do in deployment are to
write the calibration data to the registry and any other info normally set
in the welcome wizard (timezone etc).
This is only a practical method if you are deploying to a batch of devices
all of the same model. As I stated below you should call TouchCalibrate at
some point in your application perhaps after your application is deployment
and it is first run to ensure the calibration data is accurate enough for
normal use.

Peter

--
Peter Foot
Windows Embedded MVP
http://www.inthehand.com | http://blog.opennetcf.org/pfoot/

"Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
news:424e7ffa$0$3121$8fcfb975@news.wanadoo.fr...
> your solution will work even after an hard reset of the PDA ?
>
> "Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le message
> de news:esikpL3NFHA.164@TK2MSFTNGP12.phx.gbl...
>> If you place an empty file called welcome.not in the root of a storage
> card
>> which is inserted on boot (on some devices you can place this file in the
>> stable storage folder but it varies from one manufacturer to another)
>> this
>> will disable the welcome wizard. However your touchscreen may not
>> function
>> if you do not apply the calibrary data in the registry. You can work
> around
>> this by taking existing readings from a device of the same model and
> writing
>> them to the registry, then soft reset the device after you have finished
>> installation. This can allow you to perform installation un-interuppted
>> on
>> hard reset, however it's good practise to allow the user to calibrate the
>> device properly once it's up and running. Take a look at this article for
>> some pointers:-
>>
> http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=06b4072d-3585-43d4-8605-f7cebc6387f7
>>
>> Peter
>>
>> --
>> Peter Foot
>> Windows Embedded MVP
>> http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
>>
>> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
>> news:424e7115$0$25033$8fcfb975@news.wanadoo.fr...
>> > Hello
>> > i m looking for how bypass TouchScreen calibrate after a hardreset on a
>> > PDA.
>> > i think about looking in the rom and reflash pda with modify rom (but i
>> > think this impossible), or rebuilding a new winCE with platform
>> > builder.
> i
>> > think that build a new driver only will not be efficient cause after an
>> > hardreset my new driver will not be reload during the first start of
>> > the
>> > PDA. but rebuild a winCE like HP or Asus done will be not easy i
> think....
>> > Thanks
>> >
>> >
>> > Benoît Raynaud
>> >
>> >
>> >
>> >
>>
>>
>
>



Re: TouchScreen Calibrate by Benoît

Benoît
Sat Apr 02 06:27:31 CST 2005

hello
so i ll try you solution but :
how make a bootable storage card ? is a simple SD with a welcome.not
empty file on it working (in pratice, i put the SD in the pocketpc, i create
an empty file named welcome.not on it) ? even after a hardreset it will
bypass the calibrate/copy&paste/time zone screen ?
How write into registry value after an hardreset ? need i to create
another SD card with autorun.exe on it and insert it after the SD containing
the empty file welcome.not ?
i m new in pda at you can see, sorry

Benoît Raynaud

"Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le message
de news:%23UK$6m3NFHA.164@TK2MSFTNGP12.phx.gbl...
> Provided you follow those steps - have the welcome.not file on a bootable
> storage card, and make sure the first things you do in deployment are to
> write the calibration data to the registry and any other info normally set
> in the welcome wizard (timezone etc).
> This is only a practical method if you are deploying to a batch of devices
> all of the same model. As I stated below you should call TouchCalibrate at
> some point in your application perhaps after your application is
deployment
> and it is first run to ensure the calibration data is accurate enough for
> normal use.
>
> Peter
>
> --
> Peter Foot
> Windows Embedded MVP
> http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
>
> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
> news:424e7ffa$0$3121$8fcfb975@news.wanadoo.fr...
> > your solution will work even after an hard reset of the PDA ?
> >
> > "Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le
message
> > de news:esikpL3NFHA.164@TK2MSFTNGP12.phx.gbl...
> >> If you place an empty file called welcome.not in the root of a storage
> > card
> >> which is inserted on boot (on some devices you can place this file in
the
> >> stable storage folder but it varies from one manufacturer to another)
> >> this
> >> will disable the welcome wizard. However your touchscreen may not
> >> function
> >> if you do not apply the calibrary data in the registry. You can work
> > around
> >> this by taking existing readings from a device of the same model and
> > writing
> >> them to the registry, then soft reset the device after you have
finished
> >> installation. This can allow you to perform installation un-interuppted
> >> on
> >> hard reset, however it's good practise to allow the user to calibrate
the
> >> device properly once it's up and running. Take a look at this article
for
> >> some pointers:-
> >>
> >
http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=06b4072d-3585-43d4-8605-f7cebc6387f7
> >>
> >> Peter
> >>
> >> --
> >> Peter Foot
> >> Windows Embedded MVP
> >> http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
> >>
> >> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
> >> news:424e7115$0$25033$8fcfb975@news.wanadoo.fr...
> >> > Hello
> >> > i m looking for how bypass TouchScreen calibrate after a hardreset on
a
> >> > PDA.
> >> > i think about looking in the rom and reflash pda with modify rom (but
i
> >> > think this impossible), or rebuilding a new winCE with platform
> >> > builder.
> > i
> >> > think that build a new driver only will not be efficient cause after
an
> >> > hardreset my new driver will not be reload during the first start of
> >> > the
> >> > PDA. but rebuild a winCE like HP or Asus done will be not easy i
> > think....
> >> > Thanks
> >> >
> >> >
> >> > Benoît Raynaud
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>



Re: TouchScreen Calibrate by Peter

Peter
Sat Apr 02 07:23:20 CST 2005

You need just one storage card which should contain your autorun exe in the
processor specific folder e.g. 2577 - you'll find details on how to do this
in a variety of places, one here:-
http://www.pocketpcdn.com/articles/autorun.html

Add your "welcome.not" file to the root folder on the SD card. Put the SD
card in the device when it hard resets, the welcome screen will appear then
be dismissed in a couple of seconds then your autorun.exe will be launched
and can install your app and required settings. Make sure your Autorun
writes the screen calibration data to the registry the first time it is
called. After your software is deployed I reocmmend calling TouchCalibrate
when your app first runs to fine tune the screen calibration.

Peter

--
Peter Foot
Windows Embedded MVP
http://www.inthehand.com | http://blog.opennetcf.org/pfoot/

"Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
news:424e8f3d$0$25021$8fcfb975@news.wanadoo.fr...
> hello
> so i ll try you solution but :
> how make a bootable storage card ? is a simple SD with a welcome.not
> empty file on it working (in pratice, i put the SD in the pocketpc, i
> create
> an empty file named welcome.not on it) ? even after a hardreset it will
> bypass the calibrate/copy&paste/time zone screen ?
> How write into registry value after an hardreset ? need i to create
> another SD card with autorun.exe on it and insert it after the SD
> containing
> the empty file welcome.not ?
> i m new in pda at you can see, sorry
>
> Benoît Raynaud
>
> "Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le message
> de news:%23UK$6m3NFHA.164@TK2MSFTNGP12.phx.gbl...
>> Provided you follow those steps - have the welcome.not file on a bootable
>> storage card, and make sure the first things you do in deployment are to
>> write the calibration data to the registry and any other info normally
>> set
>> in the welcome wizard (timezone etc).
>> This is only a practical method if you are deploying to a batch of
>> devices
>> all of the same model. As I stated below you should call TouchCalibrate
>> at
>> some point in your application perhaps after your application is
> deployment
>> and it is first run to ensure the calibration data is accurate enough for
>> normal use.
>>
>> Peter
>>
>> --
>> Peter Foot
>> Windows Embedded MVP
>> http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
>>
>> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
>> news:424e7ffa$0$3121$8fcfb975@news.wanadoo.fr...
>> > your solution will work even after an hard reset of the PDA ?
>> >
>> > "Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le
> message
>> > de news:esikpL3NFHA.164@TK2MSFTNGP12.phx.gbl...
>> >> If you place an empty file called welcome.not in the root of a storage
>> > card
>> >> which is inserted on boot (on some devices you can place this file in
> the
>> >> stable storage folder but it varies from one manufacturer to another)
>> >> this
>> >> will disable the welcome wizard. However your touchscreen may not
>> >> function
>> >> if you do not apply the calibrary data in the registry. You can work
>> > around
>> >> this by taking existing readings from a device of the same model and
>> > writing
>> >> them to the registry, then soft reset the device after you have
> finished
>> >> installation. This can allow you to perform installation
>> >> un-interuppted
>> >> on
>> >> hard reset, however it's good practise to allow the user to calibrate
> the
>> >> device properly once it's up and running. Take a look at this article
> for
>> >> some pointers:-
>> >>
>> >
> http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=06b4072d-3585-43d4-8605-f7cebc6387f7
>> >>
>> >> Peter
>> >>
>> >> --
>> >> Peter Foot
>> >> Windows Embedded MVP
>> >> http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
>> >>
>> >> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
>> >> news:424e7115$0$25033$8fcfb975@news.wanadoo.fr...
>> >> > Hello
>> >> > i m looking for how bypass TouchScreen calibrate after a hardreset
>> >> > on
> a
>> >> > PDA.
>> >> > i think about looking in the rom and reflash pda with modify rom
>> >> > (but
> i
>> >> > think this impossible), or rebuilding a new winCE with platform
>> >> > builder.
>> > i
>> >> > think that build a new driver only will not be efficient cause after
> an
>> >> > hardreset my new driver will not be reload during the first start of
>> >> > the
>> >> > PDA. but rebuild a winCE like HP or Asus done will be not easy i
>> > think....
>> >> > Thanks
>> >> >
>> >> >
>> >> > Benoît Raynaud
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>



Re: TouchScreen Calibrate by Beverly

Beverly
Sat Apr 02 09:32:56 CST 2005

You can extract the previous (or generic) screen info from the registry,
then use a routine to insert that key into the new registry as part of
the autorun process.

The "screen calibration" is not really the hard reset problem, rather
the insistant "tutorial"

If I were doing this, I would program to do the population, then end the
process by calling the screen calibration so that it's there for the
user when the device is powered back up.

Beverly Howard [MS MVP-Mobile Devices]

Re: TouchScreen Calibrate by ctacke/>

ctacke/>
Sat Apr 02 12:00:20 CST 2005

"Extracting" the value will likely be good only for a specific device.
Sure, they're all resistive touch panels, but there's a pretty good range of
variability in 4-wire panels, not to mention the circuitry attached to them.
They're also very temp dependent. I guess you've got the small size going
for you on a PPC, but I'd think that setting cal data instead of collecting
it is a very bad idea - especially since bad cal data means you can't get to
the control panel to recal.

Now eliminating the stupid start-up tutorial is a good thing - I'll fully go
along with that.

-Chris



"Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> wrote in
message news:OHoW$k5NFHA.3336@TK2MSFTNGP10.phx.gbl...
> You can extract the previous (or generic) screen info from the registry,
> then use a routine to insert that key into the new registry as part of the
> autorun process.
>
> The "screen calibration" is not really the hard reset problem, rather the
> insistant "tutorial"
>
> If I were doing this, I would program to do the population, then end the
> process by calling the screen calibration so that it's there for the user
> when the device is powered back up.
>
> Beverly Howard [MS MVP-Mobile Devices]



Re: TouchScreen Calibrate by Peter

Peter
Sat Apr 02 13:00:00 CST 2005

We use this technique to skip the tutorial and autorun the installation from
SD card, during this we set some averaged values based on the device model
for worst case scenario. Then once installation is complete we can call the
calibration process alone without all the dentist appointment jiggery-pokery
to set exact values - calling TouchCalibrate() gets right into the
calibration process so the user doesn't need to go through the control
panel. In this way it doesn't disrupt the installation process but we still
end up with a correctly configured device.

Peter

--
Peter Foot
Windows Embedded MVP
http://www.inthehand.com | http://blog.opennetcf.org/pfoot/

"<ctacke/>" <ctacke_AT_OpenNETCF_com> wrote in message
news:uvmOX36NFHA.3988@tk2msftngp13.phx.gbl...
> "Extracting" the value will likely be good only for a specific device.
> Sure, they're all resistive touch panels, but there's a pretty good range
> of variability in 4-wire panels, not to mention the circuitry attached to
> them. They're also very temp dependent. I guess you've got the small size
> going for you on a PPC, but I'd think that setting cal data instead of
> collecting it is a very bad idea - especially since bad cal data means you
> can't get to the control panel to recal.
>
> Now eliminating the stupid start-up tutorial is a good thing - I'll fully
> go along with that.
>
> -Chris
>
>
>
> "Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> wrote in
> message news:OHoW$k5NFHA.3336@TK2MSFTNGP10.phx.gbl...
>> You can extract the previous (or generic) screen info from the registry,
>> then use a routine to insert that key into the new registry as part of
>> the autorun process.
>>
>> The "screen calibration" is not really the hard reset problem, rather the
>> insistant "tutorial"
>>
>> If I were doing this, I would program to do the population, then end the
>> process by calling the screen calibration so that it's there for the user
>> when the device is powered back up.
>>
>> Beverly Howard [MS MVP-Mobile Devices]
>
>



Re: TouchScreen Calibrate by Steve

Steve
Sat Apr 02 13:23:14 CST 2005

Peter's approach strikes me as the most reasonable approach as touch panels
are sensitive to 4 factors.
1) Individual component variations - this is not necessarily a one time
adjustment (see #4 below)
2) Temperature as Chris pointed out.
3) Air pressure (not as big a factor but still a real one)
4) Time - Over time the calibration needs adjustment due to the wear and
tear and general decay of the components.

Forcing one and only one calibration for all installations of a device
causes troubles. Using a gross approximation at first with more precise
refinements afterwards is a reasonable choice.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: TouchScreen Calibrate by ctacke/>

ctacke/>
Sat Apr 02 15:13:31 CST 2005

Yep, agreed. I was just concerned about someone just not running the cal
screen or thinking that a static cal would work for all devices.

-Chris


"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> wrote in message
news:u2NXtl7NFHA.3704@TK2MSFTNGP12.phx.gbl...
> Peter's approach strikes me as the most reasonable approach as touch
> panels are sensitive to 4 factors.
> 1) Individual component variations - this is not necessarily a one time
> adjustment (see #4 below)
> 2) Temperature as Chris pointed out.
> 3) Air pressure (not as big a factor but still a real one)
> 4) Time - Over time the calibration needs adjustment due to the wear and
> tear and general decay of the components.
>
> Forcing one and only one calibration for all installations of a device
> causes troubles. Using a gross approximation at first with more precise
> refinements afterwards is a reasonable choice.
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>



Re: TouchScreen Calibrate by Beverly

Beverly
Sat Apr 02 16:59:29 CST 2005

I tried to make it clear that the calibration should be run by
suggesting that the install process run the screen calibration at the
end of the install.

In addition, the op's need pointed to updating rather than prepping new
devices, so it would be possible to have the utility extract the current
calibration key before the re-flash and store it on the memory card for
each device for re-use.

In my experience, the primary need for the calibration was not included
in Steve's message and is due to the fact that the display is located
below the touch membranes so that the human perception of the stylus
point is about a mm or more beyond the stylus tip. For a good demo of
this, start any "draw" input method, then draw circles and crosses first
with the calibrated hand, then with the other hand. As a result, a tech
upgrader cannot, in any case, calibrate for another user, especially
left handed ones.

Beverly Howard [MS MVP-Mobile Devices]

Re: TouchScreen Calibrate by Benoît

Benoît
Sun Apr 03 06:30:42 CDT 2005

Hello
ok, my problem becomes harder...cause the environment project is pressure
and temperature variable...so when i see your message, i beging to think
that screen calibration is needed...
to precise more my project i could tell you why always the PDA is starting
it begins from an hard reset : all battery of pda must be out...and pda is
working with power wire...the project is to build a touch screen remote
control but environement of project forbid battery, so little battery inside
PDA (like bios battery in PC) must be out...it is the reson why every time
PDA is powered on, it will make start from hard reset
but the final end customer will not to calibrate the screen each time he ll
power on PDA...arghhh
i ll try the empty file called welcome.not and SDRAM with autorun in good
path on monday to see if calibration/copy&paste/time zone message will be
bypass (the sdram will be in the PDA before power on cause i could tell the
customer thats before power on the pda he will have to insert SD in the
PDA...impossible) so i hope this will work
is the problem of temperature/pressure specific to resistive touch screen ?
maybe surfacic wave or infrared or other touch screen type haven t this
problem ?
thanks for your time ans your answer, u think about lots of thinks thaht i
missed to think about.


Benoît Raynaud

"Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> a écrit dans le
message de news:eylWhe9NFHA.3928@TK2MSFTNGP09.phx.gbl...
> I tried to make it clear that the calibration should be run by
> suggesting that the install process run the screen calibration at the
> end of the install.
>
> In addition, the op's need pointed to updating rather than prepping new
> devices, so it would be possible to have the utility extract the current
> calibration key before the re-flash and store it on the memory card for
> each device for re-use.
>
> In my experience, the primary need for the calibration was not included
> in Steve's message and is due to the fact that the display is located
> below the touch membranes so that the human perception of the stylus
> point is about a mm or more beyond the stylus tip. For a good demo of
> this, start any "draw" input method, then draw circles and crosses first
> with the calibrated hand, then with the other hand. As a result, a tech
> upgrader cannot, in any case, calibrate for another user, especially
> left handed ones.
>
> Beverly Howard [MS MVP-Mobile Devices]



Re: TouchScreen Calibrate by Beverly

Beverly
Sun Apr 03 11:02:52 CDT 2005

>> no battery <<

Sounds like a nasa shuttle project limit.

Additional thoughts;

Whats going to be on screen for input... large buttons or will the user
be using the keypad, etc?

If just a few buttons, calibration may not be an issue.

If each unit has it's own memory card, previous calibration info can be
reused.

In the senario you describe, it would seem the easiest to autorun a
backup restore on cold boot which would restore the registry including
the calibration data.

If fine input is required, imho, temperature, etc will not be a
significant issue if you restore a previous good calibration.

Beverly Howard [MS MVP-Mobile Devices]



Re: TouchScreen Calibrate by Benoît

Benoît
Sun Apr 03 14:17:49 CDT 2005

Hello
the project i m working on is not for nasa or space discovery...sky of earth
only
user will operate on the PDA with finger...adult human finger...and function
of keypad of the PDA will be redefined
tomorow i ll try autorun on SD card, i m hoping that will work (i m not sure
that the autorun will be launch if the SD is in the PDA before the power
switch on). but before all i wll try the empty file called "welcome.not" on
the SD card to bypass calibration/copy&paste/yime zone screens (i hope too
that it will work if the SD is in the PDA before power is switching on)
thanks


Benoît Raynaud

"Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> a écrit dans le
message de news:e1lSYaGOFHA.2384@tk2msftngp13.phx.gbl...
> >> no battery <<
>
> Sounds like a nasa shuttle project limit.
>
> Additional thoughts;
>
> Whats going to be on screen for input... large buttons or will the user
> be using the keypad, etc?
>
> If just a few buttons, calibration may not be an issue.
>
> If each unit has it's own memory card, previous calibration info can be
> reused.
>
> In the senario you describe, it would seem the easiest to autorun a
> backup restore on cold boot which would restore the registry including
> the calibration data.
>
> If fine input is required, imho, temperature, etc will not be a
> significant issue if you restore a previous good calibration.
>
> Beverly Howard [MS MVP-Mobile Devices]
>
>



Re: TouchScreen Calibrate by Peter

Peter
Sun Apr 03 15:42:05 CDT 2005

What you should see happen is that the system will boot, and within a few
seconds the SD card will initialise, so you'll see the welcome to pocket pc
screen for a few seconds then it will be dismissed. In this way you can
leave the SD card in the unit.

Peter

--
Peter Foot
Windows Embedded MVP
http://www.inthehand.com | http://blog.opennetcf.org/pfoot/

"Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
news:425040e7$0$19336$8fcfb975@news.wanadoo.fr...
> Hello
> the project i m working on is not for nasa or space discovery...sky of
> earth
> only
> user will operate on the PDA with finger...adult human finger...and
> function
> of keypad of the PDA will be redefined
> tomorow i ll try autorun on SD card, i m hoping that will work (i m not
> sure
> that the autorun will be launch if the SD is in the PDA before the power
> switch on). but before all i wll try the empty file called "welcome.not"
> on
> the SD card to bypass calibration/copy&paste/yime zone screens (i hope too
> that it will work if the SD is in the PDA before power is switching on)
> thanks
>
>
> Benoît Raynaud
>
> "Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> a écrit dans
> le
> message de news:e1lSYaGOFHA.2384@tk2msftngp13.phx.gbl...
>> >> no battery <<
>>
>> Sounds like a nasa shuttle project limit.
>>
>> Additional thoughts;
>>
>> Whats going to be on screen for input... large buttons or will the user
>> be using the keypad, etc?
>>
>> If just a few buttons, calibration may not be an issue.
>>
>> If each unit has it's own memory card, previous calibration info can be
>> reused.
>>
>> In the senario you describe, it would seem the easiest to autorun a
>> backup restore on cold boot which would restore the registry including
>> the calibration data.
>>
>> If fine input is required, imho, temperature, etc will not be a
>> significant issue if you restore a previous good calibration.
>>
>> Beverly Howard [MS MVP-Mobile Devices]
>>
>>
>
>



Re: TouchScreen Calibrate by Alex

Alex
Sun Apr 03 16:00:01 CDT 2005

Can't you use Peter's approach and persist the calibration data on the card
between boots?

--
Alex Feinman
---
Visit http://www.opennetcf.org
"Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
news:425040e7$0$19336$8fcfb975@news.wanadoo.fr...
> Hello
> the project i m working on is not for nasa or space discovery...sky of
> earth
> only
> user will operate on the PDA with finger...adult human finger...and
> function
> of keypad of the PDA will be redefined
> tomorow i ll try autorun on SD card, i m hoping that will work (i m not
> sure
> that the autorun will be launch if the SD is in the PDA before the power
> switch on). but before all i wll try the empty file called "welcome.not"
> on
> the SD card to bypass calibration/copy&paste/yime zone screens (i hope too
> that it will work if the SD is in the PDA before power is switching on)
> thanks
>
>
> Benoît Raynaud
>
> "Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> a écrit dans
> le
> message de news:e1lSYaGOFHA.2384@tk2msftngp13.phx.gbl...
>> >> no battery <<
>>
>> Sounds like a nasa shuttle project limit.
>>
>> Additional thoughts;
>>
>> Whats going to be on screen for input... large buttons or will the user
>> be using the keypad, etc?
>>
>> If just a few buttons, calibration may not be an issue.
>>
>> If each unit has it's own memory card, previous calibration info can be
>> reused.
>>
>> In the senario you describe, it would seem the easiest to autorun a
>> backup restore on cold boot which would restore the registry including
>> the calibration data.
>>
>> If fine input is required, imho, temperature, etc will not be a
>> significant issue if you restore a previous good calibration.
>>
>> Beverly Howard [MS MVP-Mobile Devices]
>>
>>
>
>


Re: TouchScreen Calibrate by ctacke/>

ctacke/>
Sun Apr 03 21:02:42 CDT 2005

Sure, with an autorun it would work, but at some point cal data must be
collected.

-Chris



"Alex Feinman [MVP]" <public_news@alexfeinman.com> wrote in message
news:eJIgN$IOFHA.3928@TK2MSFTNGP09.phx.gbl...
> Can't you use Peter's approach and persist the calibration data on the
> card between boots?
>
> --
> Alex Feinman
> ---
> Visit http://www.opennetcf.org
> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
> news:425040e7$0$19336$8fcfb975@news.wanadoo.fr...
>> Hello
>> the project i m working on is not for nasa or space discovery...sky of
>> earth
>> only
>> user will operate on the PDA with finger...adult human finger...and
>> function
>> of keypad of the PDA will be redefined
>> tomorow i ll try autorun on SD card, i m hoping that will work (i m not
>> sure
>> that the autorun will be launch if the SD is in the PDA before the power
>> switch on). but before all i wll try the empty file called "welcome.not"
>> on
>> the SD card to bypass calibration/copy&paste/yime zone screens (i hope
>> too
>> that it will work if the SD is in the PDA before power is switching on)
>> thanks
>>
>>
>> Benoît Raynaud
>>
>> "Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> a écrit dans
>> le
>> message de news:e1lSYaGOFHA.2384@tk2msftngp13.phx.gbl...
>>> >> no battery <<
>>>
>>> Sounds like a nasa shuttle project limit.
>>>
>>> Additional thoughts;
>>>
>>> Whats going to be on screen for input... large buttons or will the user
>>> be using the keypad, etc?
>>>
>>> If just a few buttons, calibration may not be an issue.
>>>
>>> If each unit has it's own memory card, previous calibration info can be
>>> reused.
>>>
>>> In the senario you describe, it would seem the easiest to autorun a
>>> backup restore on cold boot which would restore the registry including
>>> the calibration data.
>>>
>>> If fine input is required, imho, temperature, etc will not be a
>>> significant issue if you restore a previous good calibration.
>>>
>>> Beverly Howard [MS MVP-Mobile Devices]
>>>
>>>
>>
>>
>



Re: TouchScreen Calibrate by Benoît

Benoît
Mon Apr 04 06:04:52 CDT 2005

hello
ok for autorun.exe : that s work on ipaq 4150 and Asus 730
But "welcome.not" empty file works only on ipaq PDA...On Asus730 it doesnt
work and stay on the pressscreen to calibrate; etc....
maybe it s windows version that s done the difference : ipaq4150 (2002) &
Asus730 (2003)...on both PDAs with SD containing empty "welcome.not" file a
colored circle appears during boot, but on ipaq bypass
calibration/copy&paste/timezone
if you have idea
Thanks


Benoît Raynaud

"Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le message
de news:%23FMxa2IOFHA.2704@TK2MSFTNGP15.phx.gbl...
> What you should see happen is that the system will boot, and within a few
> seconds the SD card will initialise, so you'll see the welcome to pocket
pc
> screen for a few seconds then it will be dismissed. In this way you can
> leave the SD card in the unit.
>
> Peter
>
> --
> Peter Foot
> Windows Embedded MVP
> http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
>
> "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
> news:425040e7$0$19336$8fcfb975@news.wanadoo.fr...
> > Hello
> > the project i m working on is not for nasa or space discovery...sky of
> > earth
> > only
> > user will operate on the PDA with finger...adult human finger...and
> > function
> > of keypad of the PDA will be redefined
> > tomorow i ll try autorun on SD card, i m hoping that will work (i m not
> > sure
> > that the autorun will be launch if the SD is in the PDA before the power
> > switch on). but before all i wll try the empty file called "welcome.not"
> > on
> > the SD card to bypass calibration/copy&paste/yime zone screens (i hope
too
> > that it will work if the SD is in the PDA before power is switching on)
> > thanks
> >
> >
> > Benoît Raynaud
> >
> > "Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com> a écrit
dans
> > le
> > message de news:e1lSYaGOFHA.2384@tk2msftngp13.phx.gbl...
> >> >> no battery <<
> >>
> >> Sounds like a nasa shuttle project limit.
> >>
> >> Additional thoughts;
> >>
> >> Whats going to be on screen for input... large buttons or will the user
> >> be using the keypad, etc?
> >>
> >> If just a few buttons, calibration may not be an issue.
> >>
> >> If each unit has it's own memory card, previous calibration info can be
> >> reused.
> >>
> >> In the senario you describe, it would seem the easiest to autorun a
> >> backup restore on cold boot which would restore the registry including
> >> the calibration data.
> >>
> >> If fine input is required, imho, temperature, etc will not be a
> >> significant issue if you restore a previous good calibration.
> >>
> >> Beverly Howard [MS MVP-Mobile Devices]
> >>
> >>
> >
> >
>
>



Re: TouchScreen Calibrate by Benoît

Benoît
Mon Apr 04 12:18:33 CDT 2005

Hello
i ve used the registry editor of eVC++ to get registry value of the
screencalibation in :
hkey_local_machine\hardware\devicemap\touch
and i put this value in another PDA, same Model (ipaq 4150), but this one
are booting with SD card containing an empty file "welcome.not" to bypass
screencalibration/copy&paste/time zone screens...but the calibration set in
the registry has no effect with this PDA :(...maybe i missed to do
something...
2nd trouble : i tried to generate an "Hello World" application with
eVC++...with wizard of course...and i send the .exe created by activesync in
my PDA (ipaq4150..PXA255)...i choose "ARM4I release" in the project of
eVC++...but in the PDA when i try to launch the .ee it says "not a win32
application" or something like that...i don t understand why so i tried all
type of processor type but nothing better...
help please
thanks



Benoît Raynaud
PDA is Problem Da i hAve

"Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> a écrit dans le message de
news:424e7ffa$0$3121$8fcfb975@news.wanadoo.fr...
> your solution will work even after an hard reset of the PDA ?
>
> "Peter Foot [MVP]" <feedback@nospam-inthehand.com> a écrit dans le message
> de news:esikpL3NFHA.164@TK2MSFTNGP12.phx.gbl...
> > If you place an empty file called welcome.not in the root of a storage
> card
> > which is inserted on boot (on some devices you can place this file in
the
> > stable storage folder but it varies from one manufacturer to another)
this
> > will disable the welcome wizard. However your touchscreen may not
function
> > if you do not apply the calibrary data in the registry. You can work
> around
> > this by taking existing readings from a device of the same model and
> writing
> > them to the registry, then soft reset the device after you have finished
> > installation. This can allow you to perform installation un-interuppted
on
> > hard reset, however it's good practise to allow the user to calibrate
the
> > device properly once it's up and running. Take a look at this article
for
> > some pointers:-
> >
>
http://blog.opennetcf.org/pfoot/PermaLink.aspx?guid=06b4072d-3585-43d4-8605-f7cebc6387f7
> >
> > Peter
> >
> > --
> > Peter Foot
> > Windows Embedded MVP
> > http://www.inthehand.com | http://blog.opennetcf.org/pfoot/
> >
> > "Benoît Raynaud" <benoit.raynaud3@wanadoo.fr> wrote in message
> > news:424e7115$0$25033$8fcfb975@news.wanadoo.fr...
> > > Hello
> > > i m looking for how bypass TouchScreen calibrate after a hardreset on
a
> > > PDA.
> > > i think about looking in the rom and reflash pda with modify rom (but
i
> > > think this impossible), or rebuilding a new winCE with platform
builder.
> i
> > > think that build a new driver only will not be efficient cause after
an
> > > hardreset my new driver will not be reload during the first start of
the
> > > PDA. but rebuild a winCE like HP or Asus done will be not easy i
> think....
> > > Thanks
> > >
> > >
> > > Benoît Raynaud
> > >
> > >
> > >
> > >
> >
> >
>
>