Greetings.
The marketing folks have decided it is a bad idea to let customers see the
‘boot-up’ screens in our system. The hardware folks met this requirement
by blanking the display until a certain hardware bit is set by our
software once the system is up and running. All is well unless chkdsk
(autochk) runs during the boot process to repair/scan a dirty volume. The
marketing folks have now decided it is a bad idea to leave the display
blanked for too long; our customers might think the system is
broke. So, I need to enable the display while chkdsk (autochk) runs so our
customers know that the system is just doing some necessary repair work.
(It still works, don’t send it back!)
My current plan is to write two native apps, one to turn on the display
before chkdsk (autochk) runs and one to turn it off after chkdsk (autochk)
completes. I just need to know when chkdsk (autochk) is gonna run from the
first native app so I can turn on the display. So I figured I’d ask the
file system crowd how I could accomplish this.
Anyone know the native calls or Fs ioctls I can use to get this
information? I am pretty sure there must be since the XP fsutil user mode
app can display this information.
Many thanks in advance,
Dale Chermak
Philips Medical Systems
xxxxx@philips.com
Set a callback process creation callback and properly validate that the running image is autochk and enbale your display driver.
Apart from this, did your Beavis&Butthead marketing team have any other bright ideeas ? Like enabling / disabling the display at 1Hz, to make a 7899$ strobo for a christmas tree ?
----- Original Message -----
From: xxxxx@philips.com
To: File Systems Developers
Sent: Saturday, July 27, 2002 2:32 AM
Subject: [ntfsd] Retrieving Volume Dirty Flag From Native App
Greetings.
The marketing folks have decided it is a bad idea to let customers see the ‘boot-up’ screens in our system. The hardware folks met this requirement by blanking the display until a certain hardware bit is set by our software once the system is up and running. All is well unless chkdsk (autochk) runs during the boot process to repair/scan a dirty volume. The marketing folks have now decided it is a bad idea to leave the display blanked for too long; our customers might think the system is broke. So, I need to enable the display while chkdsk (autochk) runs so our customers know that the system is just doing some necessary repair work. (It still works, don’t send it back!)
My current plan is to write two native apps, one to turn on the display before chkdsk (autochk) runs and one to turn it off after chkdsk (autochk) completes. I just need to know when chkdsk (autochk) is gonna run from the first native app so I can turn on the display. So I figured I’d ask the file system crowd how I could accomplish this.
Anyone know the native calls or Fs ioctls I can use to get this information? I am pretty sure there must be since the XP fsutil user mode app can display this information.
Many thanks in advance,
Dale Chermak
Philips Medical Systems
xxxxx@philips.com
— You are currently subscribed to ntfsd as: xxxxx@rdsor.ro To unsubscribe send a blank email to %%email.unsub%%
Dale,
you wrote on Saturday, July 27, 2002, 01:32:40:
dcpc> Greetings.
dcpc> My current plan is to write two native apps, one to turn on the display
dcpc> before chkdsk (autochk) runs and one to turn it off after chkdsk (autochk)
dcpc> completes. I just need to know when chkdsk (autochk) is gonna run from the
dcpc> first native app so I can turn on the display. So I figured I’d ask the
dcpc> file system crowd how I could accomplish this.
dcpc> Anyone know the native calls or Fs ioctls I can use to get this
dcpc> information?
Check winioctl.h for FSCTL_IS_VOLUME_DIRTY.
Ralf.