<?xml version="1.0" encoding="iso-8859-1"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>macosxhints.com PDA tips</title>
<link>http://www.macosxhints.com/index.php?topic=hwpda</link>
<description>Tips and tricks related to using PDAs with OS X.</description>
<managingEditor>webteam@macosxhints.com</managingEditor>
<webMaster>webteam@macosxhints.com</webMaster>
<copyright>Copyright 2010 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Mon, 08 Mar 2010 06:39:24 -0800</pubDate>
<language>en-gb</language>
<atom:link href="http://www.macosxhints.com/backend/hintshwpda.rss" rel="self" type="application/rss+xml" />
<item>
<title>10.4: Recover Drive Mode functionality on Palm devices</title>
<link>http://www.macosxhints.com/article.php?story=20070627142919633</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20070627142919633</guid>
<pubDate>Thu, 28 Jun 2007 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20070627142919633#comments</comments>
<dc:subject>PDAs etc.</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/tigerx2a.jpg&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;The 10.4.9 update broke &quot;drive mode&quot; functionality for Palm T5 and LifeDrive models, and Palm seems unwilling to do anything about it. Symptoms of the problem include the Palm device hanging (soft reset required) and even Mac USB ports becoming unavailable until a restart is done.
&lt;br&gt;&lt;br&gt;
Today I discovered &lt;a href=&quot;http://www.softick.com/mobile/cardexport2/&quot;&gt;CardExport II&lt;/a&gt;, which is supposed to provide drive-mode-like capabilities to Palm OS devices with expansion card slots. I installed a trial version to see if it would work, and now I can see either of the devices I could once see with Drive Mode (albeit one at a time). Better than nothing, though it's &amp;#36;14.95 I shouldn't have to spend if Palm was doing its job -- and it seems to indicate that the problem is on Palm's side, not on Apple's.</description>
</item>
<item>
<title>10.4: Fix for Adobe Reader for Palm not launching</title>
<link>http://www.macosxhints.com/article.php?story=20070202183126553</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20070202183126553</guid>
<pubDate>Mon, 05 Feb 2007 07:30:04 -0800</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20070202183126553#comments</comments>
<dc:subject>PDAs etc.</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/tigerx2a.jpg&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;I recently downloaded the &lt;a href=&quot;http://ardownload.adobe.com/pub/adobe/reader/mac/palmos/3.x/AdobeReader305-PalmOS.dmg&quot;&gt;Adobe Reader for Palm OS (for Mac)&lt;/a&gt; to my MacBook running 10.4.8.
&lt;br&gt;&lt;br&gt;
As soon as I launched the app, it closed again, and the console.log (/Applications &amp;raquo; Utilities &amp;raquo; Console.app) gave this error (line breaks added):

&lt;blockquote&gt;2007-02-02 21:10:18.327 Finder[375] CFLog (0): &lt;br /&gt;
	CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8.&lt;br /&gt;
	The file name for this data could be:&lt;br /&gt;
	Contents/Info.plist -- file://localhost/Applications/Adobe%20Reader%20for%20Palm%20OS.app/&lt;br /&gt;
	The parser will retry as in 10.2, but the problem should be corrected in the plist.&lt;/blockquote&gt;

I opened the Applications folder in Finder, then selected the &lt;em&gt;Adobe Reader for Palm OS&lt;/em&gt; app, control-clicked and chose Show Package...</description>
</item>
<item>
<title>Scripts to convert files to/from Palm's PDB format</title>
<link>http://www.macosxhints.com/article.php?story=20060624121633885</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20060624121633885</guid>
<pubDate>Tue, 27 Jun 2006 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20060624121633885#comments</comments>
<dc:subject>PDAs etc.</dc:subject>
<description>I often like to read and edit documents, articles, and papers on my Palm device (using the excellent QED), and then continue back at home on the Mac. This requires quick and easy inter-conversion from &lt;tt&gt;.txt&lt;/tt&gt; to &lt;tt&gt;.pdb&lt;/tt&gt;. In addition, for reading PDFs as text, the conversion must respect the column flow in multi-column PDF fliles (or else you end up reading across, rather than down, the columns in your text file).
&lt;br&gt;&lt;br&gt;
This is how to create AppleScript droplets to convert text, PDF, and Word documents to &lt;tt&gt;.pdb&lt;/tt&gt; and then back to text.
&lt;ol&gt;
&lt;li&gt;Read and follow &lt;a href=&quot;http://www.macosxhints.com/article.php?story=20030220222718501&quot;&gt;this excellent hint&lt;/a&gt; for converting text to pdb for Palm OS. Make sure during this you pay attention to:
&lt;ul&gt;
&lt;li&gt;Installing xCode tools first (to compile unix make/install files)&lt;/li&gt;
&lt;li&gt;The tips about using sudo to avoid &quot;permission denied&quot; errors&lt;/li&gt;
&lt;/ul&gt;
In fact, to use these droplets, you don't need to get the AppleScript on...</description>
</item>
<item>
<title>A workaround for a Palm Bluetooth HotSync error</title>
<link>http://www.macosxhints.com/article.php?story=20060528140401608</link>
<guid isPermaLink="true">http://www.macosxhints.com/article.php?story=20060528140401608</guid>
<pubDate>Thu, 01 Jun 2006 07:30:00 -0700</pubDate>
<comments>http://www.macosxhints.com/article.php?story=20060528140401608#comments</comments>
<dc:subject>PDAs etc.</dc:subject>
<description>I have a Palm Treo 650 that I HotSync with my Powerbook over Bluetooth (using MissingSync). When I initiate a HotSync from the Treo, however, I get the following error message:
&lt;br&gt;&lt;br&gt;
  &lt;em&gt;Unable to initiate HotSync operation because the port is in use by another application.&lt;/em&gt;
&lt;br&gt;&lt;br&gt;
One solution seems to be a system restart, but the problem re-appears after the first Bluetooth HotSync. The only other solution I've found is to open the Bluetooth System Preferences Pane, and toggle between the Settings and Devices tabs while the Bluetooth connection is attempting to connect. (I came across this solution in a forum somewhere). This second solution is a little annoying to do manually, so I wrote the following AppleScript to automate the process. It is adapted from the script in &lt;a href=&quot;http://www.macosxhints.com/article.php?story=20060516085755886&quot;&gt;this hint&lt;/a&gt;.

&lt;pre&gt;&lt;code&gt;tell application &quot;System Preferences&quot;
  activate
end tell
tell application &quot;System Events&quot;
  tell proc...</description>
</item>
</channel>
</rss>
