X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID: <250B3114DA16D511B82C00E0094005F8055AC80A@MSGWAW11>
From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= <wojciech DOT galazka AT polkomtel DOT com DOT pl>
To: "'Eli Zaretskii'" <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Subject: RE: lfn from scratch... - network redirectors
Date: Sat, 29 Dec 2001 20:23:16 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-2"
Reply-To: djgpp-workers AT delorie DOT com


> From: Eli Zaretskii [mailto:eliz AT is DOT elta DOT co DOT il]

> > From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= 
> <wojciech DOT galazka AT polkomtel DOT com DOT pl>
> > Date: Sat, 29 Dec 2001 16:19:02 +0100
> > 
> > Ok, network redirectors ...
> > There seems to be a problem with them because there is no interface
> > to pass long file name as an argument.
> 
> They are supposed to support the LFN API via functions 71xx of Int
> 21h. 

Are you sure this is the right way?
From what I've read DOS communicates with network redirecors through int
2fh,ax=11xxh only
so it seems natural to extend redirector capabilities expanding int 2fh,
ax=11xxh ...

> If they don't, they are simply a kind of DOS, and so they are
> limited in the length of the file name exactly like DOS is.  In fact,
> 2Fh/AH=11h is supposed to be called with file names after they are
> normalized by a call to 21h/AH=60h, so the names are already
> truncated to 8+3 limits.

And I want a redirector to see long filename instead of that 8+3 one ..

> The problem I was thinking about was with a network redirector that
> does support an LFN API, but one of the remote drive does not.  Such
> a situation could utterly confuse DJGPP programs.

I've never seen: 
* a real mode redirector that supports LFN API
* a network redirector that does support an LFN API, but one of the remote
drive does not
(actually a redirector should know if a remote drive can store long file
names or not)

We can safely ignore the situation you described when a redirecto does not
provide LFN API (thus no one can call redirector
directly)

> > Perhaps we could work around this by extending the 
> > int 2F, AH=11 interface with LFN calls ?
> 
> What software will support these extended calls on the other end of
> the network?
> 

The same software that provides LFN API to DOS (a TSR). 
The TSR would serve LFN calls to local drives on its own and would invoke
int 2fh, ax=11xxh for remote drives and cd-roms.
The int 2fh calls would in turn be served by redirectors.