In said:
Hello Mark,
Is was indeed a string type issue (REG_SZ instead of
REG_EXPAND_SZ). I cannot image how this happened, I was not
editing the registery but OK.
Thank you so much
I learned a great deal from this.
Great you shared your knowledge !
Happy I was able to help. If you hadn't found that %windir%... good
work.
I have a totally different question...
Many programs will run only correctly in an administator account
under Win2K and WinXP. This is unsafe. I'm searching for solutions
for months now but have no clue where to look.
I managed to resolve folder and file access rights but many times
this does not solve the problems.
Is there a tool to track down why certain programs will not work
in User or Restricted User accounts or is there 90% a common
cause?
Without specifics it is difficult to say. Some applications are
simply not written well (for Windows) <G>. That might mean it was
not designed for use by accounts that did not install it. It might
be a permissions issue in that it requires write access in HKLM or
that it requires system services or access not permitted to non-
admin. accounts. In some cases if the application is installed by
the user that needs it (with temporary membership in the
Administrators group for installation) it will function correctly
thereafter for that one account. There could be other reasons why.
My best suggestion is to check with the publisher of the software in
question.
As to tools. Although possibly intimidating at first the 3rd-party
tools that might be useful that I would try are REGMON and FILEMON
from
www.sysinternals.com.
But turning on file auditing and/or registry auditing may give you
some clues in the Event Logs.
It's really too general a question as it stands. You should try the
people that wrote it first. Then a group focused on the particular
application I suggest.
[ snipped prior ]