[Coco] Interbank Incident for Drivewire ?

[Boisy G. Pitre]

Look in the kernel itself. It sets up the memory map initially, and there may be something incorrectly set.

On Nov 26, 2012, at 9:19 AM, Robert Gault <robert.gault at att.net> wrote:

> In the continuing saga of finding adequate memory for The Interbank Incident in a Drivewire boot, it has become evident that the Free Memory Bit Map has had some bits in high memory incorrectly filled.
> 
> Level1 has the kernel starting at $EE00. $10000-$EE00=$1200 or $12 pages. That means there should be 18 bits at the end of the memory map filled. So the last 3 bytes in the bit map should be %00000011, %11111111, %11111111.
> Well that is not what is in the bit map the first time F$SRqMem is called. The map from $200-$2FF is
> F8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
> 
> The last four bytes should be       00 03 FF FF
> 
> Using the MESS debugger, I've manually changed the bit map and NitrOS-9 Level1 boots correctly with additional free memory. The question is what incorrectly assigned this memory?
> 
> I've tested the F$SRqMem routine and it is good. What routine in which module is setting memory bits without using F$SRqMem?
> 
> Robert
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco