Hi,
Thanks for clearing my dilema of setting the LastAccess to the currentttime
using KeQuerySystemTime, when it is set to FFFFFFFF.
But we receive correct values in the Filebasicinformation buffer in the
MyFsdSetFileInformationAtCleanup call. I am simply returning STATUS_SUCCESS
for Filebasicinformation class in this call.
Is it OK if we handle my FSD specific time conversions for FILETIMES in
MyFsdSetFileInformationAtCleanup call ?
Thanks and regards,
Rukmini
-----Original Message-----
From: Rick Winter [mailto:xxxxx@veritas.com]
Sent: Thursday, May 10, 2001 7:20 PM
To: File Systems Developers
Subject: [ntfsd] Re: FileBasicInformation and LastAccessTime
A value of FFFFFFFF for any of the file times tells the file system
to not change that file time for this handle. For example, an application
wants to open the file and read it without changing the last access time
(like a virus scanner). It would open the handle and set the file times to
0xFFFFFFFF with that handle. It could then read the file and close it and
the file times would not change. This was implemented this way for Windows
2000 as a shortcut since so many applications had to get the times, do their
reads, and then set the original times back.
If you see 0xFFFFFFFF in any of the time fields in
MyFSDSetFileInformation you should ignore it and simply pass it on to the
next driver. Changing the value will break applications that are trying to
preserve the file times.
-----Original Message-----
From: Kotikalapudi, Rukmini [mailto:xxxxx@india.ingr.com]
Sent: Thursday, May 10, 2001 6:52 AM
To: File Systems Developers
Subject: [ntfsd] Re: FileBasicInformation and LastAccessTime
Hi,
Thanks for the info!.
We are facing this problem in MyFSDSetFileInformation call for
FileBasicInformation is received, when I right click on a file with no file
extension or if the extension type is not associated with any application to
open with on my remote mount.
If we do not handle the FFFFFFFF values and return, The File properties
LastAccessTime does not get changed.
This may be happening because we are not handling the file times in
MyFsdSetFileInformationAtCleanup call for FileBasicInformation.
We noticed that when the “MyFsdSetFileInformationAtCleanup” is called for
FileBasicInformation type,
the LastAccessTime is properly initialized. I am not handling the file times
in this call and simply returning STATUS_SUCCESS.
This was not causing any problem on NT, may be because I was setting
correct values in my MyFSDSetFileInformation call itself.
DO we have to handle the file times in the
MyFsdSetFileInformationAtCleanup call also?
Thanks and regards,
Rukmini
-----Original Message-----
From: xxxxx@tjsys.co.jp [mailto:xxxxx@tjsys.co.jp]
Sent: Thursday, May 10, 2001 8:06 AM
To: File Systems Developers
Subject: [ntfsd] Re: FileBasicInformation and LastAccessTime
Hi,
I had a similar problem while working on my RDR for Win2000.
When I opened a VC++6 project on the remote, MyFsdSetBasicInformation was
called with all the time field of the FILE_BASIC_INFORMATION structure
filled with 0xffffffffffffffff.
I found that the caller of this was Ole32!_GetClassFile. This routine
calls ntoskrnl!_NtSetInformationFile with filling -1 to the time field.
I had no idea what this mean, but I guessed it does not really want to
set file time but do some other special functions depend on specific FSD.
So, I just ignored it.
Thanks,
Tsuyoshi
>
>Hi everyone,
>
> We have an FSD that needs to set the LastAccessTime of a File
>stream to our FSD specific time format. We were converting the
>LastAccessTime of the FILE_BASIC_INFORMATION
>structure(IrpContext->CurrentIrp->AssociatedIrp.SystemBuffer) received,
When
>the FileBasicInformation type request is made through Set file information
>calls.
>
>This LastAccessTime is initialized to a valid time in the
>FILE_BASIC_INFORMATION structure received on Windows NT. The
LastChangeTime,
>CreationTime are set to zero values.
>
>But on the Windows 2000 and Windows XP, we have noticed that
>the LastAccessTime in the FILE_BASIC_INFORMATION structure recieved from
>the RDBSS
>is always initialized to 0xffffffff. The LastChangeTime, CreationTime are
>also set to 0xffffffff.
>
>Has anyone faced similar kind of problem ?.
>
>Is there any other alternative way of getting the valid LastAccessTime of
>the file stream in the FileBasicInformation request in the Set
Information
>Call.
>
>Regards,
>Rukmini
>
You are currently subscribed to ntfsd as: xxxxx@india.ingr.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@veritas.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@india.ingr.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com