http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #86 from Hans Leidekker hans@meelstraat.net 2011-02-12 15:00:24 CST --- (In reply to comment #85)
Well, Renault cars don't come with long USB cords. It's kind of logical that they use another mechanism for updates (SD card). But a ONE can and is detected via USB. See my earlier post, HOME is spelunking the USB bits of the registry.
Yes, I found an alternative workaround that involves copying registry entries:
0. Attach the device to a Windows machine.
1. Navigate to this key: HKLM\System\CurrentControlSet\Control\DeviceClasses{53f56307-b6bf-11d0-94f2-00a0c91efb8b} and find the subkey that has TomTom somewhere in the name. Export it.
2. Navigate to this key: HKLM\System\CurrentControlSet\Enum\USBSTOR and find the subkey that has TomTom somewhere in the name. Export it.
3. Export this key: HKLM\SYSTEM\MountedDevices and edit the reg file to contain only the value that corresponds to your TomTom device. In my case this is \DosDevices\D:
4. Import the registry keys in Wine.
It's looking up a device identifier through setupapi and tries to match it to the value found under the MountedDevices key for a particular (removable) drive.
On Wine the relevant setupapi functions are implemented but the registry keys they query are not populated yet when a new device is attached. And the values under the MountedDevices key are currently filled with the targets of the drive symlinks under ~/.wine/dosdevices instead of device identifiers.