Sending images to a Palm Handheld

Friday, December 19th, 2003 at 7:00 pm | 1,374 views | trackback url
Tags: ,

Sending images to a Palm Handheld

    sisob, In your most-recent advogato diary entry, you mention you cannot transfer photos to your Palm from Linux, and that isn’t quite true.

    Not only do we have pilot-foto in the pilot-link suite of tools, but you can also use Par to transfer them directly to RAM or SD on your Palm (assuming you use the PPP method and the lftp client on the Palm, if you want to go to SD directly).

    Try using the pilot-link search engine to come up with some other ideas. People on the various pilot-link mailing lists are very responsive and helpful.

    Here’s exactly what you want, and more-specifically, the direct par instructions for transferring images to the Palm under Linux. Hopefully this helps you out a bit.


    Christmas will be spent in Buffalo again this year, after a 9-hour drive there. Hopefully we won’t get snowed in too much. I don’t mind the snow at all, but I don’t have bindings for my snowboard yet, so I can’t bring that with us (and no roof rack for the Audi yet this year).

    I still haven’t been paid for work I did 3 months ago for a client, which means Christmas is going to be lean this year, very lean. In fact, I’ve accrued more from Google banner ads in the last two months than I have in the last 6 months doing work for clients. Google hasn’t paid me either, so I can’t claim it yet. It should just about cover bandwidth costs this quarter, which will be nice, and the rest will probably go towards t-shirts and other miscellany for Plucker or to the FSF or EFF. Undetermined at this point.

Code Review

    In going over some old “historical” code in a project I maintain, it has come to my attention that there is a lot of room for improvement, without even considering the need to keep it current with the new features in the device advances in the last 6 months.

    I’ve been plodding through, line by line, cleaning up things in my spare time, but it’s arduous work, trying to make sure I don’t break existing functionality, or change it in a way that breaks the way the thousands of users use the code (scripted, automated, on Linux, on BSD, local, networked, over Bluetooth, etc.). Long, arduous work, and that doesn’t even count in the new API changes and protocol changes I have to reverse-engineer.

    I’ve been pouring through a lot of my old C books, and prodding people on #c on Freenode and Efnet for some general ideas about future implementation designs and design goals. Interesting times, to be sure.

Last Modified: Wednesday, April 6th, 2011 @ 13:30

Leave a Reply

You must be logged in to post a comment.

Bad Behavior has blocked 3669 access attempts in the last 7 days.