Access denied when trying to move directory in use
in [Win32 Kernel]
|
From: Tim Roberts on 15 Feb 2007 23:40 Corinna Vinschen <corinna(a)community.nospam> wrote: > >I'm not sure I get the point here. > >I have provided a source code testcase which allows your engineer to >reproduce the bug which I could reproduce now on five different XP >systems. So, just send the testcase to your engineer together with my >description. That should do it to either fix the bug or to ignore it, >which is your decision. The point is that this is not an official Microsoft support channel, Jeffrey is a not one of the select few who has access to their bug database, and he doesn't necessarily have access to someone who is. >Personally I'm interested to hear what's coming out of it but I have >certasinly no intention to create a support case. Well, then it is likely to go unfixed. With maybe millions of bogus bug reports coming in over the years, perhaps you can understand that they get a little jaded. They want people to go through the official channels to winnow out the loonies, so to speak. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc.
From: "Jeffrey Tan[MSFT]" on 16 Feb 2007 03:31 Hi Corinna , Thank you for feedback your concern. Yes, I understand that you provide the source code for reproducing this behavior. However, as I pointed out in the first reply, the official MSDN newsgroup support does not cover this type of undocumented API usage, not even with the root cause of the undocumented API. The undocumented API using means that its behavior will not be granted to be consistent on all the Windows. Also, I do not have the official channel to ask for the FS team to support this issue for this complex issue. That's why I recommend you to go with the offical PSS case support channel. They have more official channel to contact product team. Anyway, I will try to forward your further code and test code to the FS team, but I am not sure if they will go on with it. I will feedback any information here. Again, thanks for your understanding. Best regards, Jeffrey Tan Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
From: Corinna Vinschen on 18 Feb 2007 05:09 Hi Jeffrey, Jeffrey Tan[MSFT] wrote: > Hi Corinna , > > Thank you for feedback your concern. > > Yes, I understand that you provide the source code for reproducing this > behavior. However, as I pointed out in the first reply, the official MSDN > newsgroup support does not cover this type of undocumented API usage, not > even with the root cause of the undocumented API. The undocumented API > using means that its behavior will not be granted to be consistent on all > the Windows. That's ok. I still don't understand (and think it's a mistake) that such a basic and essential functionality as renaming a file (which is called from kernel32.dll anyway) can be treated as undocumented, but that's beside the point. I don't seem to be able to make myself clear enough, though. I created a testcase *for you* to be able to reproduce the problem. I didn't create the testcase for me since I already had a working workaround. I assumed that Microsoft has an interest in fixing the bug. That's why I wrote it's your (Microsoft's) decision whether you want to fix the bug or not. > Also, I do not have the official channel to ask for the FS team to support > this issue for this complex issue. That's why I recommend you to go with > the offical PSS case support channel. They have more official channel to > contact product team. Yes, I could create a support case for this problem, but how likely is it that I get a reply different from "it's an unsupported API"? I only have a limited number of support cases in my subscription. But I see your point and maybe I will actually open a support case. > Anyway, I will try to forward your further code and test code to the FS > team, but I am not sure if they will go on with it. I will feedback any > information here. Thanks, that would be nice, Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat
From: "Jeffrey Tan[MSFT]" on 19 Feb 2007 02:53 Hi Corinna , Thanks for your feedback. I still did not get any new update yet. The undocumented API is caused by the non open source feature of Windows, so it is different from other open source OS. These undocumented API is not suggested to use and if you use it you are responsible to understand its behavior, Microsoft did not keep any promise of its behavior. Thanks. Best regards, Jeffrey Tan Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
First
|
Prev
|
Pages: 1 2 3 4 5 Prev: RasEditPhoneBookEntry and Vista Next: GetCurrentHwProfile determining dockability on Vista |