Quote:
Originally Posted by dissident
My idea is to patch the memory-list at the pointer Exec-Base->MemList. Just removing the node of FAST memory out of the memory list with Remove() and inserting it again with Insert(). But this could be dangerous, because it's a private structure and could mess everything up.
|
Less dangerous than removing the entry, would be to set priority so that chipmem is allocated first. Then, no fast mem unless the system runs out of chip.
(But don't ask me how to do that, i've tried to change priority of the mem nodes and it didn't work
).
Quote:
Originally Posted by dissident
Hi meynaf, I've tested it on a WinUAE-68060 config. NoFastMem also works with KS 3.1.
Yes, using it via Execute() could be a solution, but then my program would require the pre OS2.0 NoFastMem in a OS 2.0+ environment.
|
Normally in a 2.0+ environment, NoFastMem should be available somewhere, like sys:system/NoFastMem.
Then again, it all depends
why you want to remove fastmem from the system.
What does your program do ? What is the final goal ?
Perhaps better solutions exist than just removing the fastmem.