[Bug 45116] TomTom MyDrive Connect needs implementation of iphlpapi.dll.NotifyAddrChange

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=45116

Hanno Meyer-Thurow <h.mth at web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #61302|0                           |1
        is obsolete|                            |
  Attachment #61303|0                           |1
        is obsolete|                            |
  Attachment #61332|0                           |1
        is obsolete|                            |

--- Comment #15 from Hanno Meyer-Thurow <h.mth at web.de> ---
Created attachment 61351
  --> https://bugs.winehq.org/attachment.cgi?id=61351
Implementation of NotifyAddrChange: build fixes for 3.7 (v5)

Added 'struct ip_async_io' to handle callback with user data. Taken from fileio
code.
Minor fixes like releasing non-acquired fd in IPHLPAPI_initmonitorhandle and
properly releasing ip_async_io instance in IPHLPAPI_apc_NotifyAddrChange.

v4: Refactored reading of netlink messages; fixes application hang. (forgot
before)
v5: pass overlapped.hEvent as async_data_t.event. Do not set event in internal
apc callback. Seems more sound this way.

With this variant application will not crash anymore, device still not
detected. 

Null pointer exception happens in mountmgr.sys:query_mount_points. My bet,
implementing KERNEL32.dll.SetVolumeMountPointW and not implementing
KERNEL32.dll.DeleteVolumeMountPointW brings inconsistency in internal mount
list. O well, seems not that hard to do. :-)

-- 
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.