Bug 63623 (suse48623)

<!-- SBZ_reproduce  -->
Backup Palm  
Restore Palm 
Attempt to use digitiser 
 
(Not apparent with my Visor)

This is a 3Com Palm V running Palm OS v. 3.3. 

Discussing a fix with the kpilot maintainer  

Which didn't come to anything.  

Daniel, if you find anything out can you add it here?

I also have the Palm V and have often the problem that i have to hard rest the palm to recalibrate it. But i am no quite sure if it is a pilot-link problem. There are many disscusion on the internet about calibration problems of palms ... and there also exists many applications for the palm to run the digitizer also after a soft reset or to bind it on a non-digitizer button. For example Z-digitzer:
http://www.palmgear.com/index.cfm?fuseaction=software.showsoftware&prodID=9161

Also i found hints in discussion to check if there is enough space between the screen and the case.

For me it seems to be a general palm problem (at least for older models).

Daniel, I think that you didn't get the problem here:

If the Palm lost calibration by itself then this is a Palm problem.

But in this case the calibration is fine but after restoring data with the link utility the calibration gets destroyed by the software which is definitely something the software should not do.

I had a short discussion with a pilot-link developer which never had a problem like this. 

The data you restored are from the same palm - or from another palm?
Happens this only when you restore your data? Or also while HotSync or somehting else?
Can you reproduce this realible?

The data are from the same palm.

Happens only on restore.

I could reproduce this at the time I wrote this bug report. Currently I do no longer use the palm but if there is interest I could check again.

Please try to reproduce this.

Let's try this: Hard-reset your Palm (back it up first, of course, using 'pilot-xfer -p /dev/ttySx -b /tmp/foobar' or some such, do not use -s to back it up, use -b. Make *SURE* kpilotDaemon is not running at this point. 

Press all 4 buttons on the Palm's front panel to initialize the application databases with default values. 

Calibrate the digitizer (Prefs -> Digitizer) AFTER doing the hard-reset and AFTER initializing your default application databases.

Back up the data at this point from the hard-reset Palm to another directory, /tmp/clean or some such, using pilot-xfer again. 

Hard-reset your Palm again, cd into /tmp/clean, and use restore using pilot-xfer's -r option ('pilot-xfer -p /dev/ttySx -r /tmp/clean'). 

Is the digitizer off at this point? Or does it work? 

My machines with 10.1 do not have serial ports thus I did rebuild the 10.1 package of pilot-link for 9.2 and tried there.

My Palm does not reinitialize the application databases when pressing all 4 buttons thus I did the following:

1. Backup everything as described above.

2. Hard-reset the Palm and calibrate.

3. Backup empty Palm as described above.

4. Hard-reset the Palm and calibrate.

5. Restore empty backup as described above. ==> No calibration problems.

6. Restore full backup. ==> No calibration problems.

Interesting part is that I don't see the message box described in the initial comment when restoring with the command line tool.

Another strange thing is that not all dates got restored after restoring from the full backup. Either my Palm or pilot-link is somehow horribly broken.

Due to the fact that I no longer use my Palm device I personally do no longer care very much about the data loss but if you want me to try something else I could do so.

Can you try the same testcase with kpilot instead of pilot-xfer - please.
To be sure that the also doesn't exist in kpilot.