Yeah, it would be a little non-deterministic anyhow – might depend on the
speed of the disk, number of volumes, number of other drivers loaded, etc.,
etc.
Regardless, thanks for the thought.
Ken
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of MM
Sent: Friday, January 27, 2006 6:09 AM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] Reboot since installed?
well, on second thought - nevermind, I think the time difference would
be significantly smaller than what I initially thought
it would be.
MM wrote:
Crazy idea here, don’t know if this would work… I think you were
on the right track with system time.From what I understand when a boot start driver is loaded, it’s driver
entry routine is called immediately. If the
FSFD is in the correct load order group, it will get loaded and
initialize before the file system. Now, using a global
variable to store the time the driver entry fired, vs when your volume
attach routine happens (which would only be after the FS is
initialized) there
should be a 10-20 second gap there (thus indicating to the driver’s
code a boot probably occurred).Comparing this method to loading a filter while the system is running
using for example, the time between Driver_Entry
> and the volume attach routine would usually be under 1 sec. Thus,
> calculating this time gap and storing it in a var would indicate
> a boot start vs a fltmc load.
>
> Not 100%, but in theory I think it might work (most of the time)…
> Kinda a dynamic approach.
>
> As stated, still kinda new to this driver witting thing, so if this
> approach wouldn’t work at all, please do help me learn a little by
> explaining why…
>
> Hope I conveyed that right,
> Matt
>
>
>
> Ken Cross wrote:
>
>> NTFSD Folk:
>>
>> How can a driver determine if the system has been rebooted since it was
>> installed?
>>
>> There are a few operations that my driver needs to know that the
>> system has
>> been rebooted since the driver was installed, i.e., that the driver
>> started
>> before any applications have.
>>
>> I thought to use the time the driver started relative to the system boot
>> time, but that’s rather non-deterministic, e.g., within 30 seconds of
>> system
>> boot? 60 seconds? 5 minutes?
>>
>> (BTW, where is the system boot time kept in the kernel? I can’t find
>> it.)
>>
>> Ken
>>
>>
>>
>> —
>> Questions? First check the IFS FAQ at
>> https://www.osronline.com/article.cfm?id=17
>>
>> You are currently subscribed to ntfsd as: xxxxx@comcast.net
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@comcast.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@comcast.net
To unsubscribe send a blank email to xxxxx@lists.osr.com