I have been trying to pair my windows mobile device with Mercedes Bluetooth unit. For some reason, the Mercedes Bluetooth unit could see the phone, but wasn't successful paring with it. I've been looking around internet for a while now trying to find a solution to the this issue, and have finally found a solution. This is just a combination of instructions from various  sources and I’ve put them together.

It's actually probably not the Bluetooth devices fault. Bluetooth devices identify themselves as a certain type of unit. For example, headsets as headsets, phones as phones. Interestingly, Windows mobile units identify themselves as PDA's not phones.  This need to be changed for the Bluetooth unit to recognize the phone. But this needs editing the registry of the Windows Mobile phone.

If you're not comfortable with editing the registry, don't do it. It can and will mess up your phone if done wrong. 

1. download and install CeReg editor (http://ceregeditor.mdsoft.pl/) on a Desktop PC. Its a simple registry editor for windows mobile.

2. Connect the windows mobile unit using USB and Open the registry using CeReg.

3. Edit the following value

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS]
"COD"=dword:52020C (hex)

4. Change the value to 1048852 (Decimal)

5. Reset the phone

6. If the device is already paired, delete the pairing, and start from scratch. This time it should work as the accessory is seeing the device as a phone, not a PDA.

Microsoft has released Security Advisory 977981.  It details vulnerabilities in Internet Explorer 6 and 7 on various operating systems.  The advisory does not provide any patches or new versions at this point, but does provide several recommendations for mitigation.

The Windows SDK for Windows 7 and .NET Framework 3.5 SP1 provides the documentation, samples, header files, libraries, and tools (including C++ compilers) that you need to develop applications to run on Windows 7 and the .NET Framework 3.5 SP1. To build and run .NET Framework applications, you must have the corresponding version of the .NET Framework installed. This SDK is compatible with Visual Studio® 2008, including Visual Studio Express Editions, which are available free of charge.

Please see the Release Notes for the full list of supported platforms, compilers, and Visual Studio versions and any late breaking issues. For detailed information about the content in this SDK, including a description of new content, please see the Getting Started section in the documentation.

Download at Microsoft Download

This beta is available only to customers in the United States, Israel (English only), People's Republic of China (Simplified Chinese only) and Brazil (Brazilian Portuguese only).Please visit the more information page to learn more about system requirements, our End User License Agreement and other important information.

To get the beta, just click here or on the button on the top of this page. This will take you to Microsoft Connect where you'll answer a few questions and then be able to download the Security Essentials beta.

http://www.microsoft.com/security_essentials/

Network Monitor 3.3 is a protocol analyzer. It allows you to capture network traffic, view and analyze it. Version 3.3 is an update and replaces Network Monitor 3.2. Network Monitor 3.x is a complete overhaul of the previous Network Monitor 2.x version.

The Network Monitor core engine has been decoupled from the parser set. To install the full Network Monitor 3.3 product:

• Run the setup.exe for the platform you are installing.
• You will be prompted first to install the core engine. Follow the installation directions. Make sure you close existing instances of netmon.exe, nmcap.exe and any running NMAPI applications.
• Next you will be prompted to install the parser package. Follow the installation directions.

To uninstall the full Network Monitor 3.3 product:

• Go to Add/Remove Programs in Control Panel
• Uninstall both Microsoft Network Monitor 3.3 and Microsoft Network Monitor: Microsoft Parsers 3.3.

Download : Microsoft Downloads