Hi Jorge, I agree.  The Palm is much easier to use and if they had a modern one I would use one. What is Palm Day?  Is that the 32-bit date year 2038 problem? You can also do things like "install" the databases on the other Palm if you wanted to use it for the day.  Pilot-xfer is also a nice tool for doing things that you should only do if you know what you are doing. ;-) Judd On 3/6/23 21:02, Jorge Quintanilla wrote: > Dear Judd, > > First of all thank you very much let me tell you how grateful I am to > you for jpilot. I used my Palm m100 literally all the time for several > years during 1999-2004. For various reasons, I stopped using it for a > long time. Recently I went back and I was shocked by how much more > natural and useful it is for me than gmail/outlook calendars on a mobile > phone. But without jpilot it would have been simply too impractical to > go back to Palm. > > Secondly thank you very much for your patient explanations (and Rich too!) > > Once I started using my Palm everyday again, I became naturally > concerned about Palm Day. I decided to run some really simple user-level > experiments. I needed a device I was not using for anything crucial so I > got my second Palm. I then realised the III-xe is in some ways nicer > (bigger screen so easier to read) so I thought I'd give it a go. Ideally > I would have liked to be able to switch back and forth between them but > your very clear explanation has made me give up on that. I think, from > what you wrote, it might work if you never change a record on both > palms, only create new ones/delete old ones, but I couldn't gurantee > that is what I would do. In any case, for my use case being able to go > from using one (and only that one) to using the other is enough, and the > procedure I described works for that. I will use the III-xe for a while, > and if I decide to go back to the m100 I now know how to restore it. And > in either case I will have a backup device in case the other one breaks, > with the database kept safe on .jpilot. Brilliant! > > Thank you for clarifying the intended purpose of JPILOT_HOME, I > understand now that its intended use is not much to do with my specific > "problem". > > We now need a solution for Palm Day... (Which, I note, does not affect > jpilot. It may well be that cloning the Palm devices is easier now than > fixing them...) > > Thanks again, > > And all the best, > > Jorge > > > On 07/03/2023 00:55, Judd Montgomery wrote: >> On 3/6/23 13:36, Jorge Quintanilla wrote: >> >>> Hello, >>> >>> I think it is brilliant that this list is being maintained, thank you >>> very much! I have one question, maybe someone here can help me. It >>> relates to using two Palm devices under Linux (with jpilot). >>> >>> I have recently "resurrected" my old Palm m100 out of frustration with >>> modern calendar tools. I have been amazed at how clean and efficient the >>> whole experience is. But I am probably preaching to the converted >>> here... In any case, since I use Linux in my daily work I am using >>> JPilot for backup and desktop-based work. I also tried Palm Desktop >>> 3.1.1 under Windos XP inside a VirtualBox but I have not managed to make >>> that work. In any case, I am finding JPilot very useful. Besides, I like >>> the fact that JPilot is open source and I can easily modify its >>> directories, etc. >>> >>> My question is this: I have acquired a second Palm device (a Palm IIIxe) >>> and I would like to also synchronise it with JPilot. Moreover I would >>> like both devices to be in sync with each other (at least their DateBook >>> databases). In other words, I would like a single DateBook database on >>> jpilot, my Palm m100, and my Palm IIIxe. The idea is that every time I >>> do a HotSync between jpilot and oe of the two palms the database on >>> jpilot gets synced with that Palm device. So I have a "star-shaped" syn >>> structure with jpilot in the middle and the two handheld devices as the >>> spokes: >>> >>> [m100] <--> [jpilot] <--> [IIIxe] >>> >>> Is that at all possible? How would one go about it? >>> >>> The instructions on >>> https://github.com/juddmon/jpilot#readme >>> about synchronising two palms are somewhat laconic, it seems to me they >>> are about synchronising two palms with two separate jpilot databases. In >>> any case I have tried to follow the instructions and they don't seem to >>> work for me. More detailed instructions would be highly appreciated, >>> thank you. >>> >>> Sorry for the long email, and thanks in advance for your time. >>> >>> Best wishes, >>> >>> jorge >> Hi Jorge, >> >> It is always nice to see new or returning users. >> >> You are not the first person to request this feature. I even wanted it back when I had multiple Palm OS devices. >> >> The sync protocol on PalmOS was not very robust. If you modify a record on the Palm it gets marked "dirty". If you modify it on the desktop it gets marked "dirty". On the next sync the dirty records get sent to the other side and the dirty flag is removed. Each record has a unique ID. If a record is dirty on both sides there is a conflict and it requires the user to select which one to keep. For instance, there is no elegant logic to determine that the Last name was changed on the desktop and the first name on the Palm, therefore the newest first name and newest last name should be merged during a sync. >> >> There is not much other metadata about the records and I do not think it is possible to know how to merge the records from multiple devices. I don't know if Palm did this because it was simple code from a start-up company, or if its due to a requirement to sync at 9600 baud or having a slow processor. It doesn't really matter. >> >> If you understand how the sync process works you may be able to make some hack work for you. Do you plan on changing info on both Palms and in jpilot, or just jpilot and one Palm? Or something else? Answer this and I will see if something would work. >> >> The JPILOT_HOME env var will just tell jpilot to look in another place for the .jpilot directory. That way you can have many jpilots or Palm devices to sync. Just not with each other. >> >> IIRC, it was somewhere around Palm OS 4.3 that they changed to the newer DBs (Calendar, Contacts, Tasks, Memos). These may (probably) cause problems if you put a DB from an older Palm on it and vice-versa. There was also a Calendar problem between two different Palms with the same or very close to the same OS. If you install one of these you will get a boot loop and need to reset the Palm. I think the two you are using will work fine together. >> >> Judd >> _______________________________________________ >> 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, What is Palm Day? Is that the 32-bit date year 2038 problem? > Yes I think so but it's closer than you think: 31 December, 2031. I don't know the details, see https://palmdb.net/about/palm-day and some discussioms of this on the #dev-talk channel of the PalmDB Discord channel. You can also do things like "install" the databases on the other Palm if > you wanted to use it for the day. Pilot-xfer is also a nice tool for > doing things that you should only do if you know what you are doing. ;-) > Gulp... ;-)