Card 4MB from ebay

[AlexJ]

The 4MB/3.9MB is down to the memory manufactur using 1MB=1000KB rather than the correct 1MB=1024KB.

4 000KB / 1 024KB = 3.90625MB

[Tiago]

The 4MB/3.9MB is down to the memory manufactur using 1MB=1000KB rather than the correct 1MB=1024KB.

4 000KB / 1 024KB = 3.90625MB

Yes Alexj, that's it thanks

[TiredOfLife]

Use SysInfo.
That will tell exactly what is on the card.

[Tiago]

Use SysInfo.
That will tell exactly what is on the card.

In CLi?
Ok i will try that when i get home.
Thanks

[Harrison]

Seems fine to me too. You will never see 100% free memory for either chip or fast ram as the system will be using some just by running.

Here is a quick explanation of the difference between chip and fast ram. Most people think the chip ram is mainly for graphics related tasks, but this isn't quite right. It is called chip ram because this area of ram is dedicated for use by the Amiga custom chipset. So chip ram is used by all of the custom chips in the Amiga for graphics, IO and audio data. And if an Amiga only has chip ram then this ram also gets used for everything else ram related such as the ram disk, and programs loaded into ram.

But, then some fast ram is also added to an Amiga, things such as programs and the ram disk are loaded into fast ram, and the chip ram is then left exclusively for the chipset to use. This is the main reason that just added some fast ram speeds up an Amiga so much.

Also as you run programs some of the ram gets eaten up and locked until a system reboot so don't be surprised if after you quit an application all of the ram doesn't free up. This issue can be helped greatly by enabling a secret developers Workbench menu. If you want to do this edit your startup-sequence and find the line "LOADWB" and change it to "LOADWB -DEBUG". Then after rebooting you will find you have an extra menu in Workbench. Don't use the ROMWack item as this is for modem based development use, but the second option, Flushlibs, will flush out any unused system libraries from memory and free up and ram the programs were using. This is a very useful thing to enable and use in Workbench.

[TiredOfLife]

SysInfo can found on Aminet.
FlushLibs can also be done on the Cli.
Memoptimiser should help with some of the memory issues Harrison was talking about.
The other program I mentioned is supposed to be particuarly good but is still in the early stage of development I suspect.
It has received a lot of credit from other programmers though.