«

Hi,

is there a way, to set a ntfs volumes "dirty" flag without
the fsutil.exe tool. I want to integrate this functionality of
setting a dirty flag on a volume into my application.Where
and what do i have to modify on the drive/registry to enforce
a drive check after a system reboot. Is this applicable to
other drives like FAT(32). I think it should be, as far as i know
from fsutil.exe.


TIA

Best regards

Kerem Gümrükcü

I reverse engineered fsutil.exe for you (Windows Server 2003)
Your mileage may vary. I'm not responsible if your computer is turned
into cheese.

Sample code:

--- snip ---
/* Undocumented volume management control code */
#define FSCTL_SET_DIRTY_BIT 0x90030

DWORD bytesReturned = 0x00;

HANDLE hVol = CreateFile(
_T("\\\\.\\I:"),
GENERIC_WRITE
FILE_SHARE_READ | FILE_SHARE_WRITE,
0,
OPEN_EXISTING,
FILE_ATTRIBUTE_NORMAL,
0);

BOOL bitSet = DeviceIoControl(
hVol,
FSCTL_SET_DIRTY_BIT,
0x00,
0x00,
0x00,
0x00,
&bytesReturned,
0);

if( bitSet )
printf( _T("dirty bit set.\n") );

--- snip ---


- Rafael

Kerem Gümrükcü wrote:
> Hi,
>
> is there a way, to set a ntfs volumes "dirty" flag without
> the fsutil.exe tool. I want to integrate this functionality of
> setting a dirty flag on a volume into my application.Where
> and what do i have to modify on the drive/registry to enforce
> a drive check after a system reboot. Is this applicable to
> other drives like FAT(32). I think it should be, as far as i know
> from fsutil.exe.
>
>
> TIA
>
> Best regards
>
> Kerem Gümrükcü
>
>

.... and no, it doesn't appear the bit can be set on non-NTFS volumes
using fsutil.exe methods. You may have to drill down into the BIOS
parameter block on disk... Sounds like a pain.

- Rafael

Kerem Gümrükcü wrote:
> Hi,
>
> is there a way, to set a ntfs volumes "dirty" flag without
> the fsutil.exe tool. I want to integrate this functionality of
> setting a dirty flag on a volume into my application.Where
> and what do i have to modify on the drive/registry to enforce
> a drive check after a system reboot. Is this applicable to
> other drives like FAT(32). I think it should be, as far as i know
> from fsutil.exe.
>
>
> TIA
>
> Best regards
>
> Kerem Gümrükcü
>
>

Hi Rafael,

thanks for the example. It is always the DeviceIOControl
that makes such things possible. Accessing NTFS Volumes
is just enough. I found interessting informations here:
http://www.ntfs.com/

But i think i will let the Drivers do the work for me since i dont
want to risk to damage a drive. Ill will do some tests on some
virtual systems on my machine and see what i can achieve...

Thank you very much,...

Best regards

Kerem Gümrükcü


"Rafael R. [Live Butterfly]" <"[myfirstname]"@fromvistatoxp.com> schrieb im
Newsbeitrag news:e$m%...
> ... and no, it doesn't appear the bit can be set on non-NTFS volumes using
> fsutil.exe methods. You may have to drill down into the BIOS parameter
> block on disk... Sounds like a pain.
>
> - Rafael
>
> Kerem Gümrükcü wrote:
>> Hi,
>>
>> is there a way, to set a ntfs volumes "dirty" flag without
>> the fsutil.exe tool. I want to integrate this functionality of
>> setting a dirty flag on a volume into my application.Where
>> and what do i have to modify on the drive/registry to enforce
>> a drive check after a system reboot. Is this applicable to
>> other drives like FAT(32). I think it should be, as far as i know
>> from fsutil.exe.
>>
>>
>> TIA
>>
>> Best regards
>>
>> Kerem Gümrükcü
>>

By the Way,

> Your mileage may vary. I'm not responsible if your computer is turned into
> cheese.

I like Cheeese,...


Best regards

Kerem Gümrükcü

Hi Rafael,

when i try to gain access to my Windows Drive ("C:") with the given
Parameters
for the DeviceIOControl with the CreateFile function i get a "Invalid
Handle", all
other drives work fine. Do you have any idea why?


Best regards

Kerem Gümrükcü


"Rafael R. [Live Butterfly]" <"[myfirstname]"@fromvistatoxp.com> schrieb im
Newsbeitrag news:e$m%...
> ... and no, it doesn't appear the bit can be set on non-NTFS volumes using
> fsutil.exe methods. You may have to drill down into the BIOS parameter
> block on disk... Sounds like a pain.
>
> - Rafael
>
> Kerem Gümrükcü wrote:
>> Hi,
>>
>> is there a way, to set a ntfs volumes "dirty" flag without
>> the fsutil.exe tool. I want to integrate this functionality of
>> setting a dirty flag on a volume into my application.Where
>> and what do i have to modify on the drive/registry to enforce
>> a drive check after a system reboot. Is this applicable to
>> other drives like FAT(32). I think it should be, as far as i know
>> from fsutil.exe.
>>
>>
>> TIA
>>
>> Best regards
>>
>> Kerem Gümrükcü
>>

I'm assuming you meant DeviceIoControl() returns 0 and GetLastError()
returns INVALID_HANDLE. Does CreateFile( \\.\C:, ... ) return a proper
handle?

I'll check fsutil.exe again but I don't recall seeing any special
handling for the system volume. Try using the volume names (i.e.
\\?\Volume{475977c3-578a-11da-8cd6-806e6f6e6963}\)?

- Rafael

Kerem Gümrükcü wrote:
> Hi Rafael,
>
> when i try to gain access to my Windows Drive ("C:") with the given
> Parameters
> for the DeviceIOControl with the CreateFile function i get a "Invalid
> Handle", all
> other drives work fine. Do you have any idea why?
>
>
> Best regards
>
> Kerem Gümrükcü
>
>
> "Rafael R. [Live Butterfly]" <"[myfirstname]"@fromvistatoxp.com> schrieb im
> Newsbeitrag news:e$m%...
>> ... and no, it doesn't appear the bit can be set on non-NTFS volumes using
>> fsutil.exe methods. You may have to drill down into the BIOS parameter
>> block on disk... Sounds like a pain.
>>
>> - Rafael
>>
>> Kerem Gümrükcü wrote:
>>> Hi,
>>>
>>> is there a way, to set a ntfs volumes "dirty" flag without
>>> the fsutil.exe tool. I want to integrate this functionality of
>>> setting a dirty flag on a volume into my application.Where
>>> and what do i have to modify on the drive/registry to enforce
>>> a drive check after a system reboot. Is this applicable to
>>> other drives like FAT(32). I think it should be, as far as i know
>>> from fsutil.exe.
>>>
>>>
>>> TIA
>>>
>>> Best regards
>>>
>>> Kerem Gümrükcü
>>>
>

Hi Rafael,

yes, DeviceIOControl returns FALSE and GetLastError says "Invalid Handle".
What could cause that return code, sure a invalid handle, but how does this
happen.
How do i get volume names? I work with GetLogicalDriveStrings(...) to
retrieve
the logical volumes. How to get volume names?

When i tried to open the the A: Floppy i got something like "Wrong
Parameter"
from DeviceIOControl = FALSE and GetLastError() following it. Ok Floppy A:
is empty and no disk inserted,...

Best regards

Kerem Gümrükcü

"Rafael R. [Live Butterfly]" <"[myfirstname]"@fromvistatoxp.com> schrieb im
Newsbeitrag news:%...
> I'm assuming you meant DeviceIoControl() returns 0 and GetLastError()
> returns INVALID_HANDLE. Does CreateFile( \\.\C:, ... ) return a proper
> handle?
>
> I'll check fsutil.exe again but I don't recall seeing any special handling
> for the system volume. Try using the volume names (i.e.
> \\?\Volume{475977c3-578a-11da-8cd6-806e6f6e6963}\)?
>
> - Rafael
>
> Kerem Gümrükcü wrote:
>> Hi Rafael,
>>
>> when i try to gain access to my Windows Drive ("C:") with the given
>> Parameters
>> for the DeviceIOControl with the CreateFile function i get a "Invalid
>> Handle", all
>> other drives work fine. Do you have any idea why?
>>
>>
>> Best regards
>>
>> Kerem Gümrükcü
>>
>>
>> "Rafael R. [Live Butterfly]" <"[myfirstname]"@fromvistatoxp.com> schrieb
>> im Newsbeitrag news:e$m%...
>>> ... and no, it doesn't appear the bit can be set on non-NTFS volumes
>>> using fsutil.exe methods. You may have to drill down into the BIOS
>>> parameter block on disk... Sounds like a pain.
>>>
>>> - Rafael
>>>
>>> Kerem Gümrükcü wrote:
>>>> Hi,
>>>>
>>>> is there a way, to set a ntfs volumes "dirty" flag without
>>>> the fsutil.exe tool. I want to integrate this functionality of
>>>> setting a dirty flag on a volume into my application.Where
>>>> and what do i have to modify on the drive/registry to enforce
>>>> a drive check after a system reboot. Is this applicable to
>>>> other drives like FAT(32). I think it should be, as far as i know
>>>> from fsutil.exe.
>>>>
>>>>
>>>> TIA
>>>>
>>>> Best regards
>>>>
>>>> Kerem Gümrükcü
>>>>
>>

> How do i get volume names? I work with GetLogicalDriveStrings(...) to
> retrieve
> the logical volumes. How to get volume names?


Ok, i got it:
GetVolumeNameForVolumeMountPoint

Hi Rafael,

i cant set the dirty bit on the system volume. Do you have
any idea why?

Best regards

Kerem Gümrükcü


"Rafael R. [Live Butterfly]" <"[myfirstname]"@fromvistatoxp.com> schrieb im
Newsbeitrag news:%...
> I'm assuming you meant DeviceIoControl() returns 0 and GetLastError()
> returns INVALID_HANDLE. Does CreateFile( \\.\C:, ... ) return a proper
> handle?
>
> I'll check fsutil.exe again but I don't recall seeing any special handling
> for the system volume. Try using the volume names (i.e.
> \\?\Volume{475977c3-578a-11da-8cd6-806e6f6e6963}\)?
>
> - Rafael
>
> Kerem Gümrükcü wrote:
>> Hi Rafael,
>>
>> when i try to gain access to my Windows Drive ("C:") with the given
>> Parameters
>> for the DeviceIOControl with the CreateFile function i get a "Invalid
>> Handle", all
>> other drives work fine. Do you have any idea why?
>>
>>
>> Best regards
>>
>> Kerem Gümrükcü
>>
>>
>> "Rafael R. [Live Butterfly]" <"[myfirstname]"@fromvistatoxp.com> schrieb
>> im Newsbeitrag news:e$m%...
>>> ... and no, it doesn't appear the bit can be set on non-NTFS volumes
>>> using fsutil.exe methods. You may have to drill down into the BIOS
>>> parameter block on disk... Sounds like a pain.
>>>
>>> - Rafael
>>>
>>> Kerem Gümrükcü wrote:
>>>> Hi,
>>>>
>>>> is there a way, to set a ntfs volumes "dirty" flag without
>>>> the fsutil.exe tool. I want to integrate this functionality of
>>>> setting a dirty flag on a volume into my application.Where
>>>> and what do i have to modify on the drive/registry to enforce
>>>> a drive check after a system reboot. Is this applicable to
>>>> other drives like FAT(32). I think it should be, as far as i know
>>>> from fsutil.exe.
>>>>
>>>>
>>>> TIA
>>>>
>>>> Best regards
>>>>
>>>> Kerem Gümrükcü
>>>>
>>