WNetGetConnection(): Fix for incorrect drive name and remote name and

[Krishna Murthy]

We did some analysis and come to conclusion that QueryDosDevice is a better
choice than GetVolumeInformation. As you indicated, since network path of
the wine's network drive is not pointing to a real network path, neither of
them going to return the remote path of the network drive. Since
'QueryDosDevice' retrieves a local path for the network drive (from wine
config file), this will be a better choice than GetVolumeInformation. 

Please find attached diff taken with diff -u

Thanks,
Krishna

-----Original Message-----
From: Alexandre Julliard [mailto:julliard at winehq.org] 
Sent: Wednesday, May 05, 2004 12:05 PM
To: Krishna Murthy
Cc: wine-devel at winehq.org
Subject: Re: WNetGetConnection(): Fix for incorrect drive name and remote
name and

Krishna Murthy <Krishna.Murthy at guptaworldwide.com> writes:

> - Long Description:
> 1. WNetGetConnectionA calls WNetGetConnectionW without converting 
> single character string "drive name" to wide character string. Fix is 
> to convert the single character string "drive name" to wide character 
> before calling WNetGetConnectionW.
> 2. WNetGetConnectionW() returns drive's label instead of remote name. 
> Fix is to call QueryDosDeviceW instead of GetVolumeInformationW

It's not clear to me that QueryDosDeviceW is a better choice, neither of
them is going to return a valid remote name anyway. What does your app need
to do with the remote name?

And BTW please send diff -u patches.

--
Alexandre Julliard
julliard at winehq.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: WNetGetConnection.patch.diff
Type: application/octet-stream
Size: 1248 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20040506/1c6df8fe/WNetGetConnection.patch.obj