From:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id:	<200005071011.MAA00558@father.ludd.luth.se>
Subject:	Re: Idea: \\host\share\file -> /dev/net/host/share/file
In-Reply-To:	<200005062130.RAA07149@indy.delorie.com> from Eli Zaretskii at "May 6, 2000 05:30:09 pm"
To:	djgpp-workers AT delorie DOT com
Date:	Sun, 7 May 2000 12:11:26 +0200 (MET DST)
X-Mailer:	ELM [version 2.4ME+ PL54 (25)]
MIME-Version:	1.0
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

According to Eli Zaretskii:
> > From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
> > Date: Sat, 6 May 2000 12:11:56 +0200 (MET DST)
> > 
> > How easy would it be to add the UNC functionality by mapping
> > \\host\share\file to /dev/net/host/share/file and back?
> 
> On plain DOS or on Windows?
> 
> If the latter, then you don't have to do anything, except to take care
> to pass the \\host\share\file UNC to the functions of Int 21h, and
> Windows will do the rest.  The problem is that some of the library
> functions do destructive things to such UNCs, but that's all you need
> to take care of to get the UNCs supported.

Perhaps you misunderstand me? The idea is to use
/dev/net/... internally to avoid this destructiveness, and map
\\host\ to /dev/net/host on entry to the C library and then map it
back to \\host just before calling *DOZE.

> If you want to support UNCs on DOS, then mapping to /dev/net/whatever
> will not really help, since some machinery needs to communicate to the
> network redirector so that it understands the /dev/net/ stuff.

Again these /dev/net wouldn't be seen by the network redirector. Or
are you saying that WINDOZE already understands /dev/net!?

I was primarily thinking of WINDOZE, but if it'd work on DOZE too it'd
be a bonus.


Right,

							MartinS

- Raw text -