public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Raymond Ingles" <sorceror171@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Suggest a bluetooth dongle
Date: Tue, 18 Sep 2007 13:43:20 -0400	[thread overview]
Message-ID: <a481fbf0709181043m7b4700b1qc58d886c991bebae@mail.gmail.com> (raw)
In-Reply-To: <231dafb50709181011n7b7286bua93f205f7878ab9@mail.gmail.com>

On 9/18/07, Chris Hodgins <shadowofdarkness@gmail.com> wrote:

> Please only suggest in-expensive ones that you have personally tested.
> Because I don't want to deal with returning a product bought online.
> Canadian websites would be nice.

 http://www.pcuniverse.com/product.asp?pid=3560912&m_id=32

 Class 1, good range, inexpensive, etc. Works for me on two different
Ubuntu 7.04 systems.

 One caveat: on a P-III 700MHz system, it worked fine with no
problems. On my dual-Athlon 2GHz system, it only works *fully* if I
have it connected at boot time. If I plug it in later, I can see it,
and scan the neighborhood with it, but I wasn't able to get my Treo
650 to network with it. Other than that, no issues. Take that for what
it's worth, I guess.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-09-18 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 17:11 [Bluez-users] Suggest a bluetooth dongle Chris Hodgins
2007-09-18 17:43 ` Raymond Ingles [this message]
2007-09-19  1:57 ` Brandon Casey
2007-09-20 18:39   ` Chris Hodgins
2007-09-21  2:42     ` Brandon Casey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a481fbf0709181043m7b4700b1qc58d886c991bebae@mail.gmail.com \
    --to=sorceror171@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox