<html><head></head><body>All that said - if the op is actually using basic+2 then help is a builtin command in the interactive environment. Furthermore the basic+2 builtin help uses an extra file for fast lookups into the help file, so this additional file could also be the problem.<br><br>I'd need to check when I'm back home what the exact name of this file is, but something like bp2hlp.rfa maybe?<br><br> Johnny <br><br><br><div class="gmail_quote">Paul Koning <paulkoning@comcast.net> skrev: (17 september 2018 16:38:37 CEST)<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Command processing in RSTS depends on which runtime system (more precisely, "keyboard monitor") you're currently in. <br><br>If you're in DCL, standard DCL commands (like "copy") are understood. "help" is another standard DCL command.<br><br>In most other runtime systems, like BASIC, there are a few built-in commands that relate more to the purpose of that runtime system (like "SAVE" or "OLD"). <br><br>In addition, keyboard monitors normally understand any of the defined "system commands" -- also called "CCL commands". Those are commands defined via the create command/system DCL operation, and you can see them with show command/system. For example:<br><br>$ show com/sys<br>BCK- = SY:[ 0,10 ]RMSBCK.TSK /LINE=0<br>BYE- = SY:[ 1,2 ]LOGOUT.TSK /LINE=0 /PRIVILEGE<br>CNV- = SY:[ 0,10 ]RMSCNV.TSK /LINE=0<br>DI-RECTORY = SY:[ 1,2 ]DIRECT.TSK /LINE=CCL /PRIVILEGE<br>...<br><br>In my system, "help" is not shown there, so while DCL knows it, other RTS would not. If your system does respond to it, what is the command definition?<br><br>As for [0,2]help.tsk, that's a strange protection code. Mine has <104> and I can see no reason why that program should be privileged.<br><br> paul<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Sep 17, 2018, at 10:30 AM, Keith Halewood <Keith.Halewood@pitbulluk.org> wrote:<br><br>Hi Paul,<br> <br>Thanks for the info. Other than help.hlp, there is only help.tsk in [0,2] and it has protection <232> (privileged, execute, world readonly, group+owner read/write)<br>After a backup, I’ll do some further experimentation.<br> <br>Regards<br> <br>Keith<br> <br>From: owner-hecnet@Update.UU.SE [mailto:owner-hecnet@Update.UU.SE] On Behalf Of Paul Koning<br>Sent: 17 September 2018 14:01<br>To: hecnet@Update.UU.SE<br>Subject: Re: [HECnet] RSTS/E 10.1 BASIC-2-PLUS problem<br> <br> <br><br><br>On Sep 14, 2018, at 5:26 PM, Keith Halewood <Keith.Halewood@pitbulluk.org> wrote:<br> <br>Hi,<br> <br>I’ve been playing with RSTS/E for a short while, particularly BASIC PLUS. I’ve noted that, logged into account [1,2] I can issue HELP from within BASIC and it’s all fine. From a non-privileged account I created, HELP within BASIC gives me a ‘?Protection violation’ but it seems that all the .HLP files relevant to BASIC have the correct <40> file protection. Am I missing something? Any help would be appreciated.<br> <br>Regards,<br> <br>Keith<br> <br>"help" is most likely a CCL command -- a command defined, typically at startup, that is handled by executing a program.<br> <br>You're right that the actual content in in the *.hlp files, and they need to be protected <40> for that to work. But in addition, the program that handles the command has to be executable by non-privileged users. So look in [0,*] or [1,2] for a help.* file (help.tsk, help.bac, help.sav perhaps). It has to be executable (64 bit set in the protection code). So a typical protection code would be 104.<br> <br> paul<br></blockquote><br></pre></blockquote></div><br>-- <br>Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet.</body></html>