Re[2]: Isolation driver FO fields copy doubt.

NTFSD
1

As Rod pointed out, this is one of the fields that you must manage.

Pete

–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295

------ Original Message ------
From: xxxxx@mauroleggieri.com
To: “Windows File Systems Devs Interest List”
Sent: 4/3/2017 10:56:54 AM
Subject: RE:[ntfsd] Isolation driver FO fields copy doubt.

>If I don’t copy CurrentByteOffset back and forth, IFS tests fails :frowning:
>
>—
>NTFSD is sponsored by OSR
>
>
>MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>software drivers!
>Details at http:
>
>To unsubscribe, visit the List Server section of OSR Online at
>http:</http:></http:>

2

Thanks Rod and Peter for clarifying.

Is there another field I have to worry about?

Kind regards,
Mauro.

3

> Is there another field I have to worry about?

Being flippant “Yes, but you will need to find out for yourself”. As I said
earlier this is non documented and you really just need to suck it and see.
But to start with you probably want to call one of the File Share
arbitration functions to set up the
Read/Write/Delete/ReadShare/WriteShare/DeleteShare flags.

4

> If I don’t copy CurrentByteOffset back and forth, IFS tests fails :frowning:

Don’t copy it. Maintain it. See FAT for how to do that in
FILE_SET_POSITION and PostWrite