If I try to invoke the help from the Mercury menu I see nothing and get nothing in Mercury's system messages or in the Windows event log. For testing purposes, I also have a command shell running on the services desktop. If, from there, I try "[path\]winhlp32.exe [path\]mercury.hlp" there's the same result (nothing). If I try that command using RUNAS (some user) I get an "Access denied" message in the console but no hint about access to what. "Nt authority\system" has sufficient access to winhlp32.exe and mercury.hlp.
FWIW, I also cannot launch the command shell's (JPSoft's TCC) help, a CHM file. When I try, the results are as above. I can do most anything else while on the services desktop (as "nt authority\system"). It is possible that the two help systems (HLP, CHM) require a user profile, or a profile more elaborate that the "system" user has (but that's just a wild guess).
<P>If I try to invoke the help from the Mercury menu I see nothing and get nothing in Mercury's system messages or in the Windows event log.&nbsp; For testing purposes, I also have a command shell running on the services desktop.&nbsp; If, from there, I try "[path\]winhlp32.exe [path\]mercury.hlp" there's the same result (nothing).&nbsp; If I try that command using RUNAS (some user) I get an "Access denied" message in the console but no hint about access to what. "Nt authority\system" has sufficient access to winhlp32.exe and mercury.hlp.</P>
<P>FWIW, I also cannot launch the command shell's (JPSoft's TCC) help, a CHM file.&nbsp; When I try, the results are as above. I can do most anything else while on the services desktop (as "nt authority\system").&nbsp;&nbsp;It is possible&nbsp;that the two help systems (HLP, CHM) require a user profile, or&nbsp;a profile&nbsp;more elaborate that the "system" user has (but that's just a wild guess).</P>
