X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f From: "Tim Van Holder" To: "'Eli Zaretskii'" , "'Charles Sandmann'" Cc: Subject: Re: UNC examples Date: Fri, 28 Dec 2001 13:41:05 +0100 Message-ID: <000001c18f9c$eab38bf0$d47d76d5@zastaixp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-reply-to: <7826-Fri28Dec2001132338+0200-eliz@is.elta.co.il> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > The file utils cat program built with djgpp does this too. So both > > cat \\cws333\d$\djgpp\setup.bat and cat > z:\\cws333\d$\djgpp\setup.bat > > work. > > This can still be the shell feature. Are you sure the file name gets > into the program intact, with the bogus drive letter? Yep. Just tried a little argv printing proglet, and it shows the \:\\foo\bar filename as passed. The fact that the UNC seems to get evaluated (a fairly long delay running it the first time) is probably a "feature" command.com shares with its 32-bit brother cmd.exe. We can probably use this, as long as we're sure never to pass such a bogus name to a program that doesn't support it (i.e. any non-DJGPP program other than cmd.exe/command.com).