Installing CSR Bluetooth Device Driver and Bluetooth Headset on Windows 7 Windows Vista Windows Server 2.This article describes how to install and enable Bluetooth headset profile HSP on both 3.Microsoft Windows 7, Microsoft Windows Vista, and Microsoft Windows Server 2.It also provides CSR Bluetooth device drivers for select OEMs and aftermarket Bluetooth dongles.Due to the fact that Windows doesnt support Bluetooth headset profile HSP out of the box, if you want to use a Bluetooth headset with your adapter, youll need a little creative workaround to add the headset profile to the default Microsoft stack.Download either of the x.CSR Bluetooth driver and extract its contents to a folder.When you try to pair your headset to your computer, Windows will ask for drivers for the headset since it doesnt find the appropriate headset profile.Point Windows to the folder where you have extracted the CSR drivers to make it work.Make sure you go into the device in the Bluetooth Devices panel and check off the boxes for unwanted profiles.Use IE for best view http http page missing microsoft.InformationWeek. com News, analysis and research for business technology professionals, plus peertopeer knowledge sharing.Engage with our community.Windows_Vista_Home_Premium.jpg' alt='Microsoft Windows Vista Ultimate X86 Sp1 Integrated March 2009 O' title='Microsoft Windows Vista Ultimate X86 Sp1 Integrated March 2009 O' />But first, do you have a BT radio installed Read more Bluetooth Device Driver Installation.Not taking PCI PCIe Bluetooth devices into account at all, newer versions of Windows recognize a wide range of USB Bluetooth devices out of the box.But if your Bluetooth radio USB device is not recognized, you can try the Bluetooth Filter Driver Bth.Filt 1. 0. 0. 3. Cambridge Silicon Radio Bluetooth Filter Driver 1.Download Links. Download CSR Bluetooth device driver version 1.Windows 7 x. 86 3.Windows Vista x. 86 3.Windows Server 2.Download CSR Bluetooth device driver version 1.Windows 7 x. 64 6.Windows Vista x. 64 6.Windows Server 2.Archive File Listing.Bth. Filt. inf, Bth.Filt. sys, Bth. Filt.Extracted from Dell Wireless 3.Bluetooth Internal Module drivers R1.R1. 42. 18. 3. Also included in Dell Wireless 3.Module with Bluetooth 2.EDR drivers R1. 55.R1. 55. 46. 3. Supported Devices.Manufacturer. Device Name.Hardware IDAlps. Alps Integrated Bluetooth Device.USBVID0. 44. E PID3.Alps Bluetooth USB Adapter.USBVID0. 44. E PID3.Belkin. Belkin Bluetooth Adapter.USBVID0. 50. D PID0.Belkin Bluetooth Adapter.USBVID0. 50. D PID0.ISSC USB Bluetooth Device.USBVID1. 13. 1 PID1.Microsoft Windows Vista Ultimate X86 Sp1 Integrated March 2009 O' title='Microsoft Windows Vista Ultimate X86 Sp1 Integrated March 2009 O' />REV0.Brain Boxes. Brain Boxes USB Bluetooth Adapter BL 5.USBVID0. 5D1 PID0.Cambridge Silicon Radio.Generic Bluetooth Radio.USBVID0. A1. 2 PID0.CSR Nanosira. USBVID0.A1. 2 PID0. CSR Nanosira WHQL Reference Radio.USBVID0. A1. 2 PID0.CSR Nanosira Multimedia.USBVID0. A1. 2 PID0.CSR Nanosira Multimedia WHQL Reference Radio.USBVID0. A1. 2 PID0.Dell. Dell True. Mobile Bluetooth Module.USBVID4. 13. C PID8.Dell Wireless 3. 50 Bluetooth Module.USBVID4. 13. C PID8.Dell Wireless 3. 50 Bluetooth Module.USBVID4. 13. C PID8.Dell Wireless 3. 60 Bluetooth Module.USBVID4. 13. C PID8.Hewlett Packard. HP Integrated Bluetooth module.USBVID0. 49. F PID0.HP nx. 70. 00. USBVID0.F PID0. 08. REV1.IBMBluetooth Ultra.Port Module from IBMUSBVID0.BF PID0. 31. IBM Integrated Bluetooth.USBVID0. 4BF PID0.IBM Integrated Bluetooth IIUSBVID1.PID0. 44. 1IBM Integrated Bluetooth IIIUSBVID1.PID2. 44. 1IBM Integrated Bluetooth IVUSBVID0.A5. C PID2. EThink.Pad Bluetooth with Enhanced Data Rate.USBVID0. A5. C PID2.Motion Computing.Motion Computing USB Bluetooth Device.USBVID1. 0AB PID1.Motion Computing USB Bluetooth Device.USBVID1. 0AB PID1.Sony. USB Bluetooth Device.USBVID0. 44. E PID3.USB Bluetooth Device.USBVID0. 44. E PID3.Sony Bluetooth USB Adapter.USBVID0. 44. E PID3.USB Bluetooth Device.USBVID0. 44. E PID3.TDKTDK Bluetooth USB Adapter.USBVID0. 4BF PID0.TDK Bluetooth USB Adaptor.USBVID0. 4BF PID0.Toshiba. Toshiba Integrated Bluetooth.USBVID0. 93. 0 PID0.REV1. 35. 0Toshiba Integrated Bluetooth 2.USBVID0. 93. 0 PID0.Toshiba Integrated Bluetooth 3.USBVID0. 93. 0 PID0.Toshiba Bluetooth Adapter.USBVID0. 93. 0 PID0.Toshiba Bluetooth Adapter.USBVID0. 93. 0 PID0.Toshiba Bluetooth Adapter.USBVID0. 93. 0 PID0.Bluetooth Profile Driver Installation.In order to use Bluetooth technology, a device must be compatible with the subset of Bluetooth profiles necessary to use the desired services.The way a device uses Bluetooth technology depends on its profile capabilities, such as Advanced Audio Distribution Profile A2.DP, AudioVideo Remote Control Profile AVRCP, Hands Free Profile HFP, Headset Profile HSP, Basic Imaging Profile BIP, Hard Copy Cable Replacement Profile HCRP, Video Distribution Profile VDP, etc.For every Bluetooth profile to function, you need to install its appropriate drivers, like for example using Cambridge Silicon Radio Bluetooth Driver Pack.Which version of CSR drivers would best suit me Well, that depends Depending on the vendor ID of the Bluetooth radio device youve installed, newer driver packs might refuse to work.CSR drivers from version 4 onward 4.CSR based Bluetooth devices.Users say on non CSR radios, v.Windows updategives the Bluetooth Peripheral Device Bluetooth Stereo Audio a failed driver icon.In this case, you need to uninstall the update and perhaps forcibly install downgrade to version 3 or earlier drivers.Whether or no, Id advise against installing any optional driver update once your device is working desirably.Coming up next When downgrading, beware of a service name conflict Though it might sound dumb, there comes a time when downgrading is inevitable, and along comes its complications.Read more Possible Service Name Conflict after a CSR Driver Upgrade Downgrade.CSR has changed the A2.DP driver, yet they used the same service name bthav.This causes a conflict, obviously.To switch from version 3.HKEYLOCALMACHINESYSTEMCurrent.Control. Setservicesbthav in the Registry beforehand and reboot.To swith back downgrade, which I prefer, delete HKEYLOCALMACHINESYSTEMCurrent.Control. Setservicescsra.Registry beforehand and reboot.CAUTION To be safe, in cases like this, at least always first export these keys.That said, I have not seen any problems in this particular case.With 5 buggy releases 4.Now, Bth. Av. inf version 5.Id really like to have a baseball bat involved word with them Cambridge Silicon Radio Bluetooth Driver Pack 5.Download Links. Download CSR Bluetooth driver version 5.Windows 7 x. 86 3.Windows Vista x. 86 3.Windows Server 2.Download CSR Bluetooth driver version 5.Windows 7 x. 64 6.Windows Vista x. 64 6.Windows Server 2.Archive File Listing.Bth. Audio. HF. inf, Bth.Audio. HF. sys, Bth.Audio. HF. cat, HFGService.HFGServicePS. dll 5.Bth. Av. inf, Bth.Av. sys, Bth. Av.Bth. Avrcp. inf, Bth.Avrcp. sys, Bth. Avrcp.Csr. Profiles. inf, Csr.Profiles. cat 5. 0.Cambridge Silicon Radio Bluetooth Driver Pack 5.Download Links. Download CSR Bluetooth driver version 5.Windows 7 x. 86 3.Windows Vista x. 86 3.Windows Server 2.Download CSR Bluetooth driver version 5.Windows 7 x. 64 6.Windows Vista x. 64 6.Windows Server 2.Archive File Listing.Bth. Audio. HF. inf, Bth.Audio. HF. sys, Bth.Audio. HF. cat, HFGService.HFGServicePS. dll 5.Bth. Av. inf, Bth.Av. sys, Bth. Av.Bth. Avrcp. inf, Bth.Avrcp. sys, Bth. Avrcp.Csr. Profiles. inf, Csr.Profiles. cat 5. 0.Extracted from Fujitsu Technology Solutions Bluetooth driver files FTSCSRBluetoothstack5.Windows 7 x. 86 FTSCSRBluetoothstack5.Windows 7 x. 64. Cambridge Silicon Radio Bluetooth Driver Pack 5.Download Links. Download CSR Bluetooth driver version 5.Windows 7 x. 86 3.Windows Vista x. 86 3.Windows Server 2.Download CSR Bluetooth driver version 5.Windows 7 x. 64 6.Windows Vista x. 64 6.Windows Server 2.Archive File Listing.Bth. Audio. HF. inf, Bth.Audio. HF. sys, Bth.Audio. HF. cat, HFGService.HFGServicePS. dll 5.Bth. Av. inf, Bth.Av. sys, Bth. Av.Bth. Avrcp. inf, Bth.Avrcp. sys, Bth. Avrcp.Csr. Profiles. inf, Csr.Profiles. cat 5. 0.Extracted from Fujitsu Technology Solutions Bluetooth driver files FTSCSRBluetoothstack5.Windows 7 x. 86 FTSCSRBluetoothstack5.Windows 7 x. 64. Although versioned 5.Bth. Avrcp. inf, Csr.Profiles. inf, and Csr.Profiles. cat that are identical to 5.This version has also fixed Finnish language setup crash while installing the package.Cambridge Silicon Radio Bluetooth Driver Pack 5.Fix problems with Visual Studio F5 debugging of ASP.NET applications on IIS7 Vista UPDATE 482.Ive collected the various how tos and gotchas about using Visual Studio 2.Visual Studio 2. 00.IIS 7. 0 applications into two detailed articles Using Visual Studio 2.IIS 7. 0. Using Visual Studio 2.IIS 7. 0. Be sure to check them out for detailed info on working with both local and remote IIS 7.Windows Vista SP1 and Windows Server 2.RTM, doing local and remote debugging, and other stuff.UPDATE 62. A Visual Studio patch that fixes the Visual Studio F5 debugging of IIS7 applications on Windows Vista Home Premium and above has been released This patch solves the An authentication error occurred while communicating with the web server.Please see Help for assistance., and Debugging failed because integrated Windows authentication is not enabled.Please see Help for assistance errors, that until now had to be worked around using the instructions below.This patch also enables customers using Windows Vista Home Premium customers to use Visual Studio F5 debugging, who were not able to use this feature at all previously because Windows Authentication was not available on Windows Vista Home Premium.You can download the patch from connect here Download.Also see the KB article 9.Thank you for your patience so far, and I hope that this resolves your problems.If not, please let me know.Thanks,MikeA number of people have been reporting problems when trying to debug their ASP.NET applications on Windows Vista with Visual Studio 2.F5 debugging support.There are a handful of posts about trying to get this to work in various ways most of which are missing key information needed to eallyget it to work.I am going to try and provide you with step by step instructions below, and explain the several tradeoffs that you may need to make along the way.A little note about the purpose of Visual Studios F5 debugging support Its designed to help you attach the debugger to the worker process running your ASP.NET application. You can always manually attach the debugger via the Menu Tools Attach to Process option, assuming you know what instance of W3.WP. EXE worker process on your server the application is running in.The F5 debugging mode figures this out for you, and starts a convinient browser window for you to play around with the app.Other than that, it is the same as debugging it manually.If you are debugging from a remote machine, you will need to run the Visual Studio Debugging Monitor on the remote machine, and open the firewall so that Visual Studio can connect to the debugger msvsmon.Then, you can still attach directly via the Attach to Process dialog, by specifying the servers machine name.So, the bottom line is, if you know which process you need to debug, you dont need F5 debugging to debug ASP.NET apps. With that in mind, here is what it takes to get the convinient F5 Debugging working on Vista NOTE Be sure to get the Visual Studio 2.SP1 update if you are running Visual Studio 2.Vista. This update fixes a number of incompatibilities you may otherwise hit.If you have issues installing SP1, please be sure to review Heath Stewarts blog entry at http blogs.Run Visual Studio 2.Administrator. Unfortunately, Visual Studio 2.SP1 still doesnt support the required elevation functionality to be able to do debugging when run by a LUA user.I hope it will very soon in the meantime, in order to enable debugging, you need to run it as Administrator 2 Install required IIS components.IIS7 in Vista and Longhorn server has been completely modularized to reduce the security surface area and improve performance, and installs a pretty small set of features by default.In order to enable F5 debugging, you will need at minimum the following components ASP.NETWindows Authentication Module Provides support for Windows authentication with NTLM and KerberousMetabase compatibility layer Provides support for legacy IIS configuration APIs used by existing software to manage IIS.Note that this is required to connect to your ASP.NET application from Visual Studio, even before you attempt debugging.Install them from Control Panel Programs Turn Windows Features on and off After doing this, you may get the following error if you attempt to debug Always press No.This message is incorrect, and is due to a change in how versioning is done for ASP.NET applications on IIS7 that is not being properly handled by Visual Studio 2.Enable Windows Authentication for your ASP.NET application. Visual Studio 2.ASP. NET application to have Windows Authentication enabled.This requirement also exists for Windows XP Windows Server 2.To enable Windows Authentication, open the IIS Manager administration tool by running Start type inetmgr in the search box, navigate to your application, choose the Authentication tab, and Enable Windows Authentication Note If you have Anonymous Forms authentication enabled for your application, leave it on.Enable your ASP. NET application to provide debugging auto attach support.At this point, if you press F5 and try to attach to your application, you may either see nothing or get the following error This is the dreaded error that frazzles most people.The unfortunate fact is, there is a bug in ASP.NET Integrated mode the default ASP.NET mode for IIS7 that prevents authentication from taking place correctly for the debug auto attach feature.The bug manifests only in the following case ASP.NET application is running in an application pool using Integrated mode Default, and.ASP. NET application has global.Authenticate. Request not default so, Begin.Request, Post. Begin.Request, and in some cases early in Authenticate.Request. The following workarounds are avaialble Remove global.This is a farily bad option because they are the ones you want to debug a lot of the time.Move the application to Classic mode.This may be acceptable, but not ideal especially if you are developing an application that takes advantage of Integrated mode specific features.Even if you are not, you may sometime in the future so running your application in Integrated mode will help you make sure you are well positioned for it.Use the debug assistant module below.This is a hack I wrote that temporarily enables the debugging auto attach to work correctly in integrated mode.But, since you are not debugging your Vista site while its live on the internet right For how to move your application to Classic mode, you can consult one of the existing blog posts about this issue for example, Rajivs post here.Enable the Debugging Assistant to enable F5 Debugging in Integrated mode.Like I said, dont put this module on a production system.But, its entirely safe to use it for your development test machine to help with F5 debugging.Just make sure that you turn off debugging related stuff, and remove this module before deploying in production as a general deployment practice.Hopefully I havent scared you too much, since the module doesnt really do anything major it just allows and tweaks the debug attach request to enable ASP. Audi A4 B6 Haynes Pdf Manuals . NET debug attach to work.It does however disable authorization for requests mapped to the Debug.Handler below although the handler will require an authenticated Windows user.Here is how to set this up on your machine Download the Debug Assistant module disclaimer This module is not provided by Microsoft, and is not supported in any way.NOTE If you are running on a 6.OS, download the 6.Debug Assistant. It will replace the 3.Unzip to a local directory.Right click on install.Run as AdministratorAdd the following in your applications web.Server lt modules lt addnamedebugassistant lt modules lt handlers lt addnameDebug.HandlerpathDebug.Attach. aspxverbDEBUGtypeSystem.Web. Http. Debug.Handler lt handlers lt system.Server lt system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |