synce(7) [sunos man page]
SynCE(7) http://www.synce.org/ SynCE(7) NAME
SynCE - A project for connecting to devices running Microsoft Windows Mobile. DESCRIPTION
The SynCE project aims to provide libraries and tools to connect to and synchronise with PDA's and other devices running Microsoft Windows Mobile, or Windows CE. The main components include :- libsynce Core library that provides various support services and functions. librapi2 Core library implementing the RAPI protocol, equivalent to rapi.dll on a Windows OS. RAPI is used for most kinds of interaction with a WM device. This library actually implements two versions of the protocol. RAPI 1 is used for devices up to and including CE 5.0, with RAPI 2 coming into use from 5.1 (WM5). librra Library implementing RRA (Remote Replication Agent), a protocol used for synchronisation. This protocol is used for all data synchronisa- tion until WM5, at which point Airsync is used for the majority. RRA is still used for file synchronisation however. dccm The dccm daemon negotiates the initial connection with a WM device, and may provide keep-alive signals and client connections, depending on the device version and flavour of dccm. There have been a number of dccm 'flavours'. The original, also known as synce-dccm, is now considered obsolete and should not be used. Vdccm is a natural progression of dccm which is not greatly used anymore. Odccm is the most common in use at the moment, and uses dbus to provide connections to both legacy and modern devices. Hal-dccm is a new option that integrates the dccm functionality into hal to provide a more platform consistent interface. The following steps are required to get started with SynCE: (1) Ensure the rndis kernel module or a serial connection mechanism is installed To use advanced network features (rndis) with a WM5 or later device, which is recommended, you must use the usb-rndis-[lite|ng] driver from SynCE. For older devices or to use serial with WM5, if synce-hal is not used you will require the synce-serial package. You will of course also need a dccm daemon, synce-hal or odccm is recommended. (2) Start the connection daemon (as root) If using odccm, this daemon must run as the root user. With synce-hal, dccm will be started as required. Older dccm implementations must be run as your user. (3) Run tools that access the device (as user) See for example pls(1) and pcp(1). See http://www.synce.org/ for more information about the SynCE project. AUTHOR
This manual page was written by David Eriksson <twogood@users.sourceforge.net>. It was later updated by Jonny Lamb <jonnylamb@jonny- lamb.com> and Mark Ellis <mark@mpellis.org.uk>. SEE ALSO
odccm(1) The SynCE project November 2002 SynCE(7)
Check Out this Related Man Page
SYNCE_INFO_NEW(3) http://www.synce.org/ SYNCE_INFO_NEW(3) NAME
synce_info_new - allocate a new SynceInfo struct SYNOPSIS
#include <synce.h> SynceInfo *synce_info_new(const char *device_name); void synce_info_destroy(SynceInfo *info); const char *synce_info_get_name(SynceInfo *info); bool synce_info_get_os_version(SynceInfo *info, int os_major, int os_minor); int synce_info_get_build_number(SynceInfo *info); int synce_info_get_processor_type(SynceInfo *info); const char *synce_info_get_os_name(SynceInfo *info); const char *synce_info_get_model(SynceInfo *info); const char *synce_info_get_device_ip(SynceInfo *info); const char *synce_info_get_local_ip(SynceInfo *info); int synce_info_get_partner_id_1(SynceInfo *info); int synce_info_get_partner_id_2(SynceInfo *info); const char *synce_info_get_object_path(SynceInfo *info); pid_t synce_info_get_dccm_pid(SynceInfo *info); const char *synce_info_get_transport(SynceInfo *info); const char *synce_info_get_password(SynceInfo *info); int synce_info_get_key(SynceInfo *info); DESCRIPTION
The synce_info_new() function returns a pointer to a newly allocated and populated SynceInfo struct for a mobile device. If device_name is non-NULL, the returned struct relates to a mobile device with that name, or NULL if no device of that name is connected. If device_name is NULL, the exact behaviour depends on the flavour of dccm daemon in use. When using vdccm(1) or the deprecated dccm(1), the current active device is selected. This is usually the last device connected, specifically that described in the active_connection file which is by default in the ~/.synce/ directory. With odccm(1) the first device connected will be returned. With synce-hal this depends on the device(s) in question, and should be considered undefined. This struct should be freed with synce_info_destroy(3). typedef struct _SynceInfo { pid_t dccm_pid; /* process id of dccm daemon */ char* device_ip; /* device ip address */ char* local_iface_ip; /* local interface ip address */ char* password; /* device password */ int key; /* device pass key */ int os_major; /* device OS major version */ int os_minor; /* device OS minor version */ int build_number; /* OS build number */ int processor_type; /* device processor */ int partner_id_1; /* first sync partner id number */ int partner_id_2; /* second sync partner id number */ char* name; /* device name */ char* os_name; /* device OS name eg. PocketPC */ char* model; /* device hardware name */ char* transport; /* interface type */ char* object_path; /* path to device's information */ } SynceInfo; These fields must be accessed with the synce_info_get_ functions. The particular fields populated depend on the flavour of dccm daemon in use. The use of dccm(1) is deprecated. When using vdccm(1) all fields are populated except for local_iface_ip and os_minor. With odccm(1) and synce-hal, dccm_pid, password, key, build_number, partner_id_1 and partner_id_2 are not used. odccm(1) also does not populate local_iface_ip. RETURN VALUE
The synce_info_new() function returns a pointer to the allocated SynceInfo struct, or NULL if an error occured. SEE ALSO
synce(7), odccm(1), vdccm(1) The SynCE Project 2007-08-26 SYNCE_INFO_NEW(3)