|
Posted by Jamie on May 7, 2006, 8:32 am
Please log in for more thread options
> Hopefully you didn't lose anything else you were using. The MS BT setup is
> generally much less complete than those that are supplied with Dongles. If
> you aren't wanting something unique, not a problem.
>
> --
> Sven
> MVP - Mobile Devices
>> Thanks for your response. This is how I was able to resolve the issue.
>>
>> When I initially installed the bluetooth dongle, the system did not
>> recognize it, so installed it from the CD which came with the device,
>> which
>> installed the Toschiba Bluetooth stack, rendoring any Microsoft suggested
>> configuration options & methods unavailable. The Toschiba software not
>> being
>> flexible in configuring ports. The Toschiba bluetooth dongle and the
>> software
>> are sold under the COMPUSA brand.
>>
>> This being my first bluetooth experience and thinking that the Toschiba
>> driver software was overriding any OS settings and configuration applets,
>> I
>> uninstalled the Toschiba driver software and tried different methods of
>> installing drivers for the device. The system would not recognize the
>> device.
>> When I tried plugging the bluetooth dongle into a different USB2.0 hub,
>> the
>> system suddenly recognized it and installed the Microsoft Generic
>> Bluetooth
>> Radio drivers. Why it wouldn't do it on the other hub/port, I do not
>> know.
>> All USB2.0 hubs and ports use the same generic
>> MS provided drivers.
>>
>> In conclusion, with the MS generic drivers I was able to configure the
>> settings and establish a connection using ActiveSync.
>>
>> Bluetooth was working well with the manufacturer drivers. All
>> systems and devices were communicating.
>>
>> The only thing not working or communicating was MS ActiveSync.
>>
>>
>> "Sven" wrote:
>>
>>> You need to find somewhere in the BT manager on the desktop, some way to
>>> change the virtual serial port that is assigned. That varies by BT
>>> implementation, so you'd need somebody with a similar Toshiba BT setup
>>> to
>>> help there. Has nothing to do with the ports on the SP itself. What
>>> happens
>>> is when you say to sync via BT on the phone, it sends a BT signal to the
>>> PC
>>> that says it wants to use a serial profile. That serial profile is
>>> kicked
>>> off using the port specified in the BT manager control panel on the PC.
>>> If
>>> AS is listening for activity on that same serial port, by selecting it
>>> in
>>> the AS connection screen, AS will then connect. You gotta change the BT
>>> serial port value on the PC.
>>>
>>> --
>>> Sven
>>> MVP - Mobile Devices
>>> > Open ActiveSync on the MDA and click Menu->Connect Via Bluetooth
>>> >
>>> >> I'm setting up a new Tmobile MDA SmartPhone with Windows Mobile 5.0
>>> >>
>>> >> I downloaded and installed the latest ActiveSync software, version
>>> >> 4.1, on my windows XP Pro/SP2. The desktop bluetooth device is a
>>> >> USB2.0 dongle from Toshiba. The wife's bluetooth cellphone connects
>>> >> to
>>> >> it too and does its thing as it should.
>>> >>
>>> >> XP and CE have no apparant problems connecting to each other. They
>>> >> find each other immediately, I enter the pin in CE and a window pops
>>> >> up on XP requesting the pin. I enter it and all seems fine.
>>> >>
>>> >> Problem:
>>> >> ActiveSync can not find the device. It lists all of the ports and
>>> >> COM6
>>> >> &
>>> >> COM7 are showing available. I also created COM6 & COM7 ports on the
>>> >> bluetooth
>>> >> device. Still nothing. I read all of the documentation and found
>>> >> nothing.
>>> >> XP establishes the connection using COM40, instructions state
>>> >> somewhere that it has to be less then COM20. I can not find any
>>> >> options to establish the connection using a defined port. I've
>>> >> tinkered with all of the options on XP and the device and Nothing.
>>> >>
>>> >> I do not even know if this is related to the problem.
>>> >>
>>> >> ActiveSync works fine via USB, but hey, this is wireless!
>>> >>
>>> >> Any suggestions.
>>> >>
>>> >
>>> >
>>>
>>>
>>>
>
>
| 
XML Sitemap