12-19-2013 05:52 PM
Sorry Maevid to here you re-installed but it’s not your problem its R.F. as they can't provide you or me with a driver. Broadcom makes the chips, is not responsible to provide you a driver.
I have the same situation however I’m not an average user, and put a sniffer on my network to see the request going out to “update.broadcom.com” but my machine received no answer from them. Called R.F. t/s and they were no help either, this needs to be escalated as the courteous tech on the fones solution was to return it?
Isn’t there a law in the US from the FTC that states that you have to support your product for 7 years?
12-25-2013 11:29 AM
I had a similar problem as the device could not be validated in stage 2 of the Broadcom installation and certain features are not available in the generic Windows drivers. Don't know who is at fault rocketfish or broadcom. Able to resolve though by installing drivers from HP. http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?cc=us&lc=en&softwareitem=ob-76382-1
This is sp44774.exe, ~58MB. Luck.
12-26-2013 12:50 AM
So the real solution here (besides using HP's driver) is get a refund on your Rocketfish products and never buy from them again? I really hate it when companies make garbage they refuse to support.
12-26-2013 01:37 PM
No that machine runs win7. Its not an HP either. I don't think its hardware specific so you could probably grab any bluetooth device driver from a major manufacturor as long as its specific to your OS. I'm just guessing that, I've only tried it on my daughters comp so she could play music in different rooms.
12-26-2013 02:59 PM
In my experience vista and later drivers don’t work for winxp, I’ve looked for a suitable one just haven’t found 1; understand that the device works on my laptop, just I can’t use any advanced functions of my mouse, so its not the end of the world, just wish that korp amerika had to face the same music that real people do.
01-02-2014 10:05 PM
Guys, the tech seems to be doing what he can to help. If you don't have anything to contribute other than jejune indictments of "coporate amerika" then kindly go make your own thread to vent your spleen.
01-03-2014 11:42 PM
Maybe you didn’t understand what I wrote.
I’ll try this again.
Broadcom manufactures the bluetooth radio that’s in the adapter, it supplies the chips and the drivers to R.F., Broadcom supplies the driver to R.F. Broadcom is not responsible to provide you or me with a driver only R.F.; R.F is legally required to provide one.
R.F. is/was being cheap; not supplying the driver to end users; maybe only R.F. users are affected, I dunno maybe they didn’t pay their bills or something; because the update tool from Broadcom uses SSL; it could be tied to the mac of the radio so that Broadcom could stop any R.F. user from updating your drivers. I can show you my frame captures that show that my pc sends a frame to “update.broadcom.com” and then no response. Its why unless you have the drivers in your possession or your lucky and can find another that works the only solution here is to bang on R.F. to provide a driver. It’s also why I spent just 5 minutes on the fone with t/s before they told me “take it back to the store”. If you read the board here a lot of people are having the same problem; Justin knows this too and is just like everyone else, playing the game and collecting a pay check.
Maevid I’ll ignore your impolite remarks; I understand your frustration; understand that currently I am a Network Analyst; I’ve been in IT for over 20 years and mainframes before that, I work in korp amerika and can’t stand the fact in my lifetime I’ve seen them go from being a necessary evil to being the anti-christ, or do you consider yourself a 1%’r; not likely; you shop @bb.
btw “you’re either part of the problem or part of the solution”
01-05-2014 11:08 PM
Ditto what qwerty said ...exept I only worked in IT for 18 years and only on Novell/Windows infrastructures.
I paid for a product, I expect it to work.
01-09-2014 05:54 PM
They are working on fixing the drivers right now. We were finally able to replicate the issue. The problem is a conflict with the Windows drivers. The Windows drivers do not provide full fucntionality for the device. We are working on fixing the drivers and will make them available once they clear testing.