Windows Forum

Ask something
Discussion Locked

Installing legacy applications

0 helpful
7 replies

by patty.hertel

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have some applications that were written for Windows 95/98 that our company requires. We are now starting to use Windows 2000.

When installing the applications users can only get full functionality if:

1. They are Powers users

OR

2. We install the application with the user logged in. We grant them admin right to install the application, and then return the rights to user.

We are trying to find a way to install the applications as admin but have the users access the applications an normal users profiles not power users.

7 replies

by ciscofred

First off you need to find out what the app. is trying to access on the local computer? What error messages are you getting? Turn on Auditing of folders and files. Where to find this? Go to start > settings > Administrative Tools > Local Security Policy >Expand Local Policies and you will see a folder called Audit Policy. This will display failed access on the computer. Also you might need to run regedt32.exe and set permissions for reg. keys. If program runs as administrator or power user it?s usually a permissions thing either access a folder or reg. key. I hope this helps!

by adeal

Install the application with the admin profile. Change the security permissions of the application's folder(s) to allow selected users (or groups) the rights required for access to the folder (and running the application).

by desktop jinx

If the app works as a power user but not as a user, the most likely culprit is the inability of users to write files to \WINNT and/or \Program Files. If the app only works as an Administrator (any Administrator), the hangup is probably a registry key under HKEY_LOCAL_MACHINE. If the app only works as THE Admin-equiv account under which the app was installed, it's probably missing HKEY_USER items or files in the user profile created on setup.

For all but the last case, I use a profiling tool(e.g. Ziff-Davis' InCtrl) to see what registry values and what files the app is creating/changing when it's launched under Admin. Open up those items so Users can modify them. For the last case use a profiling tool during installation and transfer those settings to Default User.

This discussion is closed to new replies.