AmigaOS 3.2 and beyond

[Don_Adan]

Originally Posted by Thomas Richter

Which means that the amount of users that profit from that is extremely limited, and the amount of hard-to-detect errors due to improper error checking increases. Besides, as I already said, it conflicts with existing hardware.




That depends on the configuration.



Again, the purpose of the zero page is *not* to act as a trampoline for MuRedox. The purpose of the zero page is to detect NULL pointers by MuForce. How large that area needs to be depends on the MMU page size, and the MMU page size you can configure. It is not by accident that the maximum MMU page size *also* matches the 32K zero page size, and conveniently also matches the size of the MacOs globals.

MacGlobals are relocated to other memory area by Mac emulators, Fusion and Shapeshifter.

Whow, you want to made with every Amiga debugging machine?
For what?
This is very useless option for average Amiga user.
And for about 99% cases, 1KB of zero page is enough to find wrong access bugs.

As choosable OPTION it can be acceptable.
As DEFAULT this only wasted Amiga resources.
And is totally useless for Amigas with 68000, 68010, 68020,68080, 68040 (PiStorm version).

Too bad that you are not Amiga games player.
You can learn how bugs are catched by WHDLoad.

[Don_Adan]

Originally Posted by Thomas Richter

Correct, in case you haven't understood it so far.

Really,? You made one BIG HOLE in Amiga memory. Available for strange programs.
Even in C new viruses can be written, due many free and unused memory for 68000/68020.

[NorthWay]

Just a curio: I patched my KS(3.1) to start chipmem from $0000F000, but I have a well expanded machine so I'm not bothered.
Oh, and I tried using $00010000 but I'm not sure what happened there: I just got a grey screen. I looked a lot at it, but couldn't find any obvious bug in what I did. *Shrug*