Date: Tue, 30 Sep 1997 15:39:57 +0200 (IST) From: Eli Zaretskii To: Cesar Scarpini Rabak cc: djgpp AT delorie DOT com Subject: Re: libc functions handling of UNCs In-Reply-To: <1.5.4.32.19970930133200.006a400c@dce03.ipt.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Tue, 30 Sep 1997, Cesar Scarpini Rabak wrote: > fnsplit(argv[0], szDrive, szPath, szFile, NULL); So the real problem is that argv[0] gets a UNC from Windows 95. Actually, programs that need to use argv[0] to open files, need to be aware of this problem and translate the UNC into a d:/path name. It is a pain in the lower back, but I know of no other solution. One other problem with using argv[0] on Windows 95 is that it always gets the 8+3 alias, even if the .exe has a valid long name *and* you invoked the 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.