Fires before the filter attaches to a newly-mounted filesystem volume.
type TBeforeFilterAttachToVolumeEvent = procedure ( Sender: TObject; const VolumeName: String; var SkipVolume: Boolean; var ResultCode: Integer ) of Object;
property OnBeforeFilterAttachToVolume: TBeforeFilterAttachToVolumeEvent read FOnBeforeFilterAttachToVolume write FOnBeforeFilterAttachToVolume;
This event fires before the filter attaches to the newly-mounted filesystem volume specified by VolumeName. Please refer to the FireVolumeEvents property for more information.
The VolumeName parameter's value is always an NT native format in this event (unlike the other volume-related events, listed below, where its format depends on the ResolveNtDeviceToDriveLetter configuration setting). It is therefore recommended that applications add volume-specific rules, if desired, during the AfterFilterAttachToVolume event rather than this one. Applications can obtain additional information about a volume by retrieving its GUID using the GetVolumeGUID method, and then using that GUID to call various Windows API functions.
The SkipVolume parameter specifies whether the component's system driver should skip the specified volume (i.e., not attach the filter to it). Setting this parameter to True will cause all filesystem operations that target to volume to be completely ignored by the component's system driver, and will also prevent any of the following events from firing for the volume:
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.
This event is fired synchronously; please refer to the Event Types topic for more information.
Applications must be aware that this event fires as a direct response to a filesystem state change (mount or unmount). Various system components or third-party actors are able to perform supplementary filesystem mounting and unmounting during main unmount operations (Volume Service is one of such components). This can cause seemingly excessive events to be fired, and sometimes they can even be fired out of order (such as two *Attach or *Detach events fired in a row).