[Coco] new problem with unpack

[Wayne Campbell]

I used vfy to change the data size and unpack still reported an error,
albeit a new one: 215 Bad Pathname. I tried using ded to do the same thing,
and unpack also reports a 215 Bad Pathname error. I am not sure what is
going on. I'm guessing increasing the memory allotment isn't enough.

Wayne


On Tue, Oct 29, 2013 at 8:43 AM, Wayne Campbell <asa.rand at gmail.com> wrote:

> Gene,
>
> Looking at vfy's help, I see:
>
> -ud=$hexint to add (modulo $1000) data size
>
> I am thinking this is what you are pointing me to. I need you to explain
> how I can use this with a Basic09 I-Code module. Do you mean I can modify
> the Runtime Variable Storage Size? I know that Runtime Variable Storage
> Size is the same field identified in object-code modules as Permanent
> Storage Size. I am going to try and see what happens. I'll post when I have
> an answer.
>
> Wayne
>
>
> On Mon, Oct 28, 2013 at 2:49 PM, Gene Heskett <gheskett at wdtv.com> wrote:
>
>> On Monday 28 October 2013 17:45:56 Wayne Campbell did opine:
>>
>> > I think you're almost grokking the problem. The memory allocation for
>> > unpack (just the main module and the getHeader sub-routine) is <1K. The
>> > other modules called by unpack are loaded and run from the disk using
>> > the RUN statement. I am also using the KILL statement to remove a
>> > module when it is done with it's part of the job. The other modules,
>> > readCode, defVars, buildSrc and instruction, all have near 8K of data
>> > memory requirements. readCode and instruction go over the 8K boundary,
>> > the other two are just under 8K required. The two that are over 8K
>> > memory requirement are bombing because RunB doesn't seem to allocate
>> > the memory properly. As I said before, this goes all the way back to
>> > OS9 L2, and is not "new to NitrOS9". While I am not sure about the
>> > shell or the system having anything to do with the issue, I believe
>> > RunB is the culprit. I think it has a problem with trying to allocate
>> > more than 8K to a procedure that initially needed <8K (and in this
>> > case, <1K).
>> >
>> > I need help determining this, and determining what (if any) workaround
>> > there is. I am still trying to solve it here, but my knowledge of the
>> > system is wanting. I am thinking about the system calls for requesting
>> > more memory, but I do not know which one, or how to implement it in a
>> > Basic09 routine. I have never seen a Basic09 procedure that made memory
>> > requests from the system.
>> >
>> > I uploaded a new copy of the unpack.os9 disk image to the decode site
>> > today.
>> >
>> > Wayne
>>
>> Wayne:  I just recalled that one of the things my "vfy" can do is modify
>> the default amount of memory a module about to be executed will ask the
>> system for.  Look at the help screen it spits out for advice.
>>
>> Cheers, Gene
>> --
>> "There are four boxes to be used in defense of liberty:
>>  soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author)
>>
>> Why does New Jersey have more toxic waste dumps and California have
>> more lawyers?
>>
>> New Jersey had first choice.
>> A pen in the hand of this president is far more
>> dangerous than 200 million guns in the hands of
>>          law-abiding citizens.
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> 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/
>



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

decode
http://cococoding.com/wayne/