Path: nntp.gmd.de!Germany.EU.net!howland.reston.ans.net!agate!msunews!
harbinger.cc.monash.edu.au!newshost.anu.edu.au!newshost!tridge
From: tri...@cs.cs.anu.edu.au (Andrew.Tridgell)
Newsgroups: comp.protocols.smb
Subject: Samba and Win95 long filenames - working
Date: 27 Mar 1995 13:14:47 GMT
Organization: Australian National University
Lines: 36
Distribution: world
Message-ID: < TRIDGE.95Mar27231447@cs.cs.anu.edu.au>
Reply-To: Andrew.Tridg...@anu.edu.au
NNTP-Posting-Host: 150.203.160.29

I've had a bit of success with the NT LM 0.12 and NT LANMAN 1.0
protocols. 

This means long filenames in Win95 now seem to work. It's probably very
buggy as the code is only a couple of hours old, but if you want to
try it then grab 1.9.09alpha1.

This might also fix some things for NT. It might give us the "dual
names" that are needed for 16 bit apps to work properly. I haven't
tested with NT (I haven't been able to kick my wife off her machine
all afternoon) so it's also possible that I've broken things badly
instead. 

The dual names do work under Win95. This means old dos apps see
mangled 8.3 names whereas Win95 apps see long names. It's interesting
that the file manager (winfile) is an "old" app and sees 8.3
names. The "explorer" and the "network neighborhood" see long names.

So, could I get a few Win95 and NT testers?

Note that you will either have to use "protocol = NT1" or no "protocol
=" line at all, otherwise you won't see the new protocol. (I've
changed the default max protocol to NT1)

Oh yes, I also updated smbclient so it can see long filenames on Win95
as well.

Andrew

PS: The date and time handling in the code for the new protocol
doesn't seem that great. We'll need to improve the code in that area.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Andrew Tridgell                 Dept. of Computer Science
Andrew.Tridg...@anu.edu.au      Australian National University (x5691)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-