[Coco] new problem with unpack

[Wayne Campbell]

If I do that I won't be able to load the program. All of them together
would use much more space than is available just to load them. I am forced
then to load each "section" separately. The problem is in the allocation
given to each procedure called from the main procedure. Somehow RunB does
not want to properly allocate the memory, or the ones going over 8K data
requirements are asking for more memory than can be allocated in the space
available. I am looking at trying to use the F$Mem system call, but I won't
know more until I actually have it coded.

Wayne


On Mon, Oct 28, 2013 at 3:09 PM, Greg Law <glaw at live.com> wrote:

> Have you tried merging all the modules used by unpack/decode into one file
> (e.g. merge unpack decode ... runb > myunpack) and then running this merged
> file with additional memory (e.g. unpack #12k or unpack #24k)?
>
> I seem to recall that linking modules separately into process space on
> OS-9 Level 2 uses n*8K MMU blocks for each module, and the dead space
> between modules isn't (or can't be) used. This can result in some pretty
> big holes in memory allocation, so the recommended solution is merge all
> the modules into one file so that the modules are loaded contiguously with
> no gaps between modules.
>
> -----Original Message----- From: Wayne Campbell
> Sent: Friday, October 25, 2013 4:11 PM
> To: CoCoList
> Subject: [Coco] new problem with unpack
>
>
> I got the changes made to decode and inserted the RUN and associated
> statements in unpack. When I run it from the command line, I get the
> following:
>
> command: unpack elapsed
> result ERROR #32: Memory Full
>
> command: unpack elapsed #20K (or higher)
> result: ERROR 43: Procedure not found
>
> command: unpack elapsed #12K (through 15K)
> result: PROCEDURE and DIM statements are printed, and
> ERROR #201
>
> I am using ErrorCodes to give me the error messages. In the third one, the
> only one that actually gets as far as it does, there is no error message
> displayed, only the error number. That tells me that the system is
> returning the error, not the program.
>
> Does anyone know what might be the cause of this, and/or what to do to fix
> it? I know it isn't the program code. I have seen this problem before, and
> never knew the cause. Re-writing the code sometimes helped, but there's no
> problems in the code. I am bewildered.
>
> Wayne
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/**mailman/listinfo/coco<http://five.pairlist.net/mailman/listinfo/coco>
>



-- 
The Structure of I-Code
http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code

decode
http://cococoding.com/wayne/