Message-ID:	<01FD6EC775C6D4119CDF0090273F74A4FD6B0E@emwatent02.meters.com.au>
From:	"da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
To:	"'opendos AT delorie DOT com'" <opendos AT delorie DOT com>
Subject:	RE: SMB with DOS (was: LFN API stuff via M$ Client?)
Date:	Wed, 18 Jun 2003 10:35:59 +1000
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)
Reply-To:	opendos AT delorie DOT com

Hi Stuart.

Well, it's been a few years since we installed this SMB stuff, however
as I recall, we first used the M$ Client installation program (probably
"install.exe" or "setup.exe"), which did most of the work, then played
around with "protocol.ini" and/or "system.ini" for one or two settings
that weren't accessible via the installation/configuration program. We
never cared to make the DOS machines "visible" from Windoze ones,
just vice versa (I think it may be possible, but requires even more
memory).

I will have a look for some further details, such as relevant "config.sys"
and "autoexec.bat" entries, also the batch files we use to log-in/out.
In the meantime, you may find "www.jacco2.dds.nl/samba/dos.html"
a useful starting point ...

Joe.

> -----Original Message-----
> From:	Cox, Stuart SRM:EX [SMTP:Stuart DOT Cox AT gems1 DOT gov DOT bc DOT ca]
> Sent:	Wednesday, June 18, 2003 2:00 AM
> To:	'opendos AT delorie DOT com'
> Subject:	RE: LFN API stuff via M$ Client?
> 
> Joe,
> 
> I've an 8 node Lantastic network that is slowly aging.  I went that route
> because of a contractor's recommendation of Lantastic rather than
> Microsoft,
> and his recommendation has worked well for me for the past decade or so.
> 
> This whole thing (the network) works well and I'd like to not "fix" it so
> that it no longer works.  You know how computer tinkering can be.
> 
> Still, I'd like to add an older machine or two to the network and go the
> SMB
> route.  What .EXEs, .BATs, config and autoexec settings, drivers and all
> that stuff do I need to put these two machines onto the network so that
> the
> newest Windows only boxes will be able to see them?  I've QEMM and know
> how
> to allocate upper memory stuff and that sort of thing.
> 
> Can you give me the quick and dirty rundown, please?
> 
> Stu Cox
> 
> -----Original Message-----
> From: da Silva, Joe [mailto:Joe DOT daSilva AT emailmetering DOT com]
> Sent: Wednesday, June 11, 2003 2:10 AM
> To: 'opendos'
> Subject: LFN API stuff via M$ Client?
> 
> 
> OK, I've tried to find this information via the Web and Ralf Brown's
> interrupt list, but no luck so far (perhaps because I don't understand
> what I'm looking at ;-). Perhaps someone here can "point me in the
> right direction" ... ?
> 
> I was wondering if there was any sort of API provided by the M$ Client
> for DOS redirector (or whatever), that would allow a DOS application
> to access LFN information from an NT (SMB) network drive?
> 
> We have a number of DR-DOS machines connected via an SMB network
> to a bunch of NT/W2K file servers. They have the usual M$ NDIS drivers,
> TCP/IP stack and M$ Client for DOS software, which is usually run in
> "basic" mode to conserve conventional memory, but is sometimes run in
> "full" mode, for access to the Exchange e-mail server.
> 
> I have read on the Web that WFW 3.11 (which we don't have or use, BTW)
> was able to display LFN information for NT (SMB) network drives, which
> suggests such capability might be possible under DOS too, although I
> haven't been able to confirm this or figure out how.
> 
> If it's possible, I want to be able to write an application to do a
> directory
> listing of a network drive, displaying long file names. If that works,
> perhaps
> later such network capability could then be added to the DOSLFN TSR,
> so that DR-DOS 7.03 could provide similar LFN capabilities for network
> drives as does the Windoze32 DOS Box ...
> 
> Joe.

- Raw text -