TDE personal information management applications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

faq.docbook 10KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386
  1. <chapter id="faq">
  2. <title>&FAQ;</title>
  3. <sect1 id="faq-crash">
  4. <title>&kpilot; Startup Problems</title>
  5. <qandaset>
  6. <qandaentry>
  7. <question>
  8. <para>
  9. What do I put after <option>--debug</option>?
  10. </para>
  11. </question>
  12. <answer>
  13. <para>
  14. Nothing. Most versions of &kpilot; don't even have
  15. a <option>--debug</option> option, and will complain if you use it.
  16. For those versions that <emphasis>do</emphasis> have it,
  17. use a value between 1 and 4, which will control the
  18. amount of debugging printed (a little).
  19. Using a value of 1 will print a fairly complete call trace
  20. without the really-boring functions, while 4 will include every trivial
  21. function in all of &kpilot;.
  22. </para>
  23. </answer>
  24. </qandaentry>
  25. <qandaentry id="faq-connection">
  26. <question>
  27. <para>
  28. &kpilot; says <errorname>Can't connect to pilot</errorname>
  29. </para>
  30. </question>
  31. <answer>
  32. <para>
  33. This can have various causes. Check that:
  34. <itemizedlist>
  35. <listitem>
  36. <para>
  37. The pilot device (usually <filename
  38. class="devicefile">/dev/pilot</filename>) exists and points to the
  39. serial port the &PalmPilot; is actually connected to.
  40. </para>
  41. <para>
  42. To link the &PalmPilot; device to the correct serial port, you can
  43. either fill in
  44. <filename
  45. class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename>
  46. in the <guilabel>Pilot Device</guilabel> field in the <link
  47. linkend="page-general">setup dialog</link> or (preferably) link
  48. <filename class="devicefile">/dev/pilot</filename> to
  49. <filename
  50. class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename>
  51. with the following command (as <systemitem
  52. class="username">root</systemitem>):
  53. <userinput>
  54. <command>ln</command>
  55. <option>-s</option>
  56. <parameter>/dev/ttyS<replaceable>n</replaceable></parameter>
  57. <parameter>/dev/pilot</parameter></userinput>
  58. Here <filename
  59. class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename>
  60. is the name
  61. of the serial port; replace <replaceable>n</replaceable>
  62. with the correct number (usually 0 or 1).
  63. </para>
  64. </listitem>
  65. <listitem>
  66. <para>
  67. Check that you have permission to read and write to the serial port.
  68. The permissions for the serial port should be such that you can write to
  69. it. This is most easily done by running the following (as root):
  70. <userinput>
  71. <command>chmod</command>
  72. <option>666</option>
  73. <parameter>/dev/ttyS<replaceable>n</replaceable></parameter>
  74. </userinput>
  75. </para>
  76. </listitem>
  77. <listitem>
  78. <para>
  79. Try starting the daemon by hand before starting &kpilot;.
  80. </para>
  81. </listitem>
  82. <listitem>
  83. <para>
  84. (For &Linux-Mandrake; 7 systems) Check the system security level:
  85. settings higher than 3 prevent some forms of inter-process
  86. communication which are necessary for &kpilot; to
  87. operate correctly.
  88. </para>
  89. <para>
  90. (<emphasis>&Linux-Mandrake; security information
  91. courtesy of Jay Summett</emphasis>)
  92. To set your
  93. <!-- TM? --><acronym>MSEC</acronym>
  94. <!-- TM? -->(Mandrake SECurity)
  95. settings to not block the
  96. &kpilot; socket (for connections to localhost) you can
  97. login as root and
  98. type
  99. <userinput>
  100. <command>/etc/security/msec/init.sh</command>
  101. <option>3</option>
  102. </userinput>
  103. Which will set your
  104. <!-- TM? --><acronym>MSEC</acronym>
  105. level to 3 (regular security).
  106. For more information about the various security levels, &etc;, see:
  107. <ulink url="http://www.linux-mandrake.com/userguide/en/reference/017.html#157">
  108. the
  109. <!-- TM? -->Mandrake
  110. reference guide</ulink>.
  111. </para>
  112. </listitem>
  113. </itemizedlist>
  114. </para>
  115. </answer>
  116. </qandaentry>
  117. </qandaset>
  118. </sect1>
  119. <sect1 id="faq-database">
  120. <title>Database Questions</title>
  121. <para>
  122. This section answers questions commonly asked about
  123. particular databases and how they
  124. interact with &kpilot;.
  125. </para>
  126. <qandaset>
  127. <qandaentry>
  128. <question>
  129. <para>
  130. Databases become corrupted after a sync,
  131. what should I do?
  132. </para>
  133. </question>
  134. <answer>
  135. <para>
  136. Certain databases (from third-party software manufacturers)
  137. appear not to follow the standard database layout.
  138. If you can find out what the creator id of the database is,
  139. you can add it to either the
  140. <guilabel>Backup Only:</guilabel> list or the
  141. <guilabel>Skip</guilabel> list in the
  142. <link linkend="page-backup">settings dialog</link>.
  143. </para>
  144. <para>
  145. The following table shows which databases should be skipped
  146. or backed-up only:
  147. <table id="dbskip">
  148. <title>Databases needing Special Treatment</title>
  149. <tgroup cols="3">
  150. <thead>
  151. <row><entry>Database</entry><entry>Creator ID</entry><entry>Action</entry></row>
  152. </thead>
  153. <tbody>
  154. <row>
  155. <entry>Launcher (the &PalmPilot;'s main menu)</entry>
  156. <entry>lnch</entry>
  157. <entry>Backup Only:</entry>
  158. </row>
  159. <row>
  160. <entry>Arranger</entry>
  161. <entry>Arng</entry>
  162. <entry>Backup Only:</entry>
  163. </row>
  164. <row>
  165. <entry>(unknown)</entry>
  166. <entry>PmDB</entry>
  167. <entry>Backup Only:</entry>
  168. </row>
  169. <row>
  170. <entry>AvantGo</entry>
  171. <entry>avgo</entry>
  172. <entry>Skip (Mostly because there's no point in backing up the
  173. news articles that AvantGo gives you)</entry>
  174. </row>
  175. </tbody>
  176. </tgroup>
  177. </table>
  178. </para>
  179. </answer>
  180. </qandaentry>
  181. <qandaentry>
  182. <question>
  183. <para>
  184. Is there a conduit for &Netscape; <application>Calendar</application>?
  185. </para>
  186. </question>
  187. <answer>
  188. <para>
  189. No, there isn't.
  190. Neither are there plans to include support or write a
  191. conduit for &Netscape; <application>Calendar</application>.
  192. </para>
  193. </answer>
  194. </qandaentry>
  195. </qandaset>
  196. </sect1>
  197. <sect1 id="faq-hotsync">
  198. <title>
  199. Special HotSync Questions
  200. </title>
  201. <para>
  202. This section lists questions about HotSync methods that differ
  203. from the <quote>usual</quote> direct serial link method.
  204. </para>
  205. <qandaset>
  206. <qandaentry>
  207. <question>
  208. <para>
  209. How do I do an infrared (<acronym>IR</acronym>) HotSync?
  210. </para>
  211. </question>
  212. <answer>
  213. <para>
  214. First of all your &PalmPilot; has to actually support
  215. <acronym>IR</acronym> HotSyncs. This can be achieved through various
  216. means: &PalmOS; 3.3 and higher include support for it; there is an
  217. <acronym>IR</acronym> enhancements package for older &PalmOS; versions;
  218. <application>IrLink</application> from IsComplete apparently has the
  219. same capabilities. Check out the <ulink
  220. url="http://www.palmone.com/us/">PalmOne</ulink> web pages for more information.
  221. </para>
  222. <para>
  223. Assuming your &PalmPilot; now has <acronym>PC</acronym> HotSync support
  224. and it is setup to do <acronym>IR</acronym> HotSyncs (in the HotSync
  225. preferences on the &PalmPilot;), we can turn our attention to the
  226. <acronym>PC</acronym> you will be synchronization with. It needs an
  227. <acronym>IR</acronym> port. For laptops, this is trivial, desktop
  228. <acronym>PCs</acronym> may require some extra hardware.
  229. </para>
  230. <para>
  231. Your &Linux; kernel will need to support <acronym>IR</acronym> and the <acronym>IRCOMM</acronym> protocol.
  232. For stock
  233. &RedHat;
  234. systems, the following command should
  235. setup <acronym>IR</acronym> support (as <systemitem class="username">root</systemitem>):
  236. <screen width="40">
  237. <prompt># </prompt><userinput><command>modprobe</command> <option>ircomm</option></userinput>
  238. </screen>
  239. Other distributions should follow the <filename>IR-HOWTO</filename>.
  240. Once <acronym>IR</acronym> support in the kernel has been activated,
  241. you need to make devices for the <acronym>IR</acronym> ports.
  242. The <filename>IR-HOWTO</filename> suggests (as <systemitem class="username">root</systemitem>):
  243. <screen width="40">
  244. <prompt># </prompt><userinput><command>mknod</command>
  245. <option>/dev/ircomm0</option> <parameter>60</parameter> <parameter>64</parameter> </userinput>
  246. <prompt># </prompt><userinput><command>chmod</command>
  247. <option>666</option> <parameter>/dev/ircomm0</parameter></userinput>
  248. </screen>
  249. Next we need to start some daemons for <acronym>IR</acronym> services:
  250. <screen width="40">
  251. <prompt># </prompt><userinput><command>irattach</command>
  252. <option>/dev/ttyS<replaceable>n</replaceable></option></userinput>
  253. <prompt># </prompt><userinput><command>irmanager</command>
  254. <option>-d</option> <parameter>0</parameter></userinput>
  255. </screen>
  256. Here <filename class="devicefile">/dev/ttyS<replaceable>n</replaceable></filename>
  257. is the serial port
  258. the <acronym>IR</acronym> port is using. <replaceable>n</replaceable> could be 0, 1, or some other
  259. number depending on your hardware setup.
  260. Follow the instructions in the <filename>IR-HOWTO</filename> for assistance
  261. (for desktop machines, it's usually a setting in the <acronym>BIOS</acronym>).
  262. </para>
  263. <para>
  264. Once you've gotten this far, just make <filename class="devicefile">/dev/pilot</filename>
  265. point to <filename class="devicefile">/dev/ircomm0</filename>
  266. and you're ready!
  267. </para>
  268. <para>
  269. The IR-HOWTO and other useful information on using IR may
  270. be found at
  271. <ulink url="http://mobilix.org/howtos.html">http://mobilix.org/howtos.html</ulink>
  272. and
  273. <ulink url="http://mobilix.org/software/irda/">http://mobilix.org/software/irda/</ulink>.
  274. </para>
  275. </answer>
  276. </qandaentry>
  277. <qandaentry>
  278. <question>
  279. <para>Can I do a &HotSync; with my (<acronym>USB</acronym>)
  280. <!-- TM? -->&Handspring; &Visor;?
  281. </para>
  282. </question>
  283. <answer>
  284. <para>
  285. Yes, you can.
  286. I don't have definitive information, but postings on the
  287. &kpilot; mailing-list have stated that you can point <filename class="devicefile">/dev/pilot</filename>
  288. to the <acronym>USB</acronym> device and everything will work fine.
  289. </para>
  290. </answer>
  291. </qandaentry>
  292. <qandaentry>
  293. <question><para>Is there any support for remote HotSyncs?</para>
  294. </question>
  295. <answer>
  296. <para>
  297. No, not yet.
  298. Maybe later.
  299. </para>
  300. </answer>
  301. </qandaentry>
  302. </qandaset>
  303. </sect1>
  304. <sect1>
  305. <title>&kpilot;'s &DCOP; interface</title>
  306. <qandaset>
  307. <qandaentry>
  308. <question>
  309. <para>What does &kpilot; use &DCOP; for?</para>
  310. </question>
  311. <answer><para>
  312. The daemon and &kpilot; communicate using &DCOP;
  313. for several purposes: logging messages, changing the &HotSync;
  314. type, and exchanging configuration information.
  315. </para></answer>
  316. </qandaentry>
  317. <qandaentry><question>
  318. <para>Which &DCOP; interfaces are there?</para></question>
  319. <answer><para>
  320. The daemon has two important interfaces:
  321. <interface>LogIface</interface>
  322. and
  323. <interface>KPilotDaemonIface
  324. </interface>.
  325. The <interface>LogIface</interface>
  326. interface is used to record messages in the sync log
  327. on the &handheld;, and is rarely used.
  328. The <interface>KPilotDaemonIface</interface>
  329. is the more important &DCOP; interface,
  330. and is used to control the kind of &HotSync; that
  331. &kpilot; will do.
  332. </para></answer>
  333. </qandaentry>
  334. <qandaentry><question><para>
  335. How can I tell the daemon to perform a specific kind of &HotSync;?</para></question>
  336. <answer><para>
  337. There are three &DCOP; functions that control what kind
  338. of &HotSync;
  339. the daemon will do next:
  340. <function></function>
  341. <function></function>
  342. </para></answer>
  343. </qandaentry>
  344. </qandaset>
  345. </sect1>
  346. </chapter>