Fiery Central doesn't work with more than 3GB RAM?

[oxident]

Hi!

My local dealer borrowed me his FC dongle in order to evaluate it for our printers. Therefore I've set up a dedicated machine (vanilla Win7 x64) and installed the latest version of FC. Unfortunately, it only starts up completely if I limit the amount of RAM (either physically by removing modules or by restricting memory using BCD) to exaclty 3072MB...

If I leave the original amount of RAM (8192 MB) installed, the Fiery Bar just says "Starting ..." indefinitely and the task manager shows that Fiery.exe is taking up a complete CPU core.

Is this behaviour expected?

[Randy_W]

This is expected behavior for current releases of Fiery Central. EFI is currently looking at enhancing this limitation in future releases.

Regards

[oxident]

Thanks for this fast and precise answer. I'm looking forward to see support for this config in the future ;-)

[adam1991]

What would more than 3GB of RAM give you that you don't have today?

Is FC not performing some function?

[oxident]

What would more than 3GB of RAM give you that you don't have today?

I know what you're trying to say ... and yes, I also agree that a memory expansion won't cure every problem.

But when talking about FC, the entire system, including the latest FEA (with JobFlow and HotFolders because I do see an advantage of having them locally on the FC) consumes between 2.2 and 2.5GB of active memory without anyone logged in to the console itself.

Just after logging in and simply starting CWS, the amount of free memory went down to nearly 0kb (!) and I clearly notice swapping although there is still about one GB of non-active RAM available.

To sum up: If you're going to use all current Fiery functions and FC on one single machine, 3GB of RAM is just not enough and as FC doesn't deal with copier interfaces (which might get DMA problems on machines with more than 3GB RAM) I can't see any point why it behaves like it does now...