On the last post:
I need to extract FULLY QUALIFIED paths, not just file name.
I am OK with network drives, but can’t get the drive info for local
drives. So basically it is a problem of getting the local hard drive info
…
The comment line above the code:
"// --grab current irp stack loc., then
DeviceObject->DeviceExtension->DeviceObject to get FSDevice ptr."
is out of date and inaccurate.
As I said, the FULLY qualified name will be relative to the volume
device. This is in the device object of the volume - and not part of
the file object’s name. /TomH
-----Original Message-----
From: Eric Fowler [mailto:xxxxx@seanet.com]
Sent: Monday, February 10, 2003 5:07 PM
To: File Systems Developers
Subject: [ntfsd] Clarification …
On the last post:
I need to extract FULLY QUALIFIED paths, not just file name.
I am OK with network drives, but can’t get the drive info for local
drives. So basically it is a problem of getting the local hard drive
info
…
The comment line above the code:
"// --grab current irp stack loc., then
DeviceObject->DeviceExtension->DeviceObject to get FSDevice ptr."
is out of date and inaccurate.
You are currently subscribed to ntfsd as: xxxxx@inflectionsystems.com
To unsubscribe send a blank email to xxxxx@lists.osr.com