From: eyal DOT ben-david AT aks DOT com
To: csrabak AT dce03 DOT ipt DOT br
cc: djgpp AT delorie DOT com
Message-ID: <42256522.006048AC.00@aks.com>
Date: Tue, 30 Sep 1997 20:14:35 +0200
Subject: Re: libc functions handling of UNCs
Mime-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Precedence: bulk




>At 15:39 30/09/97 +0200, Eli Zaretskii wrote:
>>program using that long name.  The funny thing is, this also happens for
>>native Win32 programs (so I am told).  Looks like somebody at Microsoft
>>got lazy and didn't want to differentiate between DOS and Win32 programs.
>>
Yes !.  MSVC 5 fails to print the long name.  Borland and Watcom print
argv[0] correctly.

On Tue, 30 Sep 1997, Cesar Scarpini Rabak wrote:
>Humm, your observation if correct, may mean that there is hope: if native
>Win32 programs also have this problem, but aplications like Explorer,
>Notepad, etc., are able to show in their file menus the longfilenames,
then
>there should be a documented way of doing it!
There is a Win32 API function that return the long file name. I do not know
why
it is not used also for argv[0] -- strange.

     Eyal.