www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/05/05/04:11:48

Date: Tue, 5 May 1998 11:11:21 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Richard Slobod <71231 DOT 104 AT compuserve DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: fixpath problem in Novell drives.
In-Reply-To: <354e826c.6768297@news.warwick.net>
Message-ID: <Pine.SUN.3.91.980505110626.27724E-100000@is>
MIME-Version: 1.0

On Tue, 5 May 1998, Richard Slobod wrote:

> >Under Windows, yes, but on MSDOS it depends on the redirector.  Novell 
> >generally supports it (because it intercepts DOS calls ahead of DOS), but 
> >other redirectors typically don't support such names.
> 
> Actually, only Novell's old NETX clients worked that way and they
> didn't support UNC names

Not as far as I know.  It is true that only old NETX clients would grab 
the DOS interrupt, but their support of UNCs is okay.

> Novell's later DOS clients both support UNC (in addition to the Novell
> syntax) and are true redirectors.  I don't specifically know of any
> redirector-based network client that doesn't support UNC (certainly
> both Microsoft's DOS client and LANtastic support it), but I
> admittedly haven't checked every DOS network client in existence.

Actually, the later versions of Novell DOS clients are more of a problem 
here.  That's because the DOS redirector interface is actually a callback 
mechanism: DOS does all the usual work and calls the redirector only when 
it needs to perform an actual operation on a file, and the drive in 
question is marked as a networked drive.

So, when using the newer Novell clients, the support for UNCs under DOS 
should be worse, since DOS itself cannot grok names like \\SERVER\SYS\DIR.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019