W2K pro administrative right problem

I have ran into a similar problem and here is what I did to fix it:

1. I made sure that the users group had change rights on the files in the program files directory. Your program might require this same rights in the Winnt folder also.

2. I used cacls so that I wouldn't change any permissions that was already setup. Here is a sample of what I ran to give users change access to all files on the c:\:

"c:\cacls.exe c:\ /E /G builtin\users:c /t /c"

You might want to run cacls with the help switch to decide what parameters you should use.
You would just run this from a command prompt. Hope this helps.

Hi,
The previous respondent's answer is okay to a point, but changing the permissions wholesale misses the reason that those permissions were set in the first place - to stop users making changes that may bring a system down. Far better to pinpoint EXACTLY what files \ registry areas the user requires access to and open only those up. I've had to do the same thing many a time, and have found two apps - regmon and filemon - invaluable in pinpointing the problem. They are available from sysinternals.com, and are freeware (sysinternals are a VERY respected and well known group run by some world reknowned windows experts, so have no fear about using their products). Log in as the user, and use RUNAS to run regmon or filemon in turn, each will show respectively every file or registry access made including the result of that access. You can filter the output of each to show activity by only the co-writer app. Run the co-writer app as the user, and scan the output of regmon \ filemon for'access denied' messages, these will direct you to the file \ registry areas that are causing the problem, so that they alone can be opened up to the user. BTW, I take it that you have added the user to the admin group as a test to prove the app works that way. If you haven't try it, if the app still won't work then theres a remote possibility that some parts of co-writer do not install themselves for 'allusers' and are only available to the user that performed the install. If that's the case, then add the user to admins, perform another install, remove them from admins and see if that helps. Hope it goes ok....