-Sam
.
A guy I know who's familiar with working in the registry said this about
your issue:
__
I think that this was a problem with older programs running on W2K and
Whistler. Access to the registry was tightened with W2K, and some older
programs stopped working. The work-around solution is-I believe-to set
permissions on the subkey to which the program must have access to work so
that a user or users can modify its contents. Permissions can be set in
regedit. I don't know if ACLs need to change or not; I found ACL mentioned
on one page that I've seen so far.
Here's one page that says that their program, designed for NT4, will work on
W2K if the user has the Power User profile instead of the standard user
profile.
http://www.clarklabs.org/inst.htm
Here's another workaround for some other program; install the program as a
normal user (rather than Administrator) while having temporarily given users
write permission on Program Files:
http://www.gmks.com/MAGIC/WindowsNT.html
Perhaps being logged in as a user and using run as to give the installation
operation Administrator permissions would accomplish the same thing (as long
as the user isn't made part of the Administrators group).
__
Hope that helps.
Best,
Chris
__
This posting is provided "AS IS" with no warranties, and confers no rights.
__
"Sam" <SParan...@hotmail.com> wrote in message
news:41ce01c35610$89083db0$a001...@phx.gbl...