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

2004-05-06 Thread Krishna Murthy
Thanks Alexandre, Krishna -Original Message- From: Alexandre Julliard [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 9:00 PM To: Krishna Murthy Cc: [EMAIL PROTECTED] Subject: Re: WNetGetConnection(): Fix for incorrect drive name and remote name and Krishna Murthy <[EM

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

2004-05-06 Thread Alexandre Julliard
Krishna Murthy <[EMAIL PROTECTED]> writes: > 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

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

2004-05-06 Thread Alexandre Julliard
Krishna Murthy <[EMAIL PROTECTED]> 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? -

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

2004-05-06 Thread Krishna Murthy
Wednesday, May 05, 2004 12:05 PM To: Krishna Murthy Cc: [EMAIL PROTECTED] Subject: Re: WNetGetConnection(): Fix for incorrect drive name and remote name and Krishna Murthy <[EMAIL PROTECTED]> writes: > - Long Description: > 1. WNetGetConnectionA calls WNetGetConnectionW without con

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

2004-05-05 Thread Alexandre Julliard
Krishna Murthy <[EMAIL PROTECTED]> 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 > WNet