T
tonydunn@protonmail.com
Wed, Sep 10, 2025 3:51 PM
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
CC
chantey_child_7c@icloud.com
Wed, Sep 10, 2025 4:38 PM
Tony,
I would recommend using two separate IDs and either use beaming to transfer the necessary data, or export the data from the original ID, and then import it into a new ID for the M100. This is the best way to do it since syncing two devices of different generations can cause incompatibilities between them at some point when syncing apps.
Take care,
Andrew Poulain (9HS380)
On Sep 10, 2025, at 13:21, Tony Dunn via Jpilot jpilot@lists.jpilot.org wrote:
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Tony,
I would recommend using two separate IDs and either use beaming to transfer the necessary data, or export the data from the original ID, and then import it into a new ID for the M100. This is the best way to do it since syncing two devices of different generations can cause incompatibilities between them at some point when syncing apps.
Take care,
Andrew Poulain (9HS380)
> On Sep 10, 2025, at 13:21, Tony Dunn via Jpilot <jpilot@lists.jpilot.org> wrote:
>
> Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
>
> Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
>
> Using jpilot 2.0.2 and pilot-link 0.12.5
>
> Many thanks
>
> Tony
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
JM
Judd Montgomery
Wed, Sep 10, 2025 5:17 PM
Hi,
Can you tell me what your desired outcome is? How you would want them
to sync, etc? Would you want them to always be the same?
Judd
On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Hi,
Can you tell me what your desired outcome is? How you would want them
to sync, etc? Would you want them to always be the same?
Judd
On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
> Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
>
> Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
>
> Using jpilot 2.0.2 and pilot-link 0.12.5
>
> Many thanks
>
> Tony
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
TD
Tony Dunn
Wed, Sep 10, 2025 6:05 PM
Andrew
Thanks for your thoughts. Certainly one of the potential issues I had not initially considered was different generations having incompatibilities sufficient to foul up sync between them.
One of the biggest drivers for looking before leaping was to avoid any data conflicts, so will take the sage counsel of the list on board!
Regards
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 17:50, chantey_child_7c--- via Jpilot jpilot@lists.jpilot.org wrote:
Tony,
I would recommend using two separate IDs and either use beaming to transfer the necessary data, or export the data from the original ID, and then import it into a new ID for the M100. This is the best way to do it since syncing two devices of different generations can cause incompatibilities between them at some point when syncing apps.
Take care,
Andrew Poulain (9HS380)
On Sep 10, 2025, at 13:21, Tony Dunn via Jpilot jpilot@lists.jpilot.org wrote:
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
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
Andrew
Thanks for your thoughts. Certainly one of the potential issues I had not initially considered was different generations having incompatibilities sufficient to foul up sync between them.
One of the biggest drivers for looking before leaping was to avoid any data conflicts, so will take the sage counsel of the list on board!
Regards
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 17:50, chantey_child_7c--- via Jpilot <jpilot@lists.jpilot.org> wrote:
> Tony,
>
> I would recommend using two separate IDs and either use beaming to transfer the necessary data, or export the data from the original ID, and then import it into a new ID for the M100. This is the best way to do it since syncing two devices of different generations can cause incompatibilities between them at some point when syncing apps.
>
> Take care,
> Andrew Poulain (9HS380)
>
> > On Sep 10, 2025, at 13:21, Tony Dunn via Jpilot jpilot@lists.jpilot.org wrote:
> >
> > Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
> >
> > Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
> >
> > Using jpilot 2.0.2 and pilot-link 0.12.5
> >
> > Many thanks
> >
> > Tony
> > _______________________________________________
> > 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
TD
Tony Dunn
Wed, Sep 10, 2025 6:13 PM
Hi Judd
Yes, my initial notion/outcome was/would be that both devices would be perfectly sync'd, but I wonder if being away from the Palm world for more than twenty years and being very familiar with the way the sync'd world works now (so my Mac is transparently sync'd to my iPhone/iPad etc) might be a flawed premise when applied to the Palm/jpilot, in that the platform and jpilot itself was maybe not ever built with that use case in mind?
As for how I envisaged this working, I would be content to do it manually through the GUI of jpilot to begin with, but if it could be scripted, so much the better going forward.
I'd welcome your thoughts of course.
Thanks
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 18:18, Judd Montgomery judd@jpilot.org wrote:
Hi,
Can you tell me what your desired outcome is? How you would want them
to sync, etc? Would you want them to always be the same?
Judd
On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
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
Hi Judd
Yes, my initial notion/outcome was/would be that both devices would be perfectly sync'd, but I wonder if being away from the Palm world for more than twenty years and being very familiar with the way the sync'd world works now (so my Mac is transparently sync'd to my iPhone/iPad etc) might be a flawed premise when applied to the Palm/jpilot, in that the platform and jpilot itself was maybe not ever built with that use case in mind?
As for how I envisaged this working, I would be content to do it manually through the GUI of jpilot to begin with, but if it could be scripted, so much the better going forward.
I'd welcome your thoughts of course.
Thanks
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 18:18, Judd Montgomery <judd@jpilot.org> wrote:
> Hi,
>
> Can you tell me what your desired outcome is? How you would want them
> to sync, etc? Would you want them to always be the same?
>
> Judd
>
> On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
>
> > Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
> >
> > Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
> >
> > Using jpilot 2.0.2 and pilot-link 0.12.5
> >
> > Many thanks
> >
> > Tony
> > _______________________________________________
> > 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
JM
Judd Montgomery
Wed, Sep 10, 2025 9:02 PM
You are right on the syncing not being designed like modern systems.
They may have had robust syncing in mind as a wish, but they had a
Motorola DragonBall that although was low power, was still thirsty by
today's standards. They also had to work over a serial port and most
people had 9600 baud working solidly. The sync process seems to be
designed to be low power (not a lot of processing, which was battery
friendly) and low i/o. Memory was probably a concern as well.
With USB the i/o speed isn't a big concern so you can install these
little database files fairly quickly.
If you want to go down this path what I might do is have a "master" Palm
and sync it and install its databases on the other one. The other one
would not have changes other than this done to it. That might not be
useful for your use case. Yes, there could be issues with pdb files.
The only one I know of is the ContactsDB-PAdd.pdb or (its been so long
I'm not sure anymore) the CalenderDB-PAdd.pdb. When one of those is
installed on a non-compatible Palm the Palm will keep rebooting until
you hard reset it. If you install it and it seems to work I think
you'll be fine.
This is all hacky stuff and you have to take the risks of data loss.
Always back up and keep versions.
Another way is that if you knew the pdb files were exactly the same and
you didn't make changes on the Palms then you could copy .pc3 files from
one jpilot to the other. The *.pc3 files contain changes in jpilot that
are to be synced. They depend on record IDs being the same on both
Palms and this is risky, but I did play around with it myself.
A third way is since Elmar added SQLite storage capability then you
could add a plugin that would possibly extend the database fields and do
some syncing there, although I think you'd always need to ask the user
how to resolve field conflicts since there is no timestamp on records or
fields in the Palm device. Messy.
Judd
On 9/10/25 14:13, Tony Dunn via Jpilot wrote:
Hi Judd
Yes, my initial notion/outcome was/would be that both devices would be perfectly sync'd, but I wonder if being away from the Palm world for more than twenty years and being very familiar with the way the sync'd world works now (so my Mac is transparently sync'd to my iPhone/iPad etc) might be a flawed premise when applied to the Palm/jpilot, in that the platform and jpilot itself was maybe not ever built with that use case in mind?
As for how I envisaged this working, I would be content to do it manually through the GUI of jpilot to begin with, but if it could be scripted, so much the better going forward.
I'd welcome your thoughts of course.
Thanks
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 18:18, Judd Montgomery judd@jpilot.org wrote:
Hi,
Can you tell me what your desired outcome is? How you would want them
to sync, etc? Would you want them to always be the same?
Judd
On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
You are right on the syncing not being designed like modern systems.
They may have had robust syncing in mind as a wish, but they had a
Motorola DragonBall that although was low power, was still thirsty by
today's standards. They also had to work over a serial port and most
people had 9600 baud working solidly. The sync process seems to be
designed to be low power (not a lot of processing, which was battery
friendly) and low i/o. Memory was probably a concern as well.
With USB the i/o speed isn't a big concern so you can install these
little database files fairly quickly.
If you want to go down this path what I might do is have a "master" Palm
and sync it and install its databases on the other one. The other one
would not have changes other than this done to it. That might not be
useful for your use case. Yes, there could be issues with pdb files.
The only one I know of is the ContactsDB-PAdd.pdb or (its been so long
I'm not sure anymore) the CalenderDB-PAdd.pdb. When one of those is
installed on a non-compatible Palm the Palm will keep rebooting until
you hard reset it. If you install it and it seems to work I think
you'll be fine.
This is all hacky stuff and you have to take the risks of data loss.
Always back up and keep versions.
Another way is that if you knew the pdb files were exactly the same and
you didn't make changes on the Palms then you could copy .pc3 files from
one jpilot to the other. The *.pc3 files contain changes in jpilot that
are to be synced. They depend on record IDs being the same on both
Palms and this is risky, but I did play around with it myself.
A third way is since Elmar added SQLite storage capability then you
could add a plugin that would possibly extend the database fields and do
some syncing there, although I think you'd always need to ask the user
how to resolve field conflicts since there is no timestamp on records or
fields in the Palm device. Messy.
Judd
On 9/10/25 14:13, Tony Dunn via Jpilot wrote:
> Hi Judd
>
> Yes, my initial notion/outcome was/would be that both devices would be perfectly sync'd, but I wonder if being away from the Palm world for more than twenty years and being very familiar with the way the sync'd world works now (so my Mac is transparently sync'd to my iPhone/iPad etc) might be a flawed premise when applied to the Palm/jpilot, in that the platform and jpilot itself was maybe not ever built with that use case in mind?
>
> As for how I envisaged this working, I would be content to do it manually through the GUI of jpilot to begin with, but if it could be scripted, so much the better going forward.
>
> I'd welcome your thoughts of course.
>
> Thanks
>
> Tony
>
> Sent with Proton Mail secure email.
>
> On Wednesday, September 10th, 2025 at 18:18, Judd Montgomery <judd@jpilot.org> wrote:
>
>> Hi,
>>
>> Can you tell me what your desired outcome is? How you would want them
>> to sync, etc? Would you want them to always be the same?
>>
>> Judd
>>
>> On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
>>
>>> Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
>>>
>>> Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
>>>
>>> Using jpilot 2.0.2 and pilot-link 0.12.5
>>>
>>> Many thanks
>>>
>>> Tony
>>> _______________________________________________
>>> 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
TD
Tony Dunn
Thu, Sep 11, 2025 9:39 AM
Judd
Many thanks for your expansive thoughts on this one - plenty for me to think about and experiment with. That said...
...I do wonder the more I think about this whether or not I am trying to force a square peg into a round hole? The degree of hackery (in potential) to get to where I thought I'd ideally like to be seems disproportionate to any benefit that might accrue, and even allowing for me being very relaxed about data loss on the 'slave' machine (the m100), I can feel me digging myself a monstrous time sink hole whereby I spend more time fire -fighting and less time being productive.
For now, thanks for sage counsel from all, appreciated.
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 22:03, Judd Montgomery judd@jpilot.org wrote:
You are right on the syncing not being designed like modern systems.
They may have had robust syncing in mind as a wish, but they had a
Motorola DragonBall that although was low power, was still thirsty by
today's standards. They also had to work over a serial port and most
people had 9600 baud working solidly. The sync process seems to be
designed to be low power (not a lot of processing, which was battery
friendly) and low i/o. Memory was probably a concern as well.
With USB the i/o speed isn't a big concern so you can install these
little database files fairly quickly.
If you want to go down this path what I might do is have a "master" Palm
and sync it and install its databases on the other one. The other one
would not have changes other than this done to it. That might not be
useful for your use case. Yes, there could be issues with pdb files.
The only one I know of is the ContactsDB-PAdd.pdb or (its been so long
I'm not sure anymore) the CalenderDB-PAdd.pdb. When one of those is
installed on a non-compatible Palm the Palm will keep rebooting until
you hard reset it. If you install it and it seems to work I think
you'll be fine.
This is all hacky stuff and you have to take the risks of data loss.
Always back up and keep versions.
Another way is that if you knew the pdb files were exactly the same and
you didn't make changes on the Palms then you could copy .pc3 files from
one jpilot to the other. The *.pc3 files contain changes in jpilot that
are to be synced. They depend on record IDs being the same on both
Palms and this is risky, but I did play around with it myself.
A third way is since Elmar added SQLite storage capability then you
could add a plugin that would possibly extend the database fields and do
some syncing there, although I think you'd always need to ask the user
how to resolve field conflicts since there is no timestamp on records or
fields in the Palm device. Messy.
Judd
On 9/10/25 14:13, Tony Dunn via Jpilot wrote:
Hi Judd
Yes, my initial notion/outcome was/would be that both devices would be perfectly sync'd, but I wonder if being away from the Palm world for more than twenty years and being very familiar with the way the sync'd world works now (so my Mac is transparently sync'd to my iPhone/iPad etc) might be a flawed premise when applied to the Palm/jpilot, in that the platform and jpilot itself was maybe not ever built with that use case in mind?
As for how I envisaged this working, I would be content to do it manually through the GUI of jpilot to begin with, but if it could be scripted, so much the better going forward.
I'd welcome your thoughts of course.
Thanks
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 18:18, Judd Montgomery judd@jpilot.org wrote:
Hi,
Can you tell me what your desired outcome is? How you would want them
to sync, etc? Would you want them to always be the same?
Judd
On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
Using jpilot 2.0.2 and pilot-link 0.12.5
Many thanks
Tony
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
Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org
Judd
Many thanks for your expansive thoughts on this one - plenty for me to think about and experiment with. That said...
...I do wonder the more I think about this whether or not I am trying to force a square peg into a round hole? The degree of hackery (in potential) to get to where I thought I'd ideally like to be seems disproportionate to any benefit that might accrue, and even allowing for me being very relaxed about data loss on the 'slave' machine (the m100), I can feel me digging myself a monstrous time sink hole whereby I spend more time fire -fighting and less time being productive.
For now, thanks for sage counsel from all, appreciated.
Tony
Sent with Proton Mail secure email.
On Wednesday, September 10th, 2025 at 22:03, Judd Montgomery <judd@jpilot.org> wrote:
> You are right on the syncing not being designed like modern systems.
> They may have had robust syncing in mind as a wish, but they had a
> Motorola DragonBall that although was low power, was still thirsty by
> today's standards. They also had to work over a serial port and most
> people had 9600 baud working solidly. The sync process seems to be
> designed to be low power (not a lot of processing, which was battery
> friendly) and low i/o. Memory was probably a concern as well.
>
> With USB the i/o speed isn't a big concern so you can install these
> little database files fairly quickly.
>
> If you want to go down this path what I might do is have a "master" Palm
> and sync it and install its databases on the other one. The other one
> would not have changes other than this done to it. That might not be
> useful for your use case. Yes, there could be issues with pdb files.
> The only one I know of is the ContactsDB-PAdd.pdb or (its been so long
> I'm not sure anymore) the CalenderDB-PAdd.pdb. When one of those is
> installed on a non-compatible Palm the Palm will keep rebooting until
> you hard reset it. If you install it and it seems to work I think
> you'll be fine.
>
> This is all hacky stuff and you have to take the risks of data loss.
> Always back up and keep versions.
>
> Another way is that if you knew the pdb files were exactly the same and
> you didn't make changes on the Palms then you could copy .pc3 files from
> one jpilot to the other. The *.pc3 files contain changes in jpilot that
> are to be synced. They depend on record IDs being the same on both
> Palms and this is risky, but I did play around with it myself.
>
> A third way is since Elmar added SQLite storage capability then you
> could add a plugin that would possibly extend the database fields and do
> some syncing there, although I think you'd always need to ask the user
> how to resolve field conflicts since there is no timestamp on records or
> fields in the Palm device. Messy.
>
> Judd
>
> On 9/10/25 14:13, Tony Dunn via Jpilot wrote:
>
> > Hi Judd
> >
> > Yes, my initial notion/outcome was/would be that both devices would be perfectly sync'd, but I wonder if being away from the Palm world for more than twenty years and being very familiar with the way the sync'd world works now (so my Mac is transparently sync'd to my iPhone/iPad etc) might be a flawed premise when applied to the Palm/jpilot, in that the platform and jpilot itself was maybe not ever built with that use case in mind?
> >
> > As for how I envisaged this working, I would be content to do it manually through the GUI of jpilot to begin with, but if it could be scripted, so much the better going forward.
> >
> > I'd welcome your thoughts of course.
> >
> > Thanks
> >
> > Tony
> >
> > Sent with Proton Mail secure email.
> >
> > On Wednesday, September 10th, 2025 at 18:18, Judd Montgomery judd@jpilot.org wrote:
> >
> > > Hi,
> > >
> > > Can you tell me what your desired outcome is? How you would want them
> > > to sync, etc? Would you want them to always be the same?
> > >
> > > Judd
> > >
> > > On 9/10/25 11:51, Tony Dunn via Jpilot wrote:
> > >
> > > > Just got a second Palm, an M100 to go with my IIIex. I want to sync the identical information on both devices via jpilot. I have an existing username and ID on the IIIex.
> > > >
> > > > Before I set sail into uncharted territory, can I seek confirmation/clarification on what is the likely outcome of syncing the second Palm, the m100, using a different username and ID?
> > > >
> > > > Using jpilot 2.0.2 and pilot-link 0.12.5
> > > >
> > > > Many thanks
> > > >
> > > > Tony
> > > > _______________________________________________
> > > > 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
>
> _______________________________________________
> Jpilot mailing list -- jpilot@lists.jpilot.org
> To unsubscribe send an email to jpilot-leave@lists.jpilot.org
