[Coco] Syscall

Wayne Campbell asa.rand at gmail.com
Fri Mar 2 22:46:22 EST 2018


It's not about how much free space you have. It's about how big the memory
block is that's holding syscall and whatever is merged with it. If the
block is more than 8K, basically long will have a hard time loading it in.
I can have syscall gfx gfx gfx2 and inkey merged together and it will work
okay. If I merge all of those with runB and preload runB, basic09 will
still run into the problem and report a 43 error when trying to run the
program in its memory. I do not know exactly what the cause is other than
it has to do with the amount of memory that it is dealing with where
syscall is concerned. The same applies to any other subroutine that you
have merged with syscall. If separating syscall by itself still has the
problem then I don't know what to tell you. If you have not tried loading
syscall by itself with nothing else merged with it I suggest that you try
doing that and see what the result is. If it works with syscall by itself
then whatever you have merged with syscall is exceeding the 8K boundary and
that is what the problem is. If syscall by itself does not work then you
are experiencing a different problem and I do not know what to do about it.


On Fri, Mar 2, 2018, 7:34 PM phil pt <ptaylor2446 at gmail.com> wrote:

> I already tried loading Syscall and then the program and I am getting the
> same issue, Then I tried merging runb syscall centertext and errmsg and
> that did not resolve the issue.  When I type mfree It displays that I have
> plenty of memory available
>
> On Fri, Mar 2, 2018 at 10:01 PM, Wayne Campbell <asa.rand at gmail.com>
> wrote:
>
> > I run into this problem a lot. What's happening, is that basic09 is
> trying
> > to load all of the parts that are merged together into the workspace at
> the
> > same time and it's not working. The best way to deal with this issue is
> to
> > make sure that you have enough space available in the workspace and load
> > syscall by itself into memory before running your program. This is not
> the
> > best way to deal with these things but at this point it's the only way I
> > found to deal with it while working in basic09. Perhaps Curtis or someone
> > else can provide a better way.
> >
> > On Fri, Mar 2, 2018, 5:58 PM phil pt <ptaylor2446 at gmail.com> wrote:
> >
> > > I am getting error 43 while trying to call syscall in my basic09 code.
> I
> > > have the correct type and runb and syscall merge.
> > >
> > > --
> > > Coco mailing list
> > > Coco at maltedmedia.com
> > > https://pairlist5.pair.net/mailman/listinfo/coco
> > >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > https://pairlist5.pair.net/mailman/listinfo/coco
> >
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>


More information about the Coco mailing list