Hi,
We have some special weirdness happening with Samba and windows XP here.
Background:
We are wanting to install a third party product passlogix, V-GO single
sign on product on windows
(http://www.passlogix.com), which authenticates against a windows
server. Basically it uses the windows
guy:I had purchased a ntifs kit.Now I am developping a NFS software in the kit.This software have a Smb server and some win2000 server nodes which are the smb clients.The Raid can be accessed by all win2000 server nodes.My software can working in good manner,but it have some errors.One of them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can anyone comment on this?
On Tue, 15 Oct 2002, Louis-David Mitterrand wrote:
Upon upgrading from 2.2.5 to 3.0alpha20 on Debian unstable, filenames
with accented characters (ie: éàî etc.) became unreadable. For example
in W2K a filename
Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can anyone comment on this?
On Tue, 15 Oct 2002, Louis-David Mitterrand wrote:
Upon upgrading from 2.2.5 to 3.0alpha20 on Debian unstable, filenames
with accented characters (ie: éàî etc.) became unreadable.
Microsoft have documented all the DOS error codes at :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes.asp
Plus here's the docs on the internal (NTDLL.DLL) API they use to
convert from NT_STATUS to DOS error codes.
On Wed, Oct 16, 2002 at 11:33:45PM +, [EMAIL PROTECTED] wrote:
Microsoft have documented all the DOS error codes at :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes.asp
Note that if you turn off Javascript (always a good idea) you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Everyone,
I am glad to say that 2.2.6 is out and is the last planned 2.2 release.
I know many people have been working on Samba 3.0 for several months
now. Now we can all focus on 3.0. Thanks to everyone who helped
out in the past 4 months to get
