Juan Lang wrote:
--- Eric Pouech <[EMAIL PROTECTED]> wrote:
I'm in the process of rewriting the SMB code to
use
winsock name lookup and socket calls without
NetBIOS
first, and to fall back to NetBIOS (using the
Netbios() function) second if that fails.
beware that you cannot directly call wsock3
--- Eric Pouech <[EMAIL PROTECTED]> wrote:
> first of all, most code dealing with file/pipe
> opening will be moved
> from kernel32 to ntdll (at least the core)
Okay.
> moreover, the SMB code (currently) is more a proof
> of concept than a
> full implementation of SMB (using SAMBA if possible
>
--- Eric Pouech <[EMAIL PROTECTED]> wrote:
> > I'm in the process of rewriting the SMB code to
> use
> > winsock name lookup and socket calls without
> NetBIOS
> > first, and to fall back to NetBIOS (using the
> > Netbios() function) second if that fails.
> beware that you cannot directly call wsoc
At least US corps don't controll all EU politics, as it happens in the US.
I'm in the process of rewriting the SMB code to use
winsock name lookup and socket calls without NetBIOS
first, and to fall back to NetBIOS (using the
Netbios() function) second if that fails.
beware that you cannot directly call wsock32 functions (nor netapi32)
from ntdll.
I'd like to expose som
Juan Lang wrote:
Any advice on where to put code that needs to be
shared by multiple dlls? I'm tweaking the SMB code
right now, and I'd like to reuse it in netapi32 (to
implement some of the Net functions) as in kernel32
(for CreateFile and CreateNamedPipe).
I'm thinking a new directory in libs (l
Any advice on where to put code that needs to be
shared by multiple dlls? I'm tweaking the SMB code
right now, and I'd like to reuse it in netapi32 (to
implement some of the Net functions) as in kernel32
(for CreateFile and CreateNamedPipe).
I'm thinking a new directory in libs (libs/smb). Any
b
