[Coco] Syscall

[Stephen Fischer]

To me there is the possibility that there is a free memory problem, 
before starting or trying to run the procedure.

There is a command in OS-9 that lists the modules in memory, another one 
that lists the memory in use and another one that lists what has been 
merged together.

With listings of the output of those zipped up and attached to a post 
even my 35 year old memory has a chance to see what is wrong, others 
surely could. But then where my manuals are is unknown.

Looking at mt last boot disk I see "b09.rtns" the contents of have faded 
from my mind.

So, "MFree", "Procs", and perhaps "Ident" -whatever of all modules you 
are trying to load with the output directed to a file ">/D0/list1.txt"... .

Or you could do them one at a time and include the results in a post.

The free memory and modules loaded before anything basic09 is done would 
be interesting.

I worked on at least one large Basic09 program before packing it, is 
NitrOS-9 giving you so much free memory that you cannot even do that 
simple syscall?

SHF

On 3/3/2018 5:26 PM, phil pt wrote:
> I tried running it after the program has been packed and I am having the
> same issue.
> 
> On Sat, Mar 3, 2018 at 8:07 PM, Stephen Fischer <SFischer1 at mindspring.com>
> wrote:
> 
>> Pardon my faulty brain, but my memory says that if you do not pack your
>> procedure than runb is not needed, Basic09 can run your procedure just fine.
>>
>> Or if you do pack your procedure than Basic09 is not needed.
>>
>> SHF
>>
>> On 3/3/2018 4:52 PM, phil pt wrote:
>>
>>> The file byte size is only 8699
>>>
>>> On Fri, Mar 2, 2018 at 10:01 PM, Wayne Campbell <asa.rand at gmail.com>
>>> wrote:
>>>   can execute it just fine
>>>
>>>> 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
>>
>