Originally Posted By: Ross Wellington
Hi,

I have seen the a similar nomem err with downloading a relatively small database <6 GB. I am using the new v10/v9 build and player software.

The error is "0e80:0 nomem err" or sometimes "0000.0 nomem Err and "0000.1 nomem err"".
The front panel locks up but you can use the remote to get arounsd it sometimes although, it returns quickly.

I have not seen this before on this player with the multiple times I have loaded the system while testing the v10/v9 build/load (probably 30 times) and previously loaded up 45 GB to the drives.


Is this with two 250GB drives installed ?

I think it is very likely that there is simply insufficient RAM in the empeg to hold of the necessary data structures (kernel and player) for filesystems of that size.

You may be able to work around it, by shifting more memory away from the player software, using the ReserveCache=nn flag in the player's config.ini file:


[Startup]
;; Tell the player to leave about 1MB of RAM for other uses:
ReserveCache=15


Oddly, the Empeg FAQ entry for this suggests that each chunk is reported to be a bit larger than 32kBytes -- we've known for a few years now that each chunk is actually 64kBytes.

Cheers