Guy Albertelli galbe...@neo.rr.com writes:
On Thu, 2009-03-26 at 10:08 +0100, Alexandre Julliard wrote:
Guy Albertelli galbe...@neo.rr.com writes:
1. The initial problem was that the CreateFile above would not
successfully translate the volume id to the associated Unix file. #3/10
fixed
On Thu, 2009-03-26 at 10:08 +0100, Alexandre Julliard wrote:
Guy Albertelli galbe...@neo.rr.com writes:
1. The initial problem was that the CreateFile above would not
successfully translate the volume id to the associated Unix file. #3/10
fixed that.
That should go in mountmgr, it
Guy Albertelli galbe...@neo.rr.com writes:
1. The initial problem was that the CreateFile above would not
successfully translate the volume id to the associated Unix file. #3/10
fixed that.
That should go in mountmgr, it already creates the volume symlinks and
manages the devices. What is
Am Donnerstag, den 26.03.2009, 10:08 +0100 schrieb Alexandre Julliard:
2. The FILE_NO_INTERMEDIATE_BUFFER flag seemed to require the O_DIRECT
flag during the Unix open. This was proven by having standard Linux code
access the device. #1/10 and #9/10 fixed this.
I don't see why you'd need
On Tue, 2009-03-24 at 11:32 +0100, Alexandre Julliard wrote:
Guy Albertelli galbe...@neo.rr.com writes:
1/10 server: Implement FILE_NO_INTERMEDIATE_BUFFERING with O_DIRECT
2/10 kernel32/tests: First test for CreateFile on NT unique volume name
3/10 ntdll: Implement conversion of NT
Guy Albertelli galbe...@neo.rr.com writes:
1/10 server: Implement FILE_NO_INTERMEDIATE_BUFFERING with O_DIRECT
2/10 kernel32/tests: First test for CreateFile on NT unique volume name
3/10 ntdll: Implement conversion of NT unique volume name to unix file
name
4/10 ntdll: Implement
