Welcome, Guest. Please login or register.

Author Topic: Finding the bluetooth chipset  (Read 1751 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline whabangTopic starter

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 7270
    • Show only replies by whabang
Finding the bluetooth chipset
« on: September 16, 2004, 10:23:36 AM »
I have an USB-bluetooth adapter, which I can't find a driver for.
MacOS 10.3.4 detects the adapter, and has it's own driver, but Windows XP doesn't.

According to MacOS the VendorID is 1208, and the DeviceID is 2561. Is it possible to find out which chipset is in the adapter, so that I can find a Windows XP driver for it?
Beating the dead horse since 2002.
 

Offline whabangTopic starter

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 7270
    • Show only replies by whabang
Re: Finding the bluetooth chipset
« Reply #1 on: September 16, 2004, 01:20:32 PM »
 :bump:
Beating the dead horse since 2002.
 

Offline pjhutch

  • Sr. Member
  • ****
  • Join Date: Mar 2002
  • Posts: 452
  • Country: england
  • Gender: Male
  • Amiga user and developer
    • Show only replies by pjhutch
    • http://www.pjhutchison.org
Re: Finding the bluetooth chipset
« Reply #2 on: September 16, 2004, 01:23:37 PM »
 

Offline whabangTopic starter

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 7270
    • Show only replies by whabang
Re: Finding the bluetooth chipset
« Reply #3 on: September 16, 2004, 01:41:05 PM »
Thanks, but:

That's a steel manufacturing company.
Are USB-manufacturer's IDs identical with their PCI-counterparts? :-?
Beating the dead horse since 2002.
 

Offline whabangTopic starter

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 7270
    • Show only replies by whabang
Re: Finding the bluetooth chipset
« Reply #4 on: September 16, 2004, 02:06:23 PM »
After a bit of net lurking, I found out that it's Seiko Epson.
http://www.usb.org/app/search/contacts/by_company
Well, I suppose i can forget using it for my PC.
On the other hand, I should work perfectly fine with my printer! :-P
Beating the dead horse since 2002.