Results 1 to 5 of 5

Thread: Windows Mobile and Vista 64 bit

  1. #1
    Join Date
    Aug 2008
    Posts
    3

    Windows Mobile and Vista 64 bit

    I have an AT&T Tilt. I have upgraded 3 pc to Vista 64 bit - I didn't need to sync with any of them for awhile after conversion since I used Activesync. Now that I want to install some software, I would like to get this to work - i've tried much of the scenarios that i've been able to find
    downloaded 64bit WMDC, unistalled the other first, etc... nothing seems to work -
    1. does anyone sync via wmdc and a vista 64 bit? If you do, do you also have a Tilt? If so, how did you do it?

  2. #2
    Join Date
    Dec 2007
    Posts
    2,291
    How To Sync via Bluetooth with WMDC
    Windows Mobile Device Center (WMDC) (aka ActiveSync) in Windows Vista supports synchronization between PDA and PC via Bluetooth connection. However, occasionally for odd reason such as your computer or Pocket PC is running on WidComm Bluetooth driver stack, the Bluetooth sync simply doesn’t work by simply selecting ‘Bluetooth’ in ‘Connection Settings’ in WMDC’s ‘Allow connection to one of the following’ option.

    When a mobile device such as Pocket PC Phone detects and connects to a desktop or notebook computer via Bluetooth, it cannot determine if there’s any ActiveSync or WMDC service running in the background in the PC. To make thing worse, WMDC has dropped the ability to manually set the listening port for Bluetooth COM port. The older ActiveSync has this feature to support manual configuration of Bluetooth listening COM port.

    The following registry hack provides the solution to unable to sync via Bluetooth with WMDC problem in Windows Vista. The registry hack has to be applied on desktop PC or laptop, and not the mobile device.

    • Run Registry Editor (type regedit in Start Search and press Enter). Confirm any UAC dialog.
    • Navigate to the following registry key:


    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows CE Services

    • In the right pane, locate the value name “SerialPort”. Modify the value data from the default value of “Bluetooth or “Infrared” to “COM4&Prime, where COM4 is the virtual COM port associated to your Bluetooth incoming COM port. If your PC uses different COM port number, then choose the right COM port as the value (e.g. COM5, COM6 etc).
    • Exit Registry Editor.

    Once the registry is set, WMDC will bind to a Bluetooth virtual COM port as incoming listening port instead of the generic Bluetooth name, which may not work for non-standard driver stack.

    Source:→ MydigitalLife

  3. #3
    Join Date
    Oct 2004
    Posts
    1,342
    Have you tried going into Settings/Connections/Connections/USB to PC and unticking the box? This forces a normal USB connection rather than an IP based one, and sometimes works better.

  4. #4
    Join Date
    Aug 2008
    Posts
    3
    I would like sync via USB - not bluetooth - a couple of my PCs do not have BT.

    Quote Originally Posted by einstein_007 View Post
    How To Sync via Bluetooth with WMDC
    Windows Mobile Device Center (WMDC) (aka ActiveSync) in Windows Vista supports synchronization between PDA and PC via Bluetooth connection. However, occasionally for odd reason such as your computer or Pocket PC is running on WidComm Bluetooth driver stack, the Bluetooth sync simply doesn’t work by simply selecting ‘Bluetooth’ in ‘Connection Settings’ in WMDC’s ‘Allow connection to one of the following’ option.

    When a mobile device such as Pocket PC Phone detects and connects to a desktop or notebook computer via Bluetooth, it cannot determine if there’s any ActiveSync or WMDC service running in the background in the PC. To make thing worse, WMDC has dropped the ability to manually set the listening port for Bluetooth COM port. The older ActiveSync has this feature to support manual configuration of Bluetooth listening COM port.

    The following registry hack provides the solution to unable to sync via Bluetooth with WMDC problem in Windows Vista. The registry hack has to be applied on desktop PC or laptop, and not the mobile device.

    • Run Registry Editor (type regedit in Start Search and press Enter). Confirm any UAC dialog.
    • Navigate to the following registry key:


    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows CE Services

    • In the right pane, locate the value name “SerialPort”. Modify the value data from the default value of “Bluetooth or “Infrared” to “COM4&Prime, where COM4 is the virtual COM port associated to your Bluetooth incoming COM port. If your PC uses different COM port number, then choose the right COM port as the value (e.g. COM5, COM6 etc).
    • Exit Registry Editor.

    Once the registry is set, WMDC will bind to a Bluetooth virtual COM port as incoming listening port instead of the generic Bluetooth name, which may not work for non-standard driver stack.

    Source:→ MydigitalLife

  5. #5
    Join Date
    Aug 2008
    Posts
    3
    Quote Originally Posted by VICEMAN View Post
    Have you tried going into Settings/Connections/Connections/USB to PC and unticking the box? This forces a normal USB connection rather than an IP based one, and sometimes works better.
    Yes I did - the Tilt does authenticate/recognize the USB connection, but WMDC does not recognize the connection.

Similar Threads

  1. Replies: 3
    Last Post: 14-01-2014, 11:17 AM
  2. Can windows mobile 5.0 sync with vista
    By roumieh2000 in forum Portable Devices
    Replies: 3
    Last Post: 26-08-2009, 09:53 AM
  3. Vista Bluetooth sync with Windows Mobile problems
    By sivaranjan in forum Windows Vista Network
    Replies: 2
    Last Post: 29-12-2008, 01:14 PM
  4. Windows Mobile 6.1 on Sprint’s Samsung ACE Mobile Phone
    By kattman in forum Portable Devices
    Replies: 1
    Last Post: 17-10-2008, 02:35 PM
  5. Replies: 0
    Last Post: 19-09-2008, 01:40 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,525,878.18101 seconds with 16 queries