application data path

NTFSD
1

Hi all,

I starting my minifilter driver at boot time , let me know is there any possibilities to access file in “application data” folder.

I m trying but failed.

Thanks

2

its a FS minifilter, right? which means FS is already mounted. So you should be able to read it, what is the error you are getting & what path have you specified for “application data”

3

Hi Aditya,

Let me know is there any Kernel Level API to get path of “application data” folder.

Thanks

4

This question is inherently buggy. There is no single application data path as it is a per-user setting. The setting itself may not even be available until the user logs on (consider roaming profiles). It may be pointed at a remote server that is inaccessible without the user’s credentials.

You need to rethink what you’re trying to do here.

  • S

-----Original Message-----
From: xxxxx@yahoo.com
Sent: Tuesday, October 26, 2010 23:41
To: Windows File Systems Devs Interest List
Subject: RE:[ntfsd] application data path

Hi Aditya,

Let me know is there any Kernel Level API to get path of “application data” folder.

Thanks

—
NTFSD is sponsored by OSR

For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

5

> I starting my minifilter driver at boot time , let me know is there any possibilities to access file in

“application data” folder.

Zero possibilities.

Use SYSTEM registry instead, or delay till PnP volume arrival notification.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

6

> Let me know is there any Kernel Level API to get path of “application data” folder.

No for sure.

The kernel just plain has no knowledge of what of the folders is “application data”.

More so, this folder is user-specific, so, probably you should delay this stuff till user logon.

Another approach: on install, get this folder location and write the path to the SYSTEM registry, the driver will just pick this path and go.

Also consider using \System Volume Information\GuidOfYourOwn instead, which is the suggested way of keeping driver’s per-volume data. For instance, VolSnap keeps its old-per-sector-data store files this way, and other out-of-the-box MS’s drivers are also such.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

7

One more thing to add would be that for a boot start minifilter, the
earliest (and best time) to safely access the volume is in the InstanceSetup
callback for the boot volume. Filter manager guarantees that instance setup
will be called when it detects the first operation on the volume so you are
guaranteed to not miss anything interesting, and the volume is already
mounted at that point. So don’t try to do this in DriverEntry but rather in
the InstanceSetup callback.

Thanks,
Alex.