[Bug 7711] TomTom Home can not detect TomTom devices

http://bugs.winehq.org/show_bug.cgi?id=7711


Ken Sharp <kennybobs(a)o2.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |1.2.0

Alexandre Julliard <julliard(a)winehq.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|1.2.0                       |---

Michiel Salters <msalters(a)xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msalters(a)xs4all.nl




--- Comment #69 from Ken Sharp <kennybobs(a)o2.co.uk>  2009-08-13 13:22:11 ---
USB support on the 1.2 release plan --> Nominating for 1.2

--- Comment #70 from Alexandre Julliard <julliard(a)winehq.org>  2009-08-13 13:41:59 ---
USB support is not planned for 1.2 at this point.

--- Comment #71 from Michiel Salters <msalters(a)xs4all.nl>  2009-08-20 04:52:34 ---
(In reply to comment #68)
> (From update of attachment 10196 [details])
> Communication is at the USB level, not the file mount level.

Sorry, that is incorrect. Yes, TomTom HOME will load ActiveSync if that is
available, but that is to support TomTom Navigator (their Windows Mobile
product). Their own PND line, the ones running Linux communicate only via USB
Mass Storage.

The main Wine problem with HOME seems to be recognition of the device. I've
noted that the different HOME versions behave differently. Let's focus on
2.0-2.7 for the moment, the HOME 1.x releases are obsolete. But the 2.x
releases too are not all identical when it comes to spotting the device. Let me
state what I can see for HOME 2.7

The only thing that doesn't go through the file system is retrieving the USB
descriptors (In particular vendor 1390, and serial number). TomTom doesn't use
the USB product field; all devices are 0001. Instead the serial number prefix
is unique. According to <http://www.tomtom.com/products/maps/select.php> its
first two characters determine the model. To retrieve those fields HOME uses
the registry. 

The registry keys HOME reads depends on the OS. HOME always needs
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_1390&Pid_0001. The
subkey here is USB's iSerial field. On XP, HOME also needs a ParentIdPrefix
field. It can find that in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR\Disk&Ven_TomTom&Prod_ONE_IQ_Routes\<iSerial>
 but that Prod_ part will probably depend on the product descriptor of your
particular device. The ParentIdPrefix can then be found in the appropriate
value in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices (note: these are really in
UTF-16, even though they have type binary).

On Vista, HOME only needs the HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices. The
values of these keys on Vista are now just device instance Ids (as mentioned in
comment 40 above).

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.