UZ
Ulf Zibis
Sun, Jan 21, 2024 12:40 PM
Am 21.01.24 um 13:27 schrieb Elmar Klausmeier:
You are right. I didn't know that American time counting is such illogical.
Thanks for the link.
Am 21.01.24 um 13:27 schrieb Elmar Klausmeier:
> I guess we are meaning the same: https://en.wikipedia.org/wiki/12-hour_clock
You are right. I didn't know that American time counting is such illogical.
Thanks for the link.
N
napakerr@hotmail.com
Mon, Jan 22, 2024 4:15 AM
Judd:
Thank you, that’s all I needed to know. A fix only on the Palm device is quite a daunting task itself. I thought if you had interest in doing work on the Desktop side, that might be the kick I need. Conceptually, fixing the Desktop sync is easy, but in reality it’s going to be more work than you’re up for.
Here’s perhaps a better summary:
1. When the Palm identifies as an updated device (with the date fix), JPilot needs to translated years and seconds differently. Because of the Palm identifying itself as updated, this would not effect legacy operation.
2. JPilot would need to be recompiled for Windows. I know that’s kind of a bombshell to leave here, but in this case, it’s just reality. It’s what people use and the handholding required to get everyone on Linux or an emulator is more than I’m willing to bear. I’d like to be able to just hand it over to Palm Dr and be done with it. Because it’s GTK, it should be pretty straightforward: maybe a prototype could be done in a day or two. However, its dependencies (such as pilot-link, libpisock, etc) could pose a much greater challenge. Sometime in the near future, WSL may be a viable option.
Elmar:
Yes, Palm’s epoch is 1904 and it uses an unsigned dword (UInt32) to track seconds, so the overflow point is 2036. However, the real problem is the 7-bit year which is hard coded in every application and in a really bad way. 7 bits means Palm has a 128 year span. That’s why we have up through 2031. The year needs to be wrapped, and then in 2036, the seconds too. Seconds can’t be wrapped at the same time as the year because it will break ssl. The epoch can’t be changed because it’s hard coded in applications and it would break compatibility between devices which aren’t updated. I’ve considered every angle on this issue, and there’s just not an easy fix that’s globally acceptable for everyone, but I do have a plan of attack.
Out of curiosity, what was the last Palm device you were using with JPilot?
**Judd:**\
Thank you, that’s all I needed to know. A fix only on the Palm device is quite a daunting task itself. I thought if you had interest in doing work on the Desktop side, that might be the kick I need. Conceptually, fixing the Desktop sync is easy, but in reality it’s going to be more work than you’re up for.\
\
Here’s perhaps a better summary:\
1\. When the Palm identifies as an updated device (with the date fix), JPilot needs to translated years and seconds differently. Because of the Palm identifying itself as updated, this would not effect legacy operation.\
2\. JPilot would need to be recompiled for Windows. I know that’s kind of a bombshell to leave here, but in this case, it’s just reality. It’s what people use and the handholding required to get everyone on Linux or an emulator is more than I’m willing to bear. I’d like to be able to just hand it over to Palm Dr and be done with it. Because it’s GTK, it should be pretty straightforward: maybe a prototype could be done in a day or two. However, its dependencies (such as pilot-link, libpisock, etc) could pose a much greater challenge. Sometime in the near future, WSL may be a viable option.\
\
**Elmar:**\
Yes, Palm’s epoch is 1904 and it uses an unsigned dword (UInt32) to track seconds, so the overflow point is 2036. However, the real problem is the 7-bit year which is hard coded in every application and in a really bad way. 7 bits means Palm has a 128 year span. That’s why we have up through 2031. The year needs to be wrapped, and then in 2036, the seconds too. Seconds can’t be wrapped at the same time as the year because it will break ssl. The epoch can’t be changed because it’s hard coded in applications and it would break compatibility between devices which aren’t updated. I’ve considered every angle on this issue, and there’s just not an easy fix that’s globally acceptable for everyone, but I do have a plan of attack.\
\
Out of curiosity, what was the last Palm device you were using with JPilot?
EK
Elmar Klausmeier
Mon, Jan 22, 2024 11:21 AM
I had a Palm III, Palm V, and lastly a Palm Tungsten (even a WiFi card).
They all broke down at some point -- none of them is usable anymore.
Therefore, I do not sync any longer, but probably wouldn't anyway, as my
main handheld is now Android. Today's Android smartphones are more powerful
than my PC back in those days! Octacore processors, GB of RAM, etc.
On Android I import my J-Pilot data every once in a while, mostly
addresses. Furthermore, I use termux in which I fire up a web-server, which
then serves a PHP interface to the SQLite data.
See https://eklausmeier.goip.de/aux/categories#J-Pilot.
If I understand correctly you want to fiddle with the internal Palm format
by using a "new" version of it, which handles dates slightly differently.
That is the main task of pilot-link. J-Pilot is "just" a nice interface to
pilot-link. You can sync on the command line with pilot-link, needing no
J-Pilot, no GTK. In particular, this should be already in total reach of
WSL. If you master pilot-link sync with your new format, J-Pilot can follow
suit quite "easily".
What I do not understand, how you tell the Palm device to handle all this
stuff differently, i.e., how you want the Palm internal applications to
cope with the new format.
On Mon, Jan 22, 2024 at 5:15 AM napakerr@hotmail.com wrote:
Judd:
Thank you, that’s all I needed to know. A fix only on the Palm device is
quite a daunting task itself. I thought if you had interest in doing work
on the Desktop side, that might be the kick I need. Conceptually, fixing
the Desktop sync is easy, but in reality it’s going to be more work than
you’re up for.
Here’s perhaps a better summary:
1. When the Palm identifies as an updated device (with the date fix),
JPilot needs to translated years and seconds differently. Because of the
Palm identifying itself as updated, this would not effect legacy operation.
2. JPilot would need to be recompiled for Windows. I know that’s kind of
a bombshell to leave here, but in this case, it’s just reality. It’s what
people use and the handholding required to get everyone on Linux or an
emulator is more than I’m willing to bear. I’d like to be able to just
hand it over to Palm Dr and be done with it. Because it’s GTK, it should
be pretty straightforward: maybe a prototype could be done in a day or
two. However, its dependencies (such as pilot-link, libpisock, etc) could
pose a much greater challenge. Sometime in the near future, WSL may be a
viable option.
Elmar:
Yes, Palm’s epoch is 1904 and it uses an unsigned dword (UInt32) to track
seconds, so the overflow point is 2036. However, the real problem is the
7-bit year which is hard coded in every application and in a really bad
way. 7 bits means Palm has a 128 year span. That’s why we have up through
2031. The year needs to be wrapped, and then in 2036, the seconds too.
Seconds can’t be wrapped at the same time as the year because it will break
ssl. The epoch can’t be changed because it’s hard coded in applications
and it would break compatibility between devices which aren’t updated.
I’ve considered every angle on this issue, and there’s just not an easy fix
that’s globally acceptable for everyone, but I do have a plan of attack.
Out of curiosity, what was the last Palm device you were using with JPilot?
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
I had a Palm III, Palm V, and lastly a Palm Tungsten (even a WiFi card).
They all broke down at some point -- none of them is usable anymore.
Therefore, I do not sync any longer, but probably wouldn't anyway, as my
main handheld is now Android. Today's Android smartphones are more powerful
than my PC back in those days! Octacore processors, GB of RAM, etc.
On Android I import my J-Pilot data every once in a while, mostly
addresses. Furthermore, I use termux in which I fire up a web-server, which
then serves a PHP interface to the SQLite data.
See https://eklausmeier.goip.de/aux/categories#J-Pilot.
If I understand correctly you want to fiddle with the internal Palm format
by using a "new" version of it, which handles dates slightly differently.
That is the main task of pilot-link. J-Pilot is "just" a nice interface to
pilot-link. You can sync on the command line with pilot-link, needing no
J-Pilot, no GTK. In particular, this should be already in total reach of
WSL. If you master pilot-link sync with your new format, J-Pilot can follow
suit quite "easily".
What I do not understand, how you tell the Palm device to handle all this
stuff differently, i.e., how you want the Palm internal applications to
cope with the new format.
On Mon, Jan 22, 2024 at 5:15 AM <napakerr@hotmail.com> wrote:
> **Judd:**\
> Thank you, that’s all I needed to know. A fix only on the Palm device is
> quite a daunting task itself. I thought if you had interest in doing work
> on the Desktop side, that might be the kick I need. Conceptually, fixing
> the Desktop sync is easy, but in reality it’s going to be more work than
> you’re up for.\
> \
> Here’s perhaps a better summary:\
> 1\. When the Palm identifies as an updated device (with the date fix),
> JPilot needs to translated years and seconds differently. Because of the
> Palm identifying itself as updated, this would not effect legacy operation.\
> 2\. JPilot would need to be recompiled for Windows. I know that’s kind of
> a bombshell to leave here, but in this case, it’s just reality. It’s what
> people use and the handholding required to get everyone on Linux or an
> emulator is more than I’m willing to bear. I’d like to be able to just
> hand it over to Palm Dr and be done with it. Because it’s GTK, it should
> be pretty straightforward: maybe a prototype could be done in a day or
> two. However, its dependencies (such as pilot-link, libpisock, etc) could
> pose a much greater challenge. Sometime in the near future, WSL may be a
> viable option.\
> \
> **Elmar:**\
> Yes, Palm’s epoch is 1904 and it uses an unsigned dword (UInt32) to track
> seconds, so the overflow point is 2036. However, the real problem is the
> 7-bit year which is hard coded in every application and in a really bad
> way. 7 bits means Palm has a 128 year span. That’s why we have up through
> 2031. The year needs to be wrapped, and then in 2036, the seconds too.
> Seconds can’t be wrapped at the same time as the year because it will break
> ssl. The epoch can’t be changed because it’s hard coded in applications
> and it would break compatibility between devices which aren’t updated.
> I’ve considered every angle on this issue, and there’s just not an easy fix
> that’s globally acceptable for everyone, but I do have a plan of attack.\
> \
> Out of curiosity, what was the last Palm device you were using with JPilot?
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>
B
Bob
Mon, Jan 22, 2024 3:40 PM
my last palm (that used to link in an earlier version of Linux) is the
same as the one I am still using, a TX
Bob
On Mon, 22 Jan 2024, napakerr@hotmail.com wrote:
Judd:
Thank you, that’s all I needed to know. A fix only on the Palm device is quite a daunting task itself. I thought if you had interest in doing work on the Desktop side, that might be the kick I need. Conceptually, fixing the Desktop sync is easy, but in reality it’s going to be more work than you’re up for.
Here’s perhaps a better summary:
1. When the Palm identifies as an updated device (with the date fix), JPilot needs to translated years and seconds differently. Because of the Palm identifying itself as updated, this would not effect legacy operation.
2. JPilot would need to be recompiled for Windows. I know that’s kind of a bombshell to leave here, but in this case, it’s just reality. It’s what people use and the handholding required to get everyone on Linux or an emulator is more than I’m willing to bear. I’d like to be able to just hand it over to Palm Dr and be done with it. Because it’s GTK, it should be pretty straightforward: maybe a prototype could be done in a day or two. However, its dependencies (such as pilot-link, libpisock, etc) could pose a much greater challenge. Sometime in the near future, WSL may be a viable option.
Elmar:
Yes, Palm’s epoch is 1904 and it uses an unsigned dword (UInt32) to track seconds, so the overflow point is 2036. However, the real problem is the 7-bit year which is hard coded in every application and in a really bad way. 7 bits means Palm has a 128 year span. That’s why we have up through 2031. The year needs to be wrapped, and then in 2036, the seconds too. Seconds can’t be wrapped at the same time as the year because it will break ssl. The epoch can’t be changed because it’s hard coded in applications and it would break compatibility between devices which aren’t updated. I’ve considered every angle on this issue, and there’s just not an easy fix that’s globally acceptable for everyone, but I do have a plan of attack.
Out of curiosity, what was the last Palm device you were using with JPilot?
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
my last palm (that used to link in an earlier version of Linux) is the
same as the one I am still using, a TX
Bob
On Mon, 22 Jan 2024, napakerr@hotmail.com wrote:
> **Judd:**\
> Thank you, that’s all I needed to know. A fix only on the Palm device is quite a daunting task itself. I thought if you had interest in doing work on the Desktop side, that might be the kick I need. Conceptually, fixing the Desktop sync is easy, but in reality it’s going to be more work than you’re up for.\
> \
> Here’s perhaps a better summary:\
> 1\. When the Palm identifies as an updated device (with the date fix), JPilot needs to translated years and seconds differently. Because of the Palm identifying itself as updated, this would not effect legacy operation.\
> 2\. JPilot would need to be recompiled for Windows. I know that’s kind of a bombshell to leave here, but in this case, it’s just reality. It’s what people use and the handholding required to get everyone on Linux or an emulator is more than I’m willing to bear. I’d like to be able to just hand it over to Palm Dr and be done with it. Because it’s GTK, it should be pretty straightforward: maybe a prototype could be done in a day or two. However, its dependencies (such as pilot-link, libpisock, etc) could pose a much greater challenge. Sometime in the near future, WSL may be a viable option.\
> \
> **Elmar:**\
> Yes, Palm’s epoch is 1904 and it uses an unsigned dword (UInt32) to track seconds, so the overflow point is 2036. However, the real problem is the 7-bit year which is hard coded in every application and in a really bad way. 7 bits means Palm has a 128 year span. That’s why we have up through 2031. The year needs to be wrapped, and then in 2036, the seconds too. Seconds can’t be wrapped at the same time as the year because it will break ssl. The epoch can’t be changed because it’s hard coded in applications and it would break compatibility between devices which aren’t updated. I’ve considered every angle on this issue, and there’s just not an easy fix that’s globally acceptable for everyone, but I do have a plan of attack.\
> \
> Out of curiosity, what was the last Palm device you were using with JPilot?
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>
>
N
napakerr@hotmail.com
Mon, Jan 22, 2024 6:55 PM
The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).
So you were never able to get it to sync with JPilot?
Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).\
So you were never able to get it to sync with JPilot?\
Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
JS
Jonas Sell
Mon, Jan 22, 2024 7:24 PM
I'm syncing over WiFi.
This is what I did:
In JPilot: File -> Preferences -> Settings -> Sync Port: other and net:any
On the host open port 14238/tcp in the firewall.
On the TX select in the HotSync application "Network" and add your PC by
IP. Done.
That worked for me.
Jonas
On 22/01/2024 19:55, napakerr@hotmail.com wrote:
The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).
So you were never able to get it to sync with JPilot?
Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
I'm syncing over WiFi.
This is what I did:
In JPilot: File -> Preferences -> Settings -> Sync Port: other and net:any
On the host open port 14238/tcp in the firewall.
On the TX select in the HotSync application "Network" and add your PC by
IP. Done.
That worked for me.
Jonas
On 22/01/2024 19:55, napakerr@hotmail.com wrote:
> The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).\
> So you were never able to get it to sync with JPilot?\
> Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
B
Bob
Mon, Jan 22, 2024 7:55 PM
I had a T3 before my TX so I agree with you
I run exclusively open source usually Linux, and it would link in earlier
versions but there was a trick to push the link button before the computer
linked. (or was it vice versa I could never seem to remember so sometimes
had to try more than once)but I think that stopped working in kubuntu
20.04 update. but it did link for years although it was sometimes cranky
doing so and have no reason why. one time it would work perfectly and the
next took 3-4 tries to get it to connect. but it always did eventually.
but hasn't in recent years. no matter what I did, still try when ever I
get an update.
Bob
On Mon, 22 Jan 2024, napakerr@hotmail.com wrote:
The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).
So you were never able to get it to sync with JPilot?
Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
I had a T3 before my TX so I agree with you
I run exclusively open source usually Linux, and it would link in earlier
versions but there was a trick to push the link button before the computer
linked. (or was it vice versa I could never seem to remember so sometimes
had to try more than once)but I think that stopped working in kubuntu
20.04 update. but it did link for years although it was sometimes cranky
doing so and have no reason why. one time it would work perfectly and the
next took 3-4 tries to get it to connect. but it always did eventually.
but hasn't in recent years. no matter what I did, still try when ever I
get an update.
Bob
On Mon, 22 Jan 2024, napakerr@hotmail.com wrote:
> The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).\
> So you were never able to get it to sync with JPilot?\
> Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>
>
B
Bob
Mon, Jan 22, 2024 7:58 PM
hmmm I am going to try that.
what OS are you using?
Bob
On Mon, 22 Jan 2024, Jonas Sell wrote:
I'm syncing over WiFi.
This is what I did:
In JPilot: File -> Preferences -> Settings -> Sync Port: other and net:any
On the host open port 14238/tcp in the firewall.
On the TX select in the HotSync application "Network" and add your PC by IP.
Done.
That worked for me.
Jonas
On 22/01/2024 19:55, napakerr@hotmail.com wrote:
The TX is a great device. That and the T3 were the two best Palm devices
ever made (as far as performance and functionality).
So you were never able to get it to sync with JPilot?
Is there anyone who was successful syncing a TX to JPilot over WiFi? Are
there switches that need to be added to pilot-link or can it be configured
in the GUI?
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
hmmm I am going to try that.
what OS are you using?
Bob
On Mon, 22 Jan 2024, Jonas Sell wrote:
> I'm syncing over WiFi.
> This is what I did:
> In JPilot: File -> Preferences -> Settings -> Sync Port: other and net:any
> On the host open port 14238/tcp in the firewall.
> On the TX select in the HotSync application "Network" and add your PC by IP.
> Done.
>
> That worked for me.
>
> Jonas
>
> On 22/01/2024 19:55, napakerr@hotmail.com wrote:
>> The TX is a great device. That and the T3 were the two best Palm devices
>> ever made (as far as performance and functionality).\
>> So you were never able to get it to sync with JPilot?\
>> Is there anyone who was successful syncing a TX to JPilot over WiFi? Are
>> there switches that need to be added to pilot-link or can it be configured
>> in the GUI?
>> _______________________________________________
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>
>
JS
Jonas Sell
Mon, Jan 22, 2024 8:08 PM
hmmm I am going to try that.
what OS are you using?
Bob
On Mon, 22 Jan 2024, Jonas Sell wrote:
I'm syncing over WiFi.
This is what I did:
In JPilot: File -> Preferences -> Settings -> Sync Port: other and net:any
On the host open port 14238/tcp in the firewall.
On the TX select in the HotSync application "Network" and add your PC by IP. Done.
That worked for me.
Jonas
On 22/01/2024 19:55, napakerr@hotmail.com wrote:
The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).
So you were never able to get it to sync with JPilot?
Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
I'm on Fedora 39.
Jonas
On 22 January 2024 19:58:46 UTC, Bob <accessys@smart.net> wrote:
>
>hmmm I am going to try that.
>
>what OS are you using?
>
>Bob
>
>
>On Mon, 22 Jan 2024, Jonas Sell wrote:
>
>> I'm syncing over WiFi.
>> This is what I did:
>> In JPilot: File -> Preferences -> Settings -> Sync Port: other and net:any
>> On the host open port 14238/tcp in the firewall.
>> On the TX select in the HotSync application "Network" and add your PC by IP. Done.
>>
>> That worked for me.
>>
>> Jonas
>>
>> On 22/01/2024 19:55, napakerr@hotmail.com wrote:
>>> The TX is a great device. That and the T3 were the two best Palm devices ever made (as far as performance and functionality).\
>>> So you were never able to get it to sync with JPilot?\
>>> Is there anyone who was successful syncing a TX to JPilot over WiFi? Are there switches that need to be added to pilot-link or can it be configured in the GUI?
>>> _______________________________________________
>>> Jpilot mailing list -- jpilot@lists.jpilot.org
>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>> _______________________________________________
>> Jpilot mailing list -- jpilot@lists.jpilot.org
>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
>>
>>
>_______________________________________________
>Jpilot mailing list -- jpilot@lists.jpilot.org
>To unsubscribe send an email to jpilot-leave@lists.jpilot.org
N
napakerr@hotmail.com
Mon, Jan 22, 2024 10:11 PM
It’s good to know it works on Fedora, that’s what I’ve always used, other than Centos (and now Rocky).
But I was trying to get it working on Ubuntu 22.04, but apparently pilot-link isn’t working: nothing’s listening on port 14238. If I try running pilot-link from console, it’s not found. I looked at the package and it looks like it doesn’t even contain the binary. I may need to try an older distro.
Did you have to compile pilot-link from source to get it working on Fedora 39?
It’s good to know it works on Fedora, that’s what I’ve always used, other than Centos (and now Rocky).
But I was trying to get it working on Ubuntu 22.04, but apparently pilot-link isn’t working: nothing’s listening on port 14238. If I try running pilot-link from console, it’s not found. I looked at the package and it looks like it doesn’t even contain the binary. I may need to try an older distro.\
\
Did you have to compile pilot-link from source to get it working on Fedora 39?
