it should be a bug in win2K+NTFS

sorry for the new thread.
I wish the MS man attention it.

http://www.osronline.com/showthread.cfm?link=160605

I’m not sure MS will fix such bugs in outdated OS out of support.

I think they only fix security bugs in it.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntfsd…
> sorry for the new thread.
> I wish the MS man attention it.
>
> http://www.osronline.com/showthread.cfm?link=160605
>

We’ve had to workaround a similar bug in Win2K NTFS (I don’t remember what
SP). IIRC an exception was raised and NTFS “forgot” to release the VCB lock.
In our case analysis proved that the exception turned out to be avoidable
(set/don’t set some bit or something), so we lucked out.

Nasty, really. I do hate supporting unsupported O/S releases :slight_smile:

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
I’m not sure MS will fix such bugs in outdated OS out of support.

I think they only fix security bugs in it.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntfsd…
> sorry for the new thread.
> I wish the MS man attention it.
>
> http://www.osronline.com/showthread.cfm?link=160605
>

I think they don’t fix it.
But I wish they say: Yes,this is a bug in ours.
If they say yes,the only way for me is modify my solution to work around it
or don’t let it happen.
If they say no,I will check everything I can check to find the problem.

But,I think it’s a bug.

“Maxim S. Shatskih” xxxxx@ntfsd…
I’m not sure MS will fix such bugs in outdated OS out of support.

I think they only fix security bugs in it.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntfsd…
> sorry for the new thread.
> I wish the MS man attention it.
>
> http://www.osronline.com/showthread.cfm?link=160605
>

I do hate work around ms bug,although I have do it some times!
But every time it’ is be a hell.

I don’t know what bit will set/don’t set,oh.
Can you describe it simply at your convenience.
Maybe the only way for me is modify my solution.
God…the hell call me …too.

“Scott Noone” wrote in message :xxxxx@ntfsd…
> We’ve had to workaround a similar bug in Win2K NTFS (I don’t remember what
> SP). IIRC an exception was raised and NTFS “forgot” to release the VCB
> lock. In our case analysis proved that the exception turned out to be
> avoidable (set/don’t set some bit or something), so we lucked out.
>
> Nasty, really. I do hate supporting unsupported O/S releases :slight_smile:
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
>
> “Maxim S. Shatskih” wrote in message
> news:xxxxx@ntfsd…
> I’m not sure MS will fix such bugs in outdated OS out of support.
>
> I think they only fix security bugs in it.
>
> –
> Maxim S. Shatskih
> Windows DDK MVP
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> wrote in message news:xxxxx@ntfsd…
>> sorry for the new thread.
>> I wish the MS man attention it.
>>
>> http://www.osronline.com/showthread.cfm?link=160605
>>
>
>
>

> Can you describe it simply at your convenience.

NTFS raises exceptions with the routine NtfsRaiseStatus, so you can set a
breakpoint there and watch it raise (something like, bp ntfs!ntfsraisestatus
“dd @esp+4; k; g” might be useful). Note that raises exceptions is pretty
common in NTFS (STATUS_CANT_WAIT happens often) so you’ll need to sift
through everything and find something that looks out of the ordinary.

This is of course assuming that it’s the same kind of problem, I might just
be sending you on a wild goose chase :slight_smile:

Good luck!

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@ntfsd…
>I do hate work around ms bug,although I have do it some times!
> But every time it’ is be a hell.
>
> I don’t know what bit will set/don’t set,oh.
> Can you describe it simply at your convenience.
> Maybe the only way for me is modify my solution.
> God…the hell call me …too.
>
> “Scott Noone” wrote in message :xxxxx@ntfsd…
>> We’ve had to workaround a similar bug in Win2K NTFS (I don’t remember
>> what SP). IIRC an exception was raised and NTFS “forgot” to release the
>> VCB lock. In our case analysis proved that the exception turned out to be
>> avoidable (set/don’t set some bit or something), so we lucked out.
>>
>> Nasty, really. I do hate supporting unsupported O/S releases :slight_smile:
>>
>> -scott
>>
>> –
>> Scott Noone
>> Consulting Associate
>> OSR Open Systems Resources, Inc.
>> http://www.osronline.com
>>
>>
>>
>> “Maxim S. Shatskih” wrote in message
>> news:xxxxx@ntfsd…
>> I’m not sure MS will fix such bugs in outdated OS out of support.
>>
>> I think they only fix security bugs in it.
>>
>> –
>> Maxim S. Shatskih
>> Windows DDK MVP
>> xxxxx@storagecraft.com
>> http://www.storagecraft.com
>>
>> wrote in message news:xxxxx@ntfsd…
>>> sorry for the new thread.
>>> I wish the MS man attention it.
>>>
>>> http://www.osronline.com/showthread.cfm?link=160605
>>>
>>
>>
>>
>
>
>

I have test it,but the result is strange.
I construct a simple environment for test:
Win2K + sp4 + roll up1,and C: is FAT32, D: is NTFS.
C: is system boot volume,and D: volume is for test.
there are only one file in D: volume, d:\1.txt

I do the test by following:
the windbg:
bp ntfs!ntfsraisestatus “dd @esp+4; kb”

1.start notepad
2.click the notepad manuitem: file/open…
3.in the “file open” dialog,I shift+del the file(d:\1.txt")
(my minifilter will treat the FileDisposition as FileRename,and complete
it);
no breakpoint was hitted!
I think my minifilter just change some states in VCB.

4.in explorer,I right-click the d:
breakpoint was hitted!

be38e490 8185fd08 c00000d8 00000000 00000000
be38e4a0 00000000 be38e7c4 817e33c8 00000040
be38e4b0 00000040 00000000 00000010 00000000
be38e4c0 00000000 00000000 a0109e34 00000000
be38e4d0 a01903f0 00000000 00000000 be38e500
be38e4e0 0208000c be38e098 00380018 e1c75728
be38e4f0 be38e700 0074006e 00730075 00720065
be38e500 0064002e 00740061 004c002e 0047004f
ChildEBP RetAddr Args to Child
be38e488 bea18683 8185fd08 c00000d8 00000000 Ntfs!NtfsRaiseStatus
be38e778 be9e9666 8185fd08 817e33c8 be38e7ec Ntfs!NtfsCommonCreate+0xf93
be38e82c 8041dded 81949020 817e33c8 00000000 Ntfs!NtfsFsdCreate+0x186
be38e840 bff523ce 00000000 817e33c8 81842698 nt!IopfCallDriver+0x35
be38e864 bff5de5f be38e884 81917c60 00000000
fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20e
be38e8a0 8041dded 81917c60 817e3534 817e33d8 fltmgr!FltpCreate+0x29d
be38e8b4 804bf978 804824e0 804beeba be38ebb8 nt!IopfCallDriver+0x35
be38ea44 80450893 81a6dab0 00000000 be38eafc nt!IopParseDevice+0xabe
be38eabc 804d59a0 00000000 81aa5b00 00000040 nt!ObpLookupObjectName+0x4e7
be38ebcc 8049f9f1 00000000 00000000 00000001 nt!ObOpenObjectByName+0xc8
be38eca8 8049f596 00dff3d8 80100080 00dff374 nt!IopCreateFile+0x407
be38ecf0 804a6fde 00dff3d8 80100080 00dff374 nt!IoCreateFile+0x36
be38ed30 80464f84 00dff3d8 80100080 00dff374 nt!NtCreateFile+0x2e
be38ed30 77f88283 00dff3d8 80100080 00dff374 nt!KiSystemService+0xc4
00dff334 77e7c56c 00dff3d8 80100080 00dff374 ntdll!NtCreateFile+0xb
WARNING: Frame IP not in any known module. Following frames may be wrong.
00dff3d0 72151323 00000000 80000000 00000003 0x77e7c56c
00dff428 7215178b 00000003 00dff438 00000000 0x72151323
00dff43c 7215214c 00000003 000ebaf0 78fbee5d 0x7215178b
00dff59c 78fbd7ab 000eba58 000e9498 00000003 0x7215214c
00dff61c 76e277ba 00000003 000801ad 000e6108 0x78fbd7ab
Ntfs!NtfsRaiseStatus:
be9dcce0 56 push esi

I think it’s because the states of the NTFS,when right-click the d: in
explorer.exe,NtfsRaiseStatus is called.

“Scott Noone” дÈëÏûÏ¢ÐÂÎÅ:xxxxx@ntfsd…
>> Can you describe it simply at your convenience.
>
> NTFS raises exceptions with the routine NtfsRaiseStatus, so you can set a
> breakpoint there and watch it raise (something like, bp
> ntfs!ntfsraisestatus “dd @esp+4; k; g” might be useful). Note that raises
> exceptions is pretty common in NTFS (STATUS_CANT_WAIT happens often) so
> you’ll need to sift through everything and find something that looks out
> of the ordinary.
>
> This is of course assuming that it’s the same kind of problem, I might
> just be sending you on a wild goose chase :slight_smile:
>
> Good luck!
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
>
> wrote in message news:xxxxx@ntfsd…
>>I do hate work around ms bug,although I have do it some times!
>> But every time it’ is be a hell.
>>
>> I don’t know what bit will set/don’t set,oh.
>> Can you describe it simply at your convenience.
>> Maybe the only way for me is modify my solution.
>> God…the hell call me …too.
>>
>> “Scott Noone” wrote in message :xxxxx@ntfsd…
>>> We’ve had to workaround a similar bug in Win2K NTFS (I don’t remember
>>> what SP). IIRC an exception was raised and NTFS “forgot” to release the
>>> VCB lock. In our case analysis proved that the exception turned out to
>>> be avoidable (set/don’t set some bit or something), so we lucked out.
>>>
>>> Nasty, really. I do hate supporting unsupported O/S releases :slight_smile:
>>>
>>> -scott
>>>
>>> –
>>> Scott Noone
>>> Consulting Associate
>>> OSR Open Systems Resources, Inc.
>>> http://www.osronline.com
>>>
>>>
>>>
>>> “Maxim S. Shatskih” wrote in message
>>> news:xxxxx@ntfsd…
>>> I’m not sure MS will fix such bugs in outdated OS out of support.
>>>
>>> I think they only fix security bugs in it.
>>>
>>> –
>>> Maxim S. Shatskih
>>> Windows DDK MVP
>>> xxxxx@storagecraft.com
>>> http://www.storagecraft.com
>>>
>>> wrote in message news:xxxxx@ntfsd…
>>>> sorry for the new thread.
>>>> I wish the MS man attention it.
>>>>
>>>> http://www.osronline.com/showthread.cfm?link=160605
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>

> I’m not sure MS will fix such bugs in outdated OS out of support.

Remember, if you are in Redmond/Bellevue Win7 is legacy.

They have finished it and they have to get on with the next release; This
is not a criticism of the engineers involved, those are the rigors they work
under… Equally there are probably not a lot of devs left who remember the
pain that was Win2K ship…

Must not be an exception explicitly raised by NTFS. Potentially dealing with
some kind of other error path.

4.in explorer,I right-click the d:
breakpoint was hitted!
be38e490 8185fd08 c00000d8 00000000 00000000
be38e488 bea18683 8185fd08 c00000d8 00000000 Ntfs!NtfsRaiseStatus
be38e778 be9e9666 8185fd08 817e33c8 be38e7ec Ntfs!NtfsCommonCreate+0xf93
be38e82c 8041dded 81949020 817e33c8 00000000 Ntfs!NtfsFsdCreate+0x186

c00000d8 == STATUS_CANT_WAIT. The create handler just couldn’t get some lock
(VCB lock?) so it’s going to post the request to a worker thread instead of
blocking. It’s a “normal” exception, nothing overly interesting.

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@ntfsd…
>I have test it,but the result is strange.
> I construct a simple environment for test:
> Win2K + sp4 + roll up1,and C: is FAT32, D: is NTFS.
> C: is system boot volume,and D: volume is for test.
> there are only one file in D: volume, d:\1.txt
>
> I do the test by following:
> the windbg:
> bp ntfs!ntfsraisestatus “dd @esp+4; kb”
>
> 1.start notepad
> 2.click the notepad manuitem: file/open…
> 3.in the “file open” dialog,I shift+del the file(d:\1.txt")
> (my minifilter will treat the FileDisposition as FileRename,and complete
> it);
> no breakpoint was hitted!
> I think my minifilter just change some states in VCB.
>
> 4.in explorer,I right-click the d:
> breakpoint was hitted!
>
> be38e490 8185fd08 c00000d8 00000000 00000000
> be38e4a0 00000000 be38e7c4 817e33c8 00000040
> be38e4b0 00000040 00000000 00000010 00000000
> be38e4c0 00000000 00000000 a0109e34 00000000
> be38e4d0 a01903f0 00000000 00000000 be38e500
> be38e4e0 0208000c be38e098 00380018 e1c75728
> be38e4f0 be38e700 0074006e 00730075 00720065
> be38e500 0064002e 00740061 004c002e 0047004f
> ChildEBP RetAddr Args to Child
> be38e488 bea18683 8185fd08 c00000d8 00000000 Ntfs!NtfsRaiseStatus
> be38e778 be9e9666 8185fd08 817e33c8 be38e7ec Ntfs!NtfsCommonCreate+0xf93
> be38e82c 8041dded 81949020 817e33c8 00000000 Ntfs!NtfsFsdCreate+0x186
> be38e840 bff523ce 00000000 817e33c8 81842698 nt!IopfCallDriver+0x35
> be38e864 bff5de5f be38e884 81917c60 00000000
> fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20e
> be38e8a0 8041dded 81917c60 817e3534 817e33d8 fltmgr!FltpCreate+0x29d
> be38e8b4 804bf978 804824e0 804beeba be38ebb8 nt!IopfCallDriver+0x35
> be38ea44 80450893 81a6dab0 00000000 be38eafc nt!IopParseDevice+0xabe
> be38eabc 804d59a0 00000000 81aa5b00 00000040 nt!ObpLookupObjectName+0x4e7
> be38ebcc 8049f9f1 00000000 00000000 00000001 nt!ObOpenObjectByName+0xc8
> be38eca8 8049f596 00dff3d8 80100080 00dff374 nt!IopCreateFile+0x407
> be38ecf0 804a6fde 00dff3d8 80100080 00dff374 nt!IoCreateFile+0x36
> be38ed30 80464f84 00dff3d8 80100080 00dff374 nt!NtCreateFile+0x2e
> be38ed30 77f88283 00dff3d8 80100080 00dff374 nt!KiSystemService+0xc4
> 00dff334 77e7c56c 00dff3d8 80100080 00dff374 ntdll!NtCreateFile+0xb
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 00dff3d0 72151323 00000000 80000000 00000003 0x77e7c56c
> 00dff428 7215178b 00000003 00dff438 00000000 0x72151323
> 00dff43c 7215214c 00000003 000ebaf0 78fbee5d 0x7215178b
> 00dff59c 78fbd7ab 000eba58 000e9498 00000003 0x7215214c
> 00dff61c 76e277ba 00000003 000801ad 000e6108 0x78fbd7ab
> Ntfs!NtfsRaiseStatus:
> be9dcce0 56 push esi
>
>
> I think it’s because the states of the NTFS,when right-click the d: in
> explorer.exe,NtfsRaiseStatus is called.
>
>
>
>
>
> “Scott Noone” дÈëÏûÏ¢ÐÂÎÅ:xxxxx@ntfsd…
>>> Can you describe it simply at your convenience.
>>
>> NTFS raises exceptions with the routine NtfsRaiseStatus, so you can set a
>> breakpoint there and watch it raise (something like, bp
>> ntfs!ntfsraisestatus “dd @esp+4; k; g” might be useful). Note that raises
>> exceptions is pretty common in NTFS (STATUS_CANT_WAIT happens often) so
>> you’ll need to sift through everything and find something that looks out
>> of the ordinary.
>>
>> This is of course assuming that it’s the same kind of problem, I might
>> just be sending you on a wild goose chase :slight_smile:
>>
>> Good luck!
>>
>> -scott
>>
>> –
>> Scott Noone
>> Consulting Associate
>> OSR Open Systems Resources, Inc.
>> http://www.osronline.com
>>
>>
>>
>> wrote in message news:xxxxx@ntfsd…
>>>I do hate work around ms bug,although I have do it some times!
>>> But every time it’ is be a hell.
>>>
>>> I don’t know what bit will set/don’t set,oh.
>>> Can you describe it simply at your convenience.
>>> Maybe the only way for me is modify my solution.
>>> God…the hell call me …too.
>>>
>>> “Scott Noone” wrote in message :xxxxx@ntfsd…
>>>> We’ve had to workaround a similar bug in Win2K NTFS (I don’t remember
>>>> what SP). IIRC an exception was raised and NTFS “forgot” to release the
>>>> VCB lock. In our case analysis proved that the exception turned out to
>>>> be avoidable (set/don’t set some bit or something), so we lucked out.
>>>>
>>>> Nasty, really. I do hate supporting unsupported O/S releases :slight_smile:
>>>>
>>>> -scott
>>>>
>>>> –
>>>> Scott Noone
>>>> Consulting Associate
>>>> OSR Open Systems Resources, Inc.
>>>> http://www.osronline.com
>>>>
>>>>
>>>>
>>>> “Maxim S. Shatskih” wrote in message
>>>> news:xxxxx@ntfsd…
>>>> I’m not sure MS will fix such bugs in outdated OS out of support.
>>>>
>>>> I think they only fix security bugs in it.
>>>>
>>>> –
>>>> Maxim S. Shatskih
>>>> Windows DDK MVP
>>>> xxxxx@storagecraft.com
>>>> http://www.storagecraft.com
>>>>
>>>> wrote in message news:xxxxx@ntfsd…
>>>>> sorry for the new thread.
>>>>> I wish the MS man attention it.
>>>>>
>>>>> http://www.osronline.com/showthread.cfm?link=160605
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>

oh,I’m a capitulant!
trace the NTFS in asm…,my head become heavy.
the only way to me,it’s redesign my solution to work around it.

“Scott Noone” дÈëÏûÏ¢ÐÂÎÅ:xxxxx@ntfsd…
> Must not be an exception explicitly raised by NTFS. Potentially dealing
> with some kind of other error path.
>
>> 4.in explorer,I right-click the d:
>> breakpoint was hitted!
>> be38e490 8185fd08 c00000d8 00000000 00000000
>> be38e488 bea18683 8185fd08 c00000d8 00000000 Ntfs!NtfsRaiseStatus
>> be38e778 be9e9666 8185fd08 817e33c8 be38e7ec Ntfs!NtfsCommonCreate+0xf93
>> be38e82c 8041dded 81949020 817e33c8 00000000 Ntfs!NtfsFsdCreate+0x186
>
> c00000d8 == STATUS_CANT_WAIT. The create handler just couldn’t get some
> lock (VCB lock?) so it’s going to post the request to a worker thread
> instead of blocking. It’s a “normal” exception, nothing overly
> interesting.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
>
>
> wrote in message news:xxxxx@ntfsd…
>>I have test it,but the result is strange.
>> I construct a simple environment for test:
>> Win2K + sp4 + roll up1,and C: is FAT32, D: is NTFS.
>> C: is system boot volume,and D: volume is for test.
>> there are only one file in D: volume, d:\1.txt
>>
>> I do the test by following:
>> the windbg:
>> bp ntfs!ntfsraisestatus “dd @esp+4; kb”
>>
>> 1.start notepad
>> 2.click the notepad manuitem: file/open…
>> 3.in the “file open” dialog,I shift+del the file(d:\1.txt")
>> (my minifilter will treat the FileDisposition as FileRename,and complete
>> it);
>> no breakpoint was hitted!
>> I think my minifilter just change some states in VCB.
>>
>> 4.in explorer,I right-click the d:
>> breakpoint was hitted!
>>
>> be38e490 8185fd08 c00000d8 00000000 00000000
>> be38e4a0 00000000 be38e7c4 817e33c8 00000040
>> be38e4b0 00000040 00000000 00000010 00000000
>> be38e4c0 00000000 00000000 a0109e34 00000000
>> be38e4d0 a01903f0 00000000 00000000 be38e500
>> be38e4e0 0208000c be38e098 00380018 e1c75728
>> be38e4f0 be38e700 0074006e 00730075 00720065
>> be38e500 0064002e 00740061 004c002e 0047004f
>> ChildEBP RetAddr Args to Child
>> be38e488 bea18683 8185fd08 c00000d8 00000000 Ntfs!NtfsRaiseStatus
>> be38e778 be9e9666 8185fd08 817e33c8 be38e7ec Ntfs!NtfsCommonCreate+0xf93
>> be38e82c 8041dded 81949020 817e33c8 00000000 Ntfs!NtfsFsdCreate+0x186
>> be38e840 bff523ce 00000000 817e33c8 81842698 nt!IopfCallDriver+0x35
>> be38e864 bff5de5f be38e884 81917c60 00000000
>> fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20e
>> be38e8a0 8041dded 81917c60 817e3534 817e33d8 fltmgr!FltpCreate+0x29d
>> be38e8b4 804bf978 804824e0 804beeba be38ebb8 nt!IopfCallDriver+0x35
>> be38ea44 80450893 81a6dab0 00000000 be38eafc nt!IopParseDevice+0xabe
>> be38eabc 804d59a0 00000000 81aa5b00 00000040 nt!ObpLookupObjectName+0x4e7
>> be38ebcc 8049f9f1 00000000 00000000 00000001 nt!ObOpenObjectByName+0xc8
>> be38eca8 8049f596 00dff3d8 80100080 00dff374 nt!IopCreateFile+0x407
>> be38ecf0 804a6fde 00dff3d8 80100080 00dff374 nt!IoCreateFile+0x36
>> be38ed30 80464f84 00dff3d8 80100080 00dff374 nt!NtCreateFile+0x2e
>> be38ed30 77f88283 00dff3d8 80100080 00dff374 nt!KiSystemService+0xc4
>> 00dff334 77e7c56c 00dff3d8 80100080 00dff374 ntdll!NtCreateFile+0xb
>> WARNING: Frame IP not in any known module. Following frames may be wrong.
>> 00dff3d0 72151323 00000000 80000000 00000003 0x77e7c56c
>> 00dff428 7215178b 00000003 00dff438 00000000 0x72151323
>> 00dff43c 7215214c 00000003 000ebaf0 78fbee5d 0x7215178b
>> 00dff59c 78fbd7ab 000eba58 000e9498 00000003 0x7215214c
>> 00dff61c 76e277ba 00000003 000801ad 000e6108 0x78fbd7ab
>> Ntfs!NtfsRaiseStatus:
>> be9dcce0 56 push esi
>>
>>
>> I think it’s because the states of the NTFS,when right-click the d: in
>> explorer.exe,NtfsRaiseStatus is called.
>>
>>
>>
>>
>>
>> “Scott Noone” §Õ?:xxxxx@ntfsd…
>>>> Can you describe it simply at your convenience.
>>>
>>> NTFS raises exceptions with the routine NtfsRaiseStatus, so you can set
>>> a breakpoint there and watch it raise (something like, bp
>>> ntfs!ntfsraisestatus “dd @esp+4; k; g” might be useful). Note that
>>> raises exceptions is pretty common in NTFS (STATUS_CANT_WAIT happens
>>> often) so you’ll need to sift through everything and find something that
>>> looks out of the ordinary.
>>>
>>> This is of course assuming that it’s the same kind of problem, I might
>>> just be sending you on a wild goose chase :slight_smile:
>>>
>>> Good luck!
>>>
>>> -scott
>>>
>>> –
>>> Scott Noone
>>> Consulting Associate
>>> OSR Open Systems Resources, Inc.
>>> http://www.osronline.com
>>>
>>>
>>>
>>> wrote in message news:xxxxx@ntfsd…
>>>>I do hate work around ms bug,although I have do it some times!
>>>> But every time it’ is be a hell.
>>>>
>>>> I don’t know what bit will set/don’t set,oh.
>>>> Can you describe it simply at your convenience.
>>>> Maybe the only way for me is modify my solution.
>>>> God…the hell call me …too.
>>>>
>>>> “Scott Noone” wrote in message :xxxxx@ntfsd…
>>>>> We’ve had to workaround a similar bug in Win2K NTFS (I don’t remember
>>>>> what SP). IIRC an exception was raised and NTFS “forgot” to release
>>>>> the VCB lock. In our case analysis proved that the exception turned
>>>>> out to be avoidable (set/don’t set some bit or something), so we
>>>>> lucked out.
>>>>>
>>>>> Nasty, really. I do hate supporting unsupported O/S releases :slight_smile:
>>>>>
>>>>> -scott
>>>>>
>>>>> –
>>>>> Scott Noone
>>>>> Consulting Associate
>>>>> OSR Open Systems Resources, Inc.
>>>>> http://www.osronline.com
>>>>>
>>>>>
>>>>>
>>>>> “Maxim S. Shatskih” wrote in message
>>>>> news:xxxxx@ntfsd…
>>>>> I’m not sure MS will fix such bugs in outdated OS out of support.
>>>>>
>>>>> I think they only fix security bugs in it.
>>>>>
>>>>> –
>>>>> Maxim S. Shatskih
>>>>> Windows DDK MVP
>>>>> xxxxx@storagecraft.com
>>>>> http://www.storagecraft.com
>>>>>
>>>>> wrote in message news:xxxxx@ntfsd…
>>>>>> sorry for the new thread.
>>>>>> I wish the MS man attention it.
>>>>>>
>>>>>> http://www.osronline.com/showthread.cfm?link=160605
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>