Once &kpilot; is installed it needs to be configured to match your hardware. The conduits need to be configured as well. After that you can use &kpilot; to synchronize your &PalmPilot; with your &kde; desktop or view data from your &PalmPilot; with the built-in viewers. When you run &kpilot; from either the panel menu or from the command prompt for the first time it will prompt you with a dialog box to configure it. This configuration dialog can be requested later from the main application Settings Configure &kpilot; menu, from the &kpilot; daemon popup menu Configure KPilot... menu item or by starting &kpilot; from the shell as follows: $ kpilot--setup In addition, if you upgrade &kpilot; and some new configuration options require your attention, this setup dialog will reappear. Configuration Dialog The configuration dialog The configuration dialog &kpilot;'s configuration dialog is a large one. This is because it contains not only the configuration of the device for communicating with the &PalmPilot;, but also the configuration of all the installed conduits. Each group of configuration options (general and conduits) will be discussed separately. We will begin, however, by taking a look at the configuration wizard, which should make most of the general group of configuration options superfluous. The configuration wizard helps you to set up &kpilot; to communicate with the &PalmPilot; and to configure the conduits as a group. It's a great start for new users, and you can always fine-tune your preferences later. In the Pilot Info dialog, type your User Name. It should match the one from the &PalmPilot;. Next, type the file name of the Device you will use to connect the &PalmPilot; (The connection can be through a serial port, USB port, infrared, Bluetooth, network or the generic /dev/pilot device.) Alternatively, click the Automatically detect handheld and user name... button and press the &HotSync; button on your &handheld;. The Wizard will try to find the correct Device and User Name. If the Device does not have the right permissions, the wizard will not be able to find it. Normal users must be able to read/write the correct device. To resolve this issue, please refer to &kpilot; says Can't connect to pilot &FAQ; entry, or contact your system administrator. The First Configuring Wizard Dialog Configuring Wizard: The Pilot Info Dialog Configuring Wizard: The Pilot Info Dialog Press the &HotSync; button of your &handheld; to probe for the correct Device and User Name. The Second Configuring Wizard Dialog Configuring Wizard: The Autodetection Dialog Configuring Wizard: The Autodetection Dialog &kpilot; has the ability to sync the data on your &handheld; with applications or files on your PC. The programs that perform these actions are called conduits. The sync dialog configures all applicable &kpilot; conduits to sync with widely used PIM suites. You can fine-tune these settings later, from the Settings Configure &kpilot; menu. Please check the conduits configuration section of this document for more information. The Third Configuring Wizard Dialog Configuring Wizard: The Sync Dialog Configuring Wizard: The Sync Dialog The settings available in the &kpilot; configuration dialog under the heading General Setup give you detailed control over the operation of &kpilot;: you can select a non-standard hardware device, set special encodings for foreign-language &handheld;s, and control how &kpilot; displays your data. There are five items under the General Setup heading. You may need to expand the General Setup heading to see them. Items under General Setup The items under General Setup The items under General Setup This is a setup page that contains options describing the &PalmPilot; hardware, you, the user and how you want the various parts of &kpilot; to be started. Device Page The Device Page The Device Page Pilot device The port that the cradle is connected to. By default it is set to /dev/pilot which should be a symbolic link to the real port. The port might be a serial port, in which case /dev/pilot should point to something like /dev/cuaa0 (in &FreeBSD;) or /dev/ttyS0 (in &Linux;). For &USB; devices, it can be more difficult to determine where /dev/pilot should point. It may be possible to configure your &USB; daemon to set up the link automatically, so that /dev/pilot points to the right port no matter where you plug in your &PalmOS; device. Make sure the port has the correct permissions. It must be read/write by all if &kpilot; is intended to be used by a normal user! &kpilot; will complain if the permissions are wrong, but you will need to fix the permissions by hand. This could be done by doing a chmod 666 device as root where device is the correct port. To resolve this issue, please refer to &kpilot; says Can't connect to pilot &FAQ; entry, or contact your system administrator. You can also use network sync (with pilot-link 0.11.5 and later) by entering net:any as the device name. Speed Indicate the speed of the serial connection to the &PalmPilot;. It has no meaning for &USB; devices. For an older model &PalmPilot;, choose 9600. Newer models may be able to handle speeds up to the maximum listed, 115200. You can experiment with the connection speed: the &PalmPilot; manual suggests starting at a speed of 19200 and trying faster speeds to see if they work. Encoding &PalmOS; devices are available in many different languages. If your device uses a different encoding than ISO-latin1, you will need to select the correct encoding from the list in order to display special characters correctly. If you can enter Russian in your &PalmPilot;, select CP1251, for instance. Pilot user The user name of the &PalmPilot;. By default this name is the same as your log on name. When you sync with the &PalmPilot; &kpilot; will check to see if this name matches the one on the &PalmPilot;. If they do not, you are asked to pick which you will use. If you pick the local name, the &PalmPilot; will be changed to match. The Pilot User entry is also used to name the folder that stores the information from the &PalmPilot;. This folder is created in the $TDEHOME/share/apps/kpilot/DBBackup/ folder, where the $TDEHOME environment variable (typically /home/Login Name/.kde/) points to the folder that contains your configuration and data for the &kde; applications. This page contains settings with which you can instruct &kpilot; to perform special kinds of &HotSync;, as well as direct how conflicts during a &HotSync; should be resolved. A conflict happens when both the desktop application and the &handheld; application change the same data. &kpilot; interfaces with your &handheld; in two ways: using the the conduits and the internal viewers. Conduits are plug-in programs which extend the synchronization capabilities of &kpilot;. &kpilot; stores separate copies of the databases and records for conduits, while the internal viewers and backup operation share the same copy. This distinction is important to choose your update method depending on your usage. If you use mainly the conduits to sync your &handheld; with external programs, you may choose as default synchronization method any option that runs the conduits. However, if you use mainly the internal viewers, you need to update copy of the databases as well in order to view and edit the information from your &handheld;, so running the conduits only is not sufficient. The &HotSync; setup page The &HotSync; Page The &HotSync; setup page Default Sync Select the type of synchronization that will be performed by default. HotSync: run all selected conduits, sync the databases with a modified flag set, updating the modified records only. Performs a fast backup, backing up only the databases that were modified. This option offers a nice balance between speed and data safety. FastSync: Only synchronize those databases that have conduits, and perform no backup of the data on the &PalmPilot;, reducing greatly the time required for the sync operation. This also means that if something goes wrong with your &PalmPilot;, you may not be able to recover the databases. This is a classic trade-off between speed and safety. FullSync: run all selected conduits, and sync all databases, reading all records, and performing a full backup. It is the safest option, but takes the longest time to complete, as it will merge all the records from the &handheld; and your desktop. It is the &kpilot; equivalent of the Palm SlowSync. Copy PC to handheld: run all conduits and sync all databases, but instead of merging the information from both sources, copy the PC data to the handheld. Use with care, as this option erases the changes you made in your handheld since the last sync. Copy handheld to PC: run all conduits and sync all databases, but instead of merging the information from both sources, copy the handheld data to the PC. Use with care, as this option erases the changes you made in your PC since the last sync. Remember, when &kpilot; does a &HotSync; and runs the conduits, the databases in the internal viewers are not updated. To update the internal viewers, use the FullSync or backup actions. Do full backup when changing PCs If you &HotSync; your &handheld; with multiple PCs, the flag on the &handheld; that stores which records have changed since the last &HotSync; may be inaccurate. It is recommended to do a full sync when changing PCs. You can disable the full sync by unchecking this box. Conflict Resolution Data records can be changed both on the &handheld; and on the PC. If one record has incompatible changes in both the &handheld; and the PC, (such as changing a phone number in different ways on both sides), the conflicting change needs to be resolved so that the &handheld; and the PC data are consistent again. Choices for conflict resolution are: Ask User: pop up a dialog for the user to choose how the conflict is to be resolved for every conflict. Do Nothing: leave the entries in an inconsistent state. Future syncs may not notice the discrepancy. Handheld Overrides: copy the values from the &handheld; to the PC, discarding the changes on the PC. PC Overrides: copy the values from the PC to the &handheld;, discarding changes on the &handheld;. Values From Last Sync (if possible): &kpilot; stores a backup copy of the information on your &handheld; depending on the synchronization method you selected. If this information is available, use neither the values from the &handheld; nor the PC, but the values from the last sync. Use Both Entries: Create duplicate entries of the conflicting records on both the PC and &handheld;, one with the value from the PC, the other with the value from the &handheld;. This page contains settings specific to the backup operation, which saves a copy of the the &handheld; databases, allowing the user to restore this information later. In short, databases are all files stored in your &handheld;. A database can be either a record database, which stores dynamic information created by the user (for instance, the addresses or the todo information), or a resource database, which tend to be static (for instance the applications). Backup Page The Backup Page The Backup Page Databases List databases that should not be synced or backed up. The values can be either database creator values, which are 4-letter strings surrounded by square brackets (so for Handbase databases you fill in [PmDB]), or database names, which are strings without square brackets that may contain shell-style wildcards. See the FAQ for a list of databases that should be listed here (the default should be OK though). Newer &PalmPilot; devices contain emulation code for the older 68k processor; this means that they have a large number of databases with names ending in _a68k. These do not need to be backed up nor synced, so you could add *_a68k to the list of databases to skip. No backup List here databases that should be excluded from the backup operation. Some databases do not follow the standard database layout, and trying to backup and restore them will result in information loss. You may include here databases with volatile information, such as news or web pages, that often do not require to be backed up. Not restored List here databases that should be excluded from the restore operation, even if they were previously backed up. Databases included here can be installed manually later, using the File Installer. You may include here databases with volatile information, such as news or web pages, that often do not require to be restored. Changing the contents of the No backup or Not restored fields, in particular removing the databases already listed there, can damage those databases when you perform a &HotSync;. Run conduits during a backup The backup typically updates the copy of the &handheld; databases. Conduits are programs that extend the &kpilot; functionality. Running them usually means synchronization the &handheld; to other PC databases, like the address book or the calender. Check this box to perform both operations on every backup. &kpilot; contains viewers for presenting information from the &PalmPilot;. These viewers present the databases available on the &PalmPilot; in much the same way that the device itself does. Not all databases have an application-specific viewer, though you can use the generic database viewer for those. The viewers page contains settings for the internal viewers in &kpilot;. These settings change the way in which the data is shown. Viewers Page The Viewers Setup Page The Viewers Setup Page Make internal viewers editable The internal viewers can be read only or editable. The editable mode allows you to add new records, delete or edit the existing records and sync your modifications back to the &handheld;. Check this box to set the internal viewers to editable mode, uncheck to set them to read only mode. On some &kpilot; versions, it is not possible check this box, and therefore to use the internal viewers as editors. Show private records In your &PalmPilot; you can mark some records as private. By default, &kpilot; does not display these records on the screen. Check this box if you want to see them. Address Viewer Set there the options for the address internal viewer. Show as "Last, first" or Show as "Company, last": the order and display of the address records in the address internal viewer can be set to match the &handheld;. Select the option that suits better your personal preferences. Use key field Check this box to combine entries with the same last name. This pages present options related to the startup and exit of &kpilot; and &kpilot; daemon. While &kpilot; is the front-end for the internal viewers, configuration options and logs, the sync operation is handled by the &kpilot; daemon. Even if &kpilot; is not running you can &HotSync; if the daemon is. Therefore, if you want to be able to sync your &handheld; at anytime, it is important to start the daemon at login, or the opposite, if you want to be able to sync only when &kpilot; is running, you have to stop the daemon on exit. The last option is especially usefull if you have other applications that use the same port as &kpilot;. Startup and Exit Page The Startup and Exit Page The Startup and Exit Page Startup Options Start daemon at login: By checking this, a link to the daemon is placed in your autostart folder and will be started automatically. Note that this is not normally needed if the daemon is docked in the panel. Show daemon in panel: Check this box to instruct the daemon to place a &kpilot; icon in the system tray. This icon has a menu that can be brought up with the right mouse button. Without this option, the daemon is not visible to the user at all. Exit Options Quit after HotSync: When this option is enabled, both &kpilot; and the &kpilot; daemon will exit after the &HotSync; operation has completed, leaving the device port free for other tools. This may be needed on systems where the &USB; daemon starts &kpilot; automatically. Stop daemon on exit: Setting this option will cause the daemon to exit when you quit &kpilot;, leaving the device port free for other &PalmPilot;-synchronization tools such as malsync Conduits are programs that interface your &handheld; data with PC applications or sync your &handheld; data with files that can be used by PC applications. They can be written by third parties, to interface your &PalmPilot; to any application imaginable. &kpilot;'s configuration dialog allows you to select which conduits to run during a &HotSync; and to configure those conduits. A window similar to the following will be displayed: The Conduit Setup Dialog The Conduit Setup Dialog The Conduit Setup Dialog Check the box to the left of the conduit name to make it active, uncheck to make it inactive or click on the conduit name to configure it. KNotes / Memos Synchronizes the Memo Pad application with &knotes;. Notepad Exports the free hand notes of the &handheld;'s Notepad application as pictures to the PC. Time Synchronization Sets the &handheld;'s time to that of the desktop machine. Useful for keeping the clock of the &handheld; accurate. Calendar (KOrganizer) Synchronizes the Datebook application with &korganizer; or with an iCalendar file of your choice. Palm DOC Automatically converts and installs text files in the &PalmPilot; DOC format, so you can read the text files with most DOC-capable applications on the &handheld;. Addressbook Synchronizes the Address application with &kaddressbook; or with a vCard file of your choice. System Information Writes information about your &handheld;, (such as OS version, RAM available, and the list of databases) to a file. Useful mostly for debugging purposes. ToDo's (KOrganizer) Synchronizes the Todo list application with &korganizer; or with a iCalendar file of your choice. MAL (AvantGo) Conduit Synchronizes your &handheld; with the &AvantGo; server. The &AvantGo; server offers general content (news, guides, stock quotes, &etc;) in a format that is suitable for reading in a &handheld;. To use this conduit, you need to register, subscribe the channels you select and install the &AvantGo; software on your &handheld;. Mail Sends mail written on the &handheld; through &kmail;. There is no provision for receiving mail, however. The &knotes; Conduit is a partial replacement for the built-in memo application. It keeps the notes you write with &knotes; synchronized with the memos you write on your &PalmPilot;. Setting up the &knotes; conduit is very simple. &knotes; Conduit Setup &knotes; Conduit Setup &knotes; Conduit Setup In the General Tab there are two configuration options: Delete KNote when Pilot memo is deleted Uncheck this box if you wish to maintain the note on &knotes; even if the correspondent memo was deleted on the &handheld; memo application. Suppress delete-confirmation in KNotes If the Delete KNote when Pilot memo is deleted box is checked, you may check this box to automatically delete the notes that correspond to a deleted memo, without confirmation. By default, the options delete knote and suppress delete-confirmation are turned off, so that notes will accumulate on your PC. The Notepad Conduit exports the free hand notes of the &handheld;'s Notepad application as pictures to the desktop. To set the folder to which the pictures should be exported, either enter it in the Output edit box or select it clicking the file picker button. The Time Synchronization Conduit syncs the &handheld;'s time to that of the desktop machine. It is useful for keeping the clock of the &handheld; accurate. There are really no configuration options other that enabling and disabling the conduit, as currently only one direction for the synchronization is enabled, you can only Set the handheld time from the time on the PC, and not Set the PC time from the time on the handheld. &PalmOS; Version 3.25 and 3.3 do not support setting the &handheld; system time. For these systems, the conduit will be simply skipped. This conduit will synchronize your &PalmPilot; with &korganizer; and &kontact; or to an iCalendar file of your choice. In the latter case, the conduit will need the filename of the calendar file (this will usually be a file that ends in .ics) to sync with, of if it uses the standard &korganizer; iCalendar file, it will be under the $TDEHOME/share/apps/korganizer/ folder, where the $TDEHOME environment variable (typically /home/user/.kde/) points to the folder that contains your configuration and data for the &kde; applications. The Calendar Conduit Setup Dialog Calendar Conduit Setup Calendar Conduit Setup In the General page, you can set the calendar options. Calendar Destination Choose between synchronizing with the Standard Calendar, or in other words, the &korganizer; standard calendar or with a Calendar file of your choice, that you must either write in the Calendar file edit box or select using the file picker. You can use the calendar conduit with any application that accepts a file in the iCalendar format as a resource. However, some applications, like Evolution, do not handle the synchronization gracefully while they are open. As a rule of thumb, quit these applications before synchronizing, otherwise you will lose data. There is no need to take these precautions when syncing with &korganizer; or &kontact;. Store archived records in the KDE calendar Check this box to save a copy of the archived records from your &handheld; on the PC, in order to keep a history of past appointments in you &kde; desktop as well. In the Conflicts page, you can set the calendar options, overriding &kpilot;'s general settings for conflict resolution when you are using this conduit. For a detailed description of the different conflict resolution possibilities available, please refer to the HotSync Setup section of this handbook. The Palm DOC conduit converts text files in your PC from and to databases in Palm DOC format in the &PalmPilot;. You can use any Palm DOC reader to view these files on your &PalmPilot;. Palm DOC Conduit Setup Palm DOC Conduit Setup Palm DOC Conduit Setup After changing the Palm DOC conduit configuration, you have to restart &kpilot; to let the changes you made take effect. In the General page, you can set the location of the text documents in your computer and the direction of the synchronization. Text files: Type on the text box or use the file picker to select the location of the folder that the Palm DOC conduit uses a as the place for the text files it will sync with the &handheld;. There, you may place the text documents you want install or synchronize to the PDA, and find the text documents created from Palm DOC databases in your &handheld;. The file name has to end in .txt for the conduit to recognize it as text. If the file is not recognized as text, it will be ignored by the conduit. Also, the text has to be in an encoding that is compatible with your &handheld; encoding. Therefore, if the text file has characters that are not being correctly recognized by the Palm DOC reader in your &handheld;, try opening the file a text editor, like &kwrite;, and saving it in an compatible text encoding using the Save As.. dialog, or set the encoding in the PC -> Handheld tab. Local copy: If you want to save a copy of the Palm DOC databases from your &handheld; in your computer, check the Local copy: box and type on the text box or use the file picker to select the location of the folder where these databases will be saved. Synchronization Mode The Palm DOC conduit has the ability to sync from and to the &handheld;, automatically converting the text files to Palm DOC databases and vice versa. The Sync only PC to PDA option will convert all text files located in the folder you selected above to Palm DOC databases and install them in your &handheld;. The Sync only PDA to PC option will convert all Palm DOC databases from your &handheld; to files and install them in the folder you selected above. Finally, The Sync all option allows the synchronization to work in both directions. When both the text file and the Palm DOC database are modified, you cannot merge the modifications, you have to choose one of the versions, losing the changes in one of them. In the PC -> Handheld page, you can configure the Palm DOC compression and bookmarks settings to use when converting from text files to Palm DOC databases. Compress Palm DOC documents can be compressed, saving considerable amounts of available memory in your &handheld;. Most Palm DOC readers support compressed documents, but if you use a reader or editor that is not compatible with compression (for instance, the Sied editor), you will not be able to read or edit the compressed Palm DOC documents created by this conduit. Therefore, check this box to save &handheld; memory, but uncheck it if you have compatibility problems with compressed Palm DOC in your favorite editor or reader. Convert bookmarks The Palm DOC format has a provision for bookmark records. Bookmarks allow you to easily jump to selected parts of the document, making browsing long documents easier. Check this box to allow the Palm DOC conduit to create bookmark records. To create them, the conduit has to know the location in the text and the name of the bookmark. There are three supported ways to let the conduit know the location and name of the bookmark: from inline tags in the text, from tags at the end of the text and from a .bmk bookmark file. To make the creation of bookmarks effective, you have to check at least one of these boxes below. Inline tags in text Convert tags in the format <* BookmarkName *> located inside the text to Palm DOC bookmarks, where the location of the tag in the text will be converted to the bookmark location and the BookmarkName text inside the tag will be converted to the name of the bookmark in the Palm DOC format. The tag will be removed from the resulting Palm DOC document, leaving the text clean. This is a very easy and intuitive way to create bookmarks in your Palm DOC documents. Tags at end of text Convert tags in the format <BookmarkName> located in the end of the text to Palm DOC bookmarks. Whenever the BookmarkName text appears in the text, the conduit will generate a the bookmark in the resulting Palm DOC document pointing to it. The tag will then be removed from the resulting Palm DOC document, leaving the text clean. This is a simple way to create repetitive bookmarks, like one for each Chapter in your Palm DOC documents. Regular expressions in .bmk file This is the most complex but the most powerful way to create bookmarks. The method involves using regular expressions (QRegExp) in a file TextName.bmk, where TextName.txt is the filename of the text, to search the text for bookmarks. See the documentation for an in-depth description of the bmk file format. Encoding Set here the encoding of your &handheld;. &kpilot; will convert the text document to this encoding when exporting the file to the &handheld;. In the Handheld -> PC page, you can configure bookmarks settings to use when converting from Palm DOC databases to text files. Convert Bookmarks The Palm DOC format has a provision for bookmark records. Bookmarks allow you to easily jump to selected parts of the document, making browsing long documents easier. The Palm DOC conduit can convert Palm DOC bookmark records to a format that is readable in your computer, either as a separate file or as tags in the middle of the text file. Select Do not convert bookmarks if you want to ignore the Palm DOC bookmarks, resulting in a text that is clean from bookmark tags. The Convert into .bm file options also result in a clean text file, as the bookmarks are converted to a separate file in the bmk format, as described here. The file is saved with a .bm extension to avoid conflicts with .bmk files created previously. Finally, the Convert as inline tags option creates inline tags inside the resulting text file form <* BookmarkName *> placing each tag in the place that was previously referenced by the bookmark, and using the bookmark name as the BookmarkName text inside the tag. Now you You can edit the bookmark name, move it or delete it and convert back to Palm DOC, as you wish. Do not convert, if text unchanged (only bookmarks) If you check this box, only changes in the text will trigger conversions from Palm DOC to text files. In other words, changes in the bookmarks only will not result in updates for the text files in your computer. In the Conflicts page, you can configure how the conduit deals with files that changed both in the computer and the &handheld;. Conflict Resolution The Palm DOC conduit does not feature merging the modifications when a text is changed both in the &handheld; and in the computer. Therefore, the choice is between working with the files out of sync, or discarding the changes in one of them. The No resolution option will avoid synchronizing texts with conflicts, the PDA overrides option will overwrite the computer text file version in case of conflict, the PC overrides will do the same, but the other way around, and the Ask the user option will bring a dialog to let the user decide on a file by file, case by case basis. Always show resolution dialog, even when there are no conflicts This option will always bring the conflict resolution dialog, even if there is no conflicts to solve. The advantage is that you can keep track of all the files that are being covered by the conduit. This conduit will synchronize your &PalmPilot; with the &kde; address book or to a vCard file of your choice. In the latter case, the conduit will need the filename of the vCard file (this will usually be a file that ends in .vcf) to sync with, of if it uses the standard &kde; address book file, it will be under the $TDEHOME/share/apps/kabc/ folder, where the $TDEHOME environment variable (typically /home/Login Name/.kde/) points to the folder that contains your configuration and data for the &kde; applications. The &kaddressbook; Conduit Setup Dialog &kaddressbook; Conduit Setup &kaddressbook; Conduit Setup In the General page, you can set the general address sync options. Sync Destination Choose between synchronizing with the Standard address book, or in other words, the &kde; standard address book or with a vCard file of your choice, that you must either write in the vCard file edit box or select using the file picker. You can use the address book conduit with any application that accepts a file in the vCard format as a resource. However, some applications may not handle the synchronization gracefully while they are open. As a rule of thumb, quit these applications before synchronizing, otherwise you may lose data. There is no need to take these precautions when syncing with the &kde; address book. Store archived records in the KDE address book The &handheld; offers an option to archive deleted addresses in your desktop. If that option is selected, check this box to keep the deleted addresses from your &handheld; in your PC address book. These addresses will be no longer synchronized with your handheld. In the Conflicts page, you can set the address book conduit options, overriding &kpilot;'s general settings for conflict resolution when you are using this conduit. For a detailed description of the different conflict resolution possibilities available, please refer to the HotSync Setup section of this handbook. In the Fields page, you can set the conduit options for synchronizing the &handheld; address fields that do not have a direct counterpart in the &kde; address book. Handheld other phone: The Other field in the &handheld; address application can be used for many things (for instance storing a secondary email address). It is not clear how to classify this field in &kde;. Depending on your usage, select in the dropdown the field from the computer that will be synchronized with the Other field from your &handheld;. Handheld street address: While the Address field in the &handheld; address application is the only default option for storing an street address, the &kde; street address field can be a home address or a business address. The preferred address will have precedence over other addresses, and the conduit will try to set this status by default. Either the home or business street address will be used to store the &handheld; street address. Select in the dropdown the option that suits better your needs. For instance, if you use this field mainly for business addresses, select Preferred, then Business Address. If not, select Preferred, then Home Address. Handheld fax: While the Fax field in the &handheld; address application is the only default option for storing a fax number, the &kde; address book can store a home fax or a business fax number. Select in the dropdown the option that suits better your needs. For instance, if you use this field mainly for business faxes, select Business Fax. If not, select Home Fax. In the Custom Fields page, you can set the conduit options for dealing with the Custom fields from your &handheld; address application. Since there are no natural correspondence between these fields and other &kde; address book fields, you can set them as you like. You can use them to store a URL, a IM Address, the Birthdate of your contact or the obvious: Store as Costume Field. If you select to store birthdays, remember to use a date format that is consistent with the settings in the Date format dropdown, so that the conduit can correctly identify the date from the record and vice versa. Possible placeholders are: %d for the day, %m for the month, %y for the two-digit year, %Y for the four-digit year. For example, %d.%m.%Y would generate a date like 27.3.1952, while %m/%d/%y would write the same date as 03/27/52. This conduit generates a page with your &handheld; information. Some info about your &kde;, &kpilot; and Pilot-Link version is included as well. The available output formats are &HTML;, text or custom template. The conduit output and in special, the debug output section of the output may help the developers track down bugs. The System Information Conduit Setup Dialog System Information Conduit Setup System Information Conduit Setup In the General page, you can set the output location and format. Output File Write in the edit box or use the file picker to select the location and file name of the output file where the &handheld; system information will be written. Type of Output Choose between HTML, Text file (plain text), or a selectable Custom template. To create a custom template, you can use the default template as a reference. In the Parts Included page, you can set which parts will be included in the output, one by one, by checking or unchecking them in the Output Type list. This conduit will synchronize your &PalmPilot; To Do List application with &korganizer; and &kontact;, or to an iCalendar file of your choice. The configuration dialog looks and behaves exactly the same as the configuration dialog for the Calendar Conduit. The only difference is that instead of synchronizing the Calendar, you will be syncing the To Do List. The Calendar Conduit Setup Dialog Calendar Conduit Setup Calendar Conduit Setup The MAL (&AvantGo;) Conduit synchronizes your &handheld; with the &AvantGo; server. This conduit is based on Jason Day's libmal. The &AvantGo; server offers general content (news, guides, stock quotes, &etc;) in a format that is suitable for reading in a &handheld;. To use this conduit, you need to register to a service provider, for instance, AvantGo.com, subscribe the channels you select and install the &AvantGo; software on your &handheld;, and configure the software on your handheld to find the MAL server. The installation software for the &handheld; client is usually only available for &Microsoft; &Windows;, if you do not have access to a windows computer, you can try installing the databases available in the MalSync Homepage, with different versions, one for PalmOS 5 and other for older PalmOSs. To configure the software on your handheld to find the MAL server, open the AGConnect application in your &handheld;, click Settings... and enter your MAL server address, the User Name and Password you got while registering. The &AvantGo; server address is sync.avantgo.com, and its port is 80. On some installations, you should use the MobileLink instead of the AGConnect application on your &handheld;. The MAL (AvantGo) Conduit Setup Dialog MAL (AvantGo) Conduit Setup MAL (AvantGo) Conduit Setup In the General page, you can set the synchronization frequency options. It can be set for Every Sync, Once per Hour, Once a Day, Once a Week or Once a Month. The conduit only runs when you hit &HotSync; on your &handheld;, so Once per Hour, for instance, really means that &kpilot; will only try to synchronize with the MAL servers if it is more than an hour since the last MAL sync. The MAL conduit can work through a proxy server. In the Proxy page, you can set the proxy settings. Proxy Type If you connect the Internet directly, select No proxy, requiring no further configuration. But if you use a HTTP proxy or a SOCKS proxy, select it, to enable the rest of the dialog and to make the conduit use it to connect the MAL server. Server Information Write in the Server Name dropdown box the address of the proxy server to use, in the form foo.bar.com, not http://foo.bar.com or http://foo.bar.com:8080. Check the box Custom port: if your proxy uses a non standard port, and enter the correct port number. In the No proxy for edit box, you may enter the list of MAL servers that do not need the use of a proxy, separated by commas. For instance, localhost,lan. If your proxy require authentication, enter your User name and Password in the respective edit boxes. In the MAL Server page, you can set the MAL server address and settings. Currently, you can only configure this settings using the &handheld; MobileLink or AGConnect applications, so this page is disabled. This conduit allows you to send mail using a transport. The configuration of the Mail Conduit is fairly simple. Setting up the Mail Conduit The Mail Conduit Setup Dialog The Mail Conduit Conduit Setup Dialog There are two tabs in the setup dialog for the Mail Conduit, one for Sending mail and one for the credits of the mail conduit. Depending on which send method you choose, different fields will be activated in the remainder of the tab, allowing you to enter the necessary information. Currently, the only method available is Using KMail, which has a very simple configuration. Your email address can be entered in the Email Address: field. This is the email address that goes in the From: line in outgoing mail. If you enter a file name in the Signature File field then that file will be appended to each outgoing mail as a signature. When sending mail through &kmail;, &kpilot; automatically places it in your &kmail; outbox. &kmail; saves mail in the outbox until you request that those pieces of mail are really sent.