synce-serial-abort(8) [debian man page]

SYNCE-SERIAL-ABORT(8)					   http://synce.sourceforge.net/				     SYNCE-SERIAL-ABORT(8)

NAME

       synce-serial-abort - Force a SynCE serial connection to abort.

SYNOPSIS

       synce-serial-abort

DESCRIPTION

       synce-serial-abort is used to force a shutdown of an existing serial connection.  It should only be used if the connection cannot be closed
       by other means.

       This must be done with root privileges.

AUTHOR

       This manual page was written by David Eriksson <twogood@users.sourceforge.net>.

SEE ALSO

       synce(1) pppd(8) synce-serial-config(8) synce-serial-start(8)

The SynCE project						   November 2002					     SYNCE-SERIAL-ABORT(8)

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)