David Boyett
December 14th 03, 02:14 PM
Well, hopefully this is the right newsgroup, if not just
point me in the right direction.
We have a client that installed a third party software
package on a new Windows XP Home version workstation.
There are 5 users setup each set up with Admin.
The software package was installed under one of
the "Admin" users and it works for that user just fine. If
we log in another user and try to open up the program we
get an "Error accessing the system Registry" error and the
program fails. We have tried to remove the
program/reinstall, including registry entries, under
original user. We have also tried removing the
program/reinstall, including registry entries with other
users with admin setup. Each a no go, only the original
account that first installed the program will run it.
We have contacted the software vendor and they can't help
us, as they don't know the answer as well. (I believe they
have additional security features that the programmers
didn't tell their technicians that prevent additional
installs to protect their "demo" versions). It looks like
there has to be a profile conflict somewhere with their
progam, especially in the initial load.
We've hit a brick wall. I believe it has to be a
security/permission setting for the particular profile(s)
and that's why I'm posting here. Hopefully someone has
seen something similar to this with XP Home.
point me in the right direction.
We have a client that installed a third party software
package on a new Windows XP Home version workstation.
There are 5 users setup each set up with Admin.
The software package was installed under one of
the "Admin" users and it works for that user just fine. If
we log in another user and try to open up the program we
get an "Error accessing the system Registry" error and the
program fails. We have tried to remove the
program/reinstall, including registry entries, under
original user. We have also tried removing the
program/reinstall, including registry entries with other
users with admin setup. Each a no go, only the original
account that first installed the program will run it.
We have contacted the software vendor and they can't help
us, as they don't know the answer as well. (I believe they
have additional security features that the programmers
didn't tell their technicians that prevent additional
installs to protect their "demo" versions). It looks like
there has to be a profile conflict somewhere with their
progam, especially in the initial load.
We've hit a brick wall. I believe it has to be a
security/permission setting for the particular profile(s)
and that's why I'm posting here. Hopefully someone has
seen something similar to this with XP Home.