Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: stopthegop on April 16, 2007, 01:16:06 PM
-
Hello
For those who don't know, I thought I'd mention what a fantastic program wballocfast is. It really works at keeping things out of chip memory. The only incompatibility I've found with it is it won't work with Dopus. Otherwise it works great as you can see in this example (http://www.amiga.org/gallery/index.php?n=1943=58191&com_rootid=57194&com_mode=flat&com_order=0#comment58191).
-
Is this patch necessary in OS3.9, which has settings in Workbench prefs to allocate icons etc to fast instead of chip?
--
moto
-
I think that only maps icons into fast memory, but other apps are still free to use chip memory. wballocfast re-routes everything to fastram. Almost everything... :)
-
I guess that's a great thing to use when you have a graphics card.
There's really no reason other than sound and parallel/serial port to use the chip ram when you have a graphics card.
-
Where about is WBAllocfast put in the S:Startup-Sequence ?
I put mine in the C: draw and just before LoadWB I done this,
C:WBAllocfast
LoadWB
Doing it that way my Chip ram is still the same and so is my Fastram like it isnt working.
TIA,
Mike.
-
C:wballocfast >NIL:
Just before setpatch..
-
It is not advisable to install patches before setpatch. This is especially true if you have a 040/060 CPU. And what's the point anyway? Have you tried to install it after it to see if there is a benefit at all?
Furthermore, if you have install patches like PoolMem or MemOptimizer, it is not a good idea to install WbAllocFast before them. (afaik)
-
I've had mine like that for a while now and its not caused any problems for me.
-
I thought you were going to talk about SearchStar 0.70b and the new printf feature that was added. :lol: :lol: :lol:
-
Talking about cool little programs, what about MCP?
It's free for 68k users, like me.
And do a lot of good job in the system.
-
From the docs;
"WBAllocFast V1.5
================
This tool redirects all Chipmem-Allocs from 136 Bytes (Mousepointer)
or greater to Fastmem. It redirects more allocs than "WBCtrl IMT=FAST".
This way nearly all Chipmem stays free.
Usage:
in Startup-Sequence before "IPrefs"
WBAllocFast >NIL:"
Since the programmer suggests using it this way, who am I to argue? I have been running the program this way, and have had no problems at all.