Aaron Sloman See text for reply address wrote:
> > I'm having trouble with the function sys_lock_system.
>
> What exactly are you trying to achieve? Are you wanting to set up
> a saved image that includes some pre-compiled code so that you can
> repeatedly start it up without recompiling?
>
> In that case, I suspect that mkimage may be what you want.
Thanks, Aaron. I'm afraid I'm thrashing about rather blindly. A series
of faulty conjectures that I won't try to reconstruct led me to think I
wanted to execute the code in $usepop/pop/src/syscomp/make_poplink.p by
hand.
> > ;;; MISHAP - sys_lock_system: CALLS OF writeable HAVE BEEN IGNORED
> > (pop_record
> > ;;; _writeable not set true)
> > ;;; DOING : pop_setpop_compiler
> >
> > no matter what I do. In particular, if I start up poplog 15.53,
>
> How did you start it up? Did you include %nort and %noinit ?
I used %nort, but not %noinit, because I was running poplog in the name
of a user who had no init.p file.
> >but HELP *
> > SYS_LOCK_SYSTEM
>
> which takes you into the middle of REF SYSTEM. You may need to read
> the whole of that file to work out what is going on.
I did read quite a lot of it :-)
I'm sure you are right that I didn't really want to be calling
sys_lock_system at all, but someone might still want to have a look at
that error message at some point, because whatever I was doing wrong, it
was not failing to set pop_record_writeable to true.
> > I did try to search
> > the popforum archives at http://www.poplog.org/search/, but was told
> It did not do that to me, but it did not appear to have any information
> on sys_lock_system either!
...
> Must have been a temporary problem?
Yes, Graham Higgins of bel-epa.com sent a message saying that he had
fixed it.
Best,
Steve
|