My miggy's using to much chipmem...

Hi
after boot-up there's just 1600/1700 kB's chipmem free. So when I open a directory all icons will be loaded into the chipmem, which causes some apps being unloadable due to the lack of chipmem. I set the prefs/wb to load images-> other mem, but this makes no difference...
Anybody got some solutions to this?, as I've got the feeling I'm not the only one with these probs.

Thanks in advance,
P

[MrZammler]

There is a patch on aminet, which will load icons and stuff into fast mem, which will also speed up your graphics performance. I think it's called fblit or something, check it out.

You need to find out what your hogging all your chip mem, keep at a reasonable resolution like 640x480 64 colours, don't use a RAD disk or anything try and avoid loading stuff into chip ram.

speed up your graphics performance

.. The fblit manual states that fblit uses the cpu in stead of blitter, would this be good for the overall cpu performance??? I'm in doubt...

[Damion]

I had the same problem. Try Fblit and Ftext,
both are on aminet. You basically drop the files
in your c: and libs: drawers, and then make a small
change to the s:startup-sequence. With a 64 color
WB, OS3.9 and Aweb running I still have over 1.5MB
chipmem left. I had even more left on 3.1. They
speed up your system nicely as well.

[Damion]

It's a solid program, I've been using it for 6
months with NO problems. My system is faster,
and seems more stable.

I think that with an accelerator the CPU would be
faster than the blitter, but I'm not positive. I've
only experienced speed gains with fblit.

convincing story, thanks
will give it a try...

Greets
P

[J]

Yep, I recommend Fblit too. Before i got a graphics card, I was running it on an 030 and it did speed up my system (windows open faster etc).

J

[carls]

FBlit is a great program. Actually, when using AGA+FBlit on my 060, Doom plays faster than on my CV64/3D (with the same CPU).

[JaXanim]

Try EnvHandler from Aminet.
It puts all your system icons (usually stored in RAM:env) into
FastRAM.

I have OS3.9 running on an A1200 and my Chip Ram is showing around
1.9Mb.

Cheers,

JaXanim
http://waveguide.v-2-1.net

[SilvrDrgn]

I believe that the versions of FBlit and FText on Aminet might be old.  You should get the most recent versions from this LINK.

[blobrana]

There are lots of way to save chip mem...

As mentioned, FBLIT (it does what it says on the tin),
HappyENV,
 try to run  programs that can use `bufmem type = 5`
( the RAD device, for example, can be made to use fast mem)
You can change the tooltypes entry (menu/information)

(bufmem type= 1 is CHIP, and bufmem type =3 is FAST, while  bufmem type =5 is BOTH)

Most Amiga setups support FastROM. This function maps the OS ROM into fast RAM for much faster general operation. If you have are using a 16-bit ROM image with a 32-bit RAM available (say, an A2000 with an 060 accelerator) the difference in general speed can be very noticable. Most accelerators come with FastROM support, either in the form of a software command, or a hardware jumper, so read your manual if you aren't sure. The AmigaOS also provides FastROM support via the CPU command CPU FastROM or CPU NoFastROM.

"Try EnvHandler from Aminet.
It puts all your system icons (usually stored in RAM:env) into
FastRAM."

That's not what envhandler does. Usually there will
be a line in the startup-sequence which copies everything from envarc:
(sys:prefs/env-archive)
to env: (ram:env). This tends to include a lot of icons/prefs/settings etc which
are not needed every time you boot your amiga. envhandler will setup a
env: device, everytime a progrom tries to access a file in env: it
will be copied from hd to the env: "drive". This method will speed up
booting and save some memory. A very nice program indeed :-)
Usually it won't free up chip ram (unless you are VERY low on fast
ram).

Usually it won't free up chip ram (unless you are VERY low on fast
ram).

shouldn't this be the other way around?? free chipmem provided there's ENOUGH fastmem....

Because RAM disks respect the memory priorities, fast RAM gets used first. That's why the environment variables shouldn't take chip RAM, if there is any fast RAM available at all.