Re: Bluetooth and WSAECONNREFUSED (10061)
- From: "Uncle Marvo" <paul.r@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Mar 2007 07:44:48 +0100
Comments...
"Greg Scott [MS]" <gregsco@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OIciHclbHHA.1400@xxxxxxxxxxxxxxxxxxxxxxx
It is not a known issue that you can only connect to a peer device twoI am surprised, but possibly not as surprised as you are!
times from CE. I'm not as familiar with the XP BT stack but I'd be
surprised if they had a bug this bad.
Many of the Bluetooth profiles on your device (e.g. Hands Free Profile)I assumed this which is why I am surprised. I have done loads of work using
communicate over winsock as well and we have tested multiple reconnections
without any issues.
Winsock ever since it worked "properly" in Win98SE. Never had a problem
before, not one I couldn't code round, anyway.
Unfortunately I don't have any ideas to help you debug this. Have youYes, I have been writing serial interfaces for something like 35 years. Not
tried connecting between two PPCs to see if the issue reproduces? Or two
PCs?
all on Windows, obviously :-)
Regarding the issues with COM ports, I'm not sure what issue you areI bet you a dollar I'm not!
seeing. These are not known issues so my only theory is that you are
incorrectly using these APIs.
You may want to download the Windows CE Platform Builder evaluation
version and look at the following sample code:
public\common\oak\drivers\bluetooth\sample\*
public\common\sdk\samples\bluetooth\*
There are a ton of samples here, some of which use winsock/COM ports.
Looked at these, they don't work on my device. I suspect that the device
itself is not good, there is a MS bug report on this at
http://support.microsoft.com/kb/916279 which also surprised me, and I
suspect the fix is not implemented in my device.
Interestingly, it states "This problem occurs because the internal counters
in the device are out of sync. These internal counters are not reset until
you restart the device by using the soft boot method". It should read "...
because the internal conters in the Microsoft Software are out of sync ..."
:-)
Good luck!Thanks for looking, Greg.
--
Greg Scott
Software Design Engineer, Windows CE
Microsoft Corporation
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no
rights.
_____________________________________________________________
"Uncle Marvo" <paul.r@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:56iar1F2817reU1@xxxxxxxxxxxxxxxxxxxxx
And further to my last rant ...
I am now using a serial bluetooth connection from XP (a dongle) and a
Vodafone 1640.
It works one way (from PC to PDA), not the other. The PDA won't open a
serial with CreateFile most of the time (usually error 55), then when it
does, when you WriteData to it, the XP box doesn't see it. It *must* be
going down a big hole somewhere.
And if you turn the Bluetooth OFF while it's running, ReadFile returns
non-zero and GetLastError() isn't set. And WriteFile on the XP box just
hangs.
Wonderful.
Which device should I throw away, the XP one or the Vodafone 1640 (I
suspect the latter).
Anyone had any experience of BT devices in Mobile that actually work?
Money no object.
Many thanks - Unc
.
- References:
- Bluetooth and WSAECONNREFUSED (10061)
- From: Uncle Marvo
- Re: Bluetooth and WSAECONNREFUSED (10061)
- From: Uncle Marvo
- Re: Bluetooth and WSAECONNREFUSED (10061)
- From: Uncle Marvo
- Re: Bluetooth and WSAECONNREFUSED (10061)
- From: Greg Scott [MS]
- Bluetooth and WSAECONNREFUSED (10061)
- Prev by Date: File System filter on Windows 5.0 Pocket PC Emulator
- Next by Date: probelm to create new project with VS 2005
- Previous by thread: Re: Bluetooth and WSAECONNREFUSED (10061)
- Next by thread: Re: Help - registering directshow filter in Pocket PC device
- Index(es):
Relevant Pages
|