--===============0739163929==
Content-Type: multipart/signed;
  boundary="nextPart1363156.xHT67QGbvU";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1363156.xHT67QGbvU
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 23 April 2006 17:46, Jean-Phi (prive) wrote:
> "not working, unrecognised by Kpilot"
> "USB Only device, no COM wire available"
> "My old m100 works, so not a config issue - with a com port"
> "Un-Hacked box, just Suse 93, KDE 3.4.0, Kpilot 4.5.0 "baby""
> "Palm OS Garnet 5.4.0"
>
> Nothing happens during hotsync. No /dev/pilot on my system.

Anything happen in /var/log/messages? If the kernel / OS doesn't recognize =
the=20
device and create the relevant devices / symlinks, there's not much KPilot=
=20
can do. This list is full of messages about not finding devices as well as=
=20
advice on how to troubleshoot it.

=2D-=20
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot

--nextPart1363156.xHT67QGbvU
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQBEToPrdqzuAf6io/4RAoh0AJ9e8Zm3v/H9WujraNw+gHO38Fr7pgCbBiWQ
LEMu4UvNsPLPb+fRaH/UxnI=
=52Dc
-----END PGP SIGNATURE-----

--nextPart1363156.xHT67QGbvU--

--===============0739163929==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users

--===============0739163929==--