Juan Lang juan_lang@yahoo.com writes:
File I/O, fine. But how about named pipes? Mailslots? They are implemented with nearly the same SMBs, and belong in kernel32 or ntdll. netapi32 needs 'em too, for these two functions.
They should go in the kernel too. Anything that does I/O needs to be there, because it can't be done reliably in the client process, and it can't be done efficiently in the wine server.
Okay, I'll put it into a static lib.
You shouldn't need that. Just forget about the kernel32 part, it needs to be redone anyway.