> Mr. Z wrote:
> > Windows XP Pro SP3 with latest patches.
> >
> > When I added a p/w to one of my admin accounts, XP
> > asked if I wanted to make its files private-and I answered
> > Yes. Now my standard user is having issues running
> > one of the apps intalled by the admin. How can I "unprivatize"
> > the files back in the admin account?
>
> Malke wrote:
> >
http://windowsxp.mvps.org/undoprivate.htm - MVP Ramesh - How to
> > undo "Make this folder private" option"
>
> Mr. Z wrote:
> > Thanks, but which files - c:\documents and settings\user of course,
> > but anywhere else?
>
> Shenan Stanley wrote:
> > Whatever folders you made 'private'.
> >
> > If you only made *your*files private - then it is just c:\documents
> > and settings\<your username> and all subdirectories (yes - you need
> > to propogate the settings to all folders/subfolders.)
> >
> > If you have manually changed the permissions on other folders/files
> > - only you would know this.
> >
> > Given what you have - your problem is unlikely to be due to the
> > fact that you 'privatized the account' (not that you needed to that
> > I see - the built-in administrator profile is not going to be able
> > to be accessed by a standard user account (another administrative
> > level, sure, a standarduser, no.))
> >
> > - What application(s) (specifically) is your standard user having
> > issues running that was intalled by the admin?
> > - What trouble (specifically) is the standard user having with this
> > app?
> >
> > Many older applications (or badly written ones) do not function
> > well without administrative rights. Many of them can be 'worked
> > around' by changing the permissions to their installation
> > directories and/or their registry entries. Some have 'common areas'
> > they also need access to.
> >
> > "RegMon" and "FileMon" come in useful when trying to figure out
> > what an application accesses when ran - so you know what all the
> > users of a computer (and that app) need permissions to in order to
> > properly run said application. Another way is usually to upgrade
> > the application to a version that has been better written (either
> > in the way it works or the way it installed or both) to work in a
> > multi-user/multi-level enviroment.
> >
> > If the applications you are trying to run needs access to the user
> > profile (the only thing that is 'marked private' in the manner
> > described - c:\documents and settings\<username>) for the
> > administrative user account - that is a badly written/single user
> > application and you are not fixing anything, but working around the
> > short-comings of the application and sharing the same stuff (likely
> > settings) with all users of the computer.
>
> Mr. Z wrote:
> > "Whatever folders you made 'private'."
> > Well that's the thing - "I" didn't manually make any folders
> > private, XP did - if you read my OP.
> >
> > I'll check RegMon and FileMon to see if they'll help in my case.
>
> If you read the entire posting - I clarified what "Make Private" does - or
> more precisely - what it does it to.
>
> "If the applications you are trying to run needs access to the user