From: Corinna Vinschen on 30 Jan 2007 11:05 Corinna Vinschen wrote: > The following sequence > > ZwOpen(FILE_DELETE_ON_CLOSE) > ZwSetInformationFile(FileRenameInformation) > ZwClose() > > works on the following OSes like this: > > - NT4 SP6: Succeeds on files and directories for all accounts. > > - W2K SP4: Succeeds on files and directories for all accounts. > > - XP SP2: Succeeds on files for all accounts. > Fails on directories for all account with ZwSetInformationFile > returning access denied error. > > - 2K3 SP1: Succeeds on files and directories for all accounts. > > Surprise, surprise: > > - Vista: Succeeds on files and directories for non-restricted admin. > Succeeds on directories(!) for restricted admin and standard > user accounts. > Fails on files(!) for restricted admin and standard user > account with ZwSetInformationFile returning access denied > error. Uh oh, sorry, no. The Vista behaviour is not a surprise, it's rather due to a mistake on my side. The permissions of the target folder (where the files and directories are moved to) didn't allow to create files, only directories. This explains why I could move directories but no files into that folder with restricted accounts. Sorry again. Actually Vista behaves like every other system, except XP, moving a file or directory opened for delete-on-close succeeds for all accounts. I looked into the permissions on my XP system again, but the permissions of the target folder allow to create files and directories for every user. So it appears I developed and tested this on the only system showing this behaviour. Corinna -- Antworten an o.g. (existierende) Adresse werden ungelesen verworfen. Private Mails bitte an corinnaPLOPvinschenPINGde.
From: "Jeffrey Tan[MSFT]" on 31 Jan 2007 04:51 Hi Corinna, Really thank you for the effort of collecting so much information! Yes, I understand you want to find out the root cause of this behavior(I am curious either). However, this behavior may hide deep in the kernel-mode(most probably in File System level), so finding the root cause really goes out side of my scope. Anyway, I will forward your useful information to the File System and wait for their further comment. I hope they will provide some insight for this 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.
From: "Jeffrey Tan[MSFT]" on 1 Feb 2007 21:49 Hi Corinna, Sorry for letting you wait. Actually, I still did not get any further feedback from the File System dev team yet, I assume they are busy now. In this situation, if you still want to find out the root cause, I recommend you repost your problem in microsoft.public.development.device.drivers newsgroup. There may be some File System expert to help you find out the root cause. Anyway, once I got any further feedback from the File System dev team, I will paste here. 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 2 Feb 2007 06:47 Hi Jeffrey, Jeffrey Tan[MSFT] wrote: > Hi Corinna, > > Sorry for letting you wait. > > Actually, I still did not get any further feedback from the File System dev > team yet, I assume they are busy now. In this situation, if you still want > to find out the root cause, I recommend you repost your problem in > microsoft.public.development.device.drivers newsgroup. There may be some > File System expert to help you find out the root cause. > > Anyway, once I got any further feedback from the File System dev team, I > will paste here. Thanks for your help. Actually it's not *that* important anymore, now that I have a solution working nicely on all NT versions, and given the fact, that this behaviour apparently only occurs on XP. So, if you get some interesting reply it would be nice if you could share it, if you don't get it, well, never mind. Thanks again, Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat
From: "Jeffrey Tan[MSFT]" on 3 Feb 2007 22:35 Hi Corinna, Thanks for your feedback! Thanks for your patient and understanding. Yes, MSDN newsgroup support nature normally makes it hard to find out the root cause of such type of complex issue. Also, since we have no official channel of contacting the Windows dev team, I can only send consulting emai internal to contact them indirectly. So if there is no response from the dev team, it is rude for me strike them. Anyway, I will try to contact that File System developer privately again, I hope he will have time to response. Thanks again 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.
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: RasEditPhoneBookEntry and Vista Next: GetCurrentHwProfile determining dockability on Vista |