Fix Private Profile Functions for .INI in Current Directory

[Alexandre Julliard]

Robert Shearman <R.J.Shearman at warwick.ac.uk> writes:

> As per MSDN (1), if a relative path to a file is passed in to the
> {Get,Write}PrivateProfile* functions then the current directory is tried
> first, and then if that fails the Windows directory is used (for both
> the opening and creating cases).

I don't see any evidence that this is true, and MSDN says "If the
lpFileName parameter does not contain a full path and file name for
the file, WritePrivateProfileString searches the Windows directory for
the file". Do you have a test case showing that the current behavior
is wrong?

-- 
Alexandre Julliard
julliard at winehq.org