Return-Path: <postfix@gmx.com>
Date: Fri, 13 Feb 2004 12:37:49 +0100
From: Radu Maurer <a400@gmx.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Apple keyboard
Message-ID: <20040213113749.GA13481@mail.gmx.de>
References: <20040210175802.GA17705@mail.gmx.de> <1076451979.2777.21.camel@pegasus> <20040211151146.GA19818@mail.gmx.de> <1076515215.2696.36.camel@pegasus> <20040213105035.GA10464@mail.gmx.de> <1076669640.2671.27.camel@pegasus>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="h31gzZEtNLTqOjlF"
In-Reply-To: <1076669640.2671.27.camel@pegasus>
List-ID: <bluez-users.lists.sourceforge.net>


--h31gzZEtNLTqOjlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fr, 13 Feb, 2004 at 11:54:00 +0100, Marcel Holtmann wrote:
> Hi Radu,
> 
> > hcidump -w <file> seems to write a binary file. Do you nee that file? 
> > Anyway, if I don't give the -w option, it dumps this to stdout:
> 
> yes.

ok, see attachment.

> So it is a pairing problem. Check the keyboard manual how the pairing
> procedure should work. Maybe it has a default PIN or you have to use the
> num pad for input.

The manual just sais to follow the instructions on screen :-(
There is no default PIN in the manual.
I tested it on windows 2000: there you get a PIN written on the screen,
which you have to type on the keyboard.

thanks
Radu


--h31gzZEtNLTqOjlF
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="hcidump.log"
Content-Transfer-Encoding: base64

EQAAAMeqLECYPQAAAQUEDcw/OpUKABjMAgAAAAEHAAEAx6osQIpcAAAEDwQAAQUEDgABAOWq
LEA17AUABAMLIikAzD86lQoAAQA=

--h31gzZEtNLTqOjlF--