Bluetooth Sync breaks after Hibernation

From a cold boot or restart, syncing my SMT 5600 with my Toshiba M200 TPC
over Bluetooth works just fine. However, coming out of hibernation, it no
longer works; both devices report the COM Port is no longer available.

Returning from hibernation and looking at the Device Manager, it reports
that Network adapters > Bluetooth Device (Personal Area Network) is not
working propertly because "Windows cannot load the drivers required for this
device. (Code 31)". Disabling and re-enabling the BT radio has no
effect--the same status is reported. One may think this could simply be a
fault of the Toshiba BT Monitor, or just the native MS BT stack. However, if
I follow this process:

1) Kill wcescomm.exe
2) Disable BT radio
3) Enable BT radio

At this point, the BT Dev (PAN) loads correctly. If I then

4) start ActiveSync,

it will sync properly. At no point before this will ActiveSync work
properly; it will always report a non-available COM port (and annoyingly
launch into the new partnership wizard! Augh! Is this by design?!).

Anyway, this sequence of events leads me to believe that the only malefactor
here is ActiveSync, but I've been wrong before.

I'm not even hoping for a fix at this point--I just want to know that there
is at least one other person out there who has had this problem, or make MS
aware that at least one person is having it. Going in and out of hibernation
often is important for keeping the Tablet PC useful to me.

For the record:
Toshiba M200 Tablet PC
Toshiba Integrated Bluetooth

native Microsoft BT Stack
Toshiba Bluetooth Monitor (specifically "Toshiba Integrated Bluetooth 2")
ActiveSync 3.8.0 (Build 5004)

Thanks so much for any help.

(P.S. - Also, while I'm at it, I just want to complain that WMP10 *does* see
my SMT 5600 as a portable device, which is handy...just so long as I use USB,
and not Bluetooth. Sigh.)

Hi,
Hibernation can break ActiveSync because ActiveSync does not expect the
drivers are not available after resuming. I do not know of a fix or a
workaround for it.

BTW an easier way to end wcescomm.exe is to use Killsync from
www.pocketpcfaq.com/applications/

--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

"Michael Jacobs" <Michael > wrote in message
news:5DF61658-6347-4B70-AB5D-...
> From a cold boot or restart, syncing my SMT 5600 with my Toshiba M200 TPC
> over Bluetooth works just fine. However, coming out of hibernation, it no
> longer works; both devices report the COM Port is no longer available.
>
> Returning from hibernation and looking at the Device Manager, it reports
> that Network adapters > Bluetooth Device (Personal Area Network) is not
> working propertly because "Windows cannot load the drivers required for
> this
> device. (Code 31)". Disabling and re-enabling the BT radio has no
> effect--the same status is reported. One may think this could simply be a
> fault of the Toshiba BT Monitor, or just the native MS BT stack. However,
> if
> I follow this process:
>
> 1) Kill wcescomm.exe
> 2) Disable BT radio
> 3) Enable BT radio
>
> At this point, the BT Dev (PAN) loads correctly. If I then
>
> 4) start ActiveSync,
>
> it will sync properly. At no point before this will ActiveSync work
> properly; it will always report a non-available COM port (and annoyingly
> launch into the new partnership wizard! Augh! Is this by design?!).
>
> Anyway, this sequence of events leads me to believe that the only
> malefactor
> here is ActiveSync, but I've been wrong before.
>
> I'm not even hoping for a fix at this point--I just want to know that
> there
> is at least one other person out there who has had this problem, or make
> MS
> aware that at least one person is having it. Going in and out of
> hibernation
> often is important for keeping the Tablet PC useful to me.
>
> For the record:
> Toshiba M200 Tablet PC
> Toshiba Integrated Bluetooth
>
> native Microsoft BT Stack
> Toshiba Bluetooth Monitor (specifically "Toshiba Integrated Bluetooth 2")
> ActiveSync 3.8.0 (Build 5004)
>
> Thanks so much for any help.
>
> (P.S. - Also, while I'm at it, I just want to complain that WMP10 *does*
> see
> my SMT 5600 as a portable device, which is handy...just so long as I use
> USB,
> and not Bluetooth. Sigh.)