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

[Krishna Murthy]

We have used the attached sample to test this. The patch I have sent earlier
had two fixes; Fix-1 (wide character string) and Fix-2 (Remote Path Name).
Basically we have Team Developer product which generates the runtime win32
applications. These generated application are behaving differently on Win32
and Wine.

Please find attached the sample win32 application that demonstrates the
behavior of WNetGetConnection API. 
1. The sample has hard coded the network drive name as "N:\" for this
demonstration.
Please map a new network drive  named "N:\" before running  this sample
program.
2. In Wine, apply the fix-1 (wide character issue) before applying fix-2 to
see the different behavior.
3. Invoke Menu item Test->GetRemotePath 

Thanks,
Krishna

-----Original Message-----
From: Alexandre Julliard [mailto:julliard at winehq.org] 
Sent: Thursday, May 06, 2004 11:57 AM
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:

> We did some analysis and come to conclusion that QueryDosDevice is a 
> better choice than GetVolumeInformation.

What sort of analysis?  Do you have an app that needs that, and if so why is
returning a Unix path better?  What does the app do with it?

--
Alexandre Julliard
julliard at winehq.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: WNetGetConnection.zip
Type: application/octet-stream
Size: 12399 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20040506/55bf310e/WNetGetConnection.obj