[Bug 7711] tomtom home does not find the device go 901

[wine-bugs at winehq.org]

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


Hans Leidekker <hans at it.vu.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |kernel32




--- Comment #32 from Hans Leidekker <hans at it.vu.nl>  2008-01-09 14:49:16 ---
This is the interesting part from your relay log:

0042:Call user32.SetWindowsHookExW(00000004,0189c1b0,00000000,00000042)
0042:Ret  user32.SetWindowsHookExW() retval=00040064
0042:Call KERNEL32.FindFirstVolumeW(0034e8ec,00000104)
0042:fixme:volume:FindFirstVolumeW (0x34e8ec, 260), stub!
0042:Ret  KERNEL32.FindFirstVolumeW() retval=ffffffff
0042:Call KERNEL32.FindVolumeClose(ffffffff)
0042:fixme:volume:FindVolumeClose (0xffffffff), stub!
0042:Ret  KERNEL32.FindVolumeClose() retval=00000000

Meanwhile Alexandre has implemented the volume APIs, which promted me to
try TomTom HOME again. This is what it looks like now:

0011:Ret  user32.SetWindowsHookExW() retval=00010036
0011:Call KERNEL32.FindFirstVolumeW(0034fa40,00000104)
0011:Ret  KERNEL32.FindFirstVolumeW() retval=001557e0
0011:Call KERNEL32.GetDriveTypeW(0034fa40
L"\\\\?\\Volume{00000000-0000-0000-0000-000000000043}\\")
0011:Ret  KERNEL32.GetDriveTypeW() retval=00000000
0011:Call KERNEL32.FindNextVolumeW(001557e0,0034fa40,00000104)
0011:Ret  KERNEL32.FindNextVolumeW() retval=00000001
0011:Call KERNEL32.GetDriveTypeW(0034fa40
L"\\\\?\\Volume{00000000-0000-0000-0000-00000000005a}\\")
0011:Ret  KERNEL32.GetDriveTypeW() retval=00000000
0011:Call KERNEL32.FindNextVolumeW(001557e0,0034fa40,00000104)
0011:Ret  KERNEL32.FindNextVolumeW() retval=00000000
0011:Call KERNEL32.FindVolumeClose(001557e0)
0011:Ret  KERNEL32.FindVolumeClose() retval=00000001

So it finds volumes now and wants to know what type they are. That fails
because GetDriveType on a volume name is not implemented yet (I tried, it
works on Windows). The preceding SetWindowsHookEx call presumably serves
to monitor changes to the drives configuration.

Alexander, since you have one of these devices, can you try again
with current git and post the relevant snippet from a +relay log here?


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.